What are two responsibilities of testers within a Development Team?

The assertion that quality control is a collective responsibility within the Development Team aligns with Scrum principles. In Scrum, every member of the Development Team, regardless of their title or specialization, contributes to the overall quality of the product. This reflects the essence of the Agile mindset, where collaboration, communication, and collective ownership are paramount.

In practice, while there may be individuals on the team who take on testing as a specific focus, the accountability for quality is a shared endeavor. This means that everyone on the Development Team participates in various activities that can influence quality, such as writing tests, conducting reviews, and ensuring that the Definition of Done is adhered to. This collaborative approach fosters a culture of shared responsibility, enabling the team to produce a high-quality product that meets stakeholders' expectations.

By recognizing that there is no singular "tester" role, Scrum empowers all team members to contribute their skills and insights towards maintaining and improving quality throughout the development process. This philosophy helps to integrate testing into the daily work rather than relegating it to a specific phase, leading to more effective and efficient quality management.