Who Owns Quality in a Scrum Team?

In the world of Agile development, Scrum has emerged as one of the most popular frameworks for managing software projects. Scrum teams are self-organizing and cross-functional, with the goal of delivering high-quality software in short iterations called sprints. However, when it comes to the question of who owns quality in a Scrum team, there can be some confusion and debate. In this article, we will explore this topic in depth and provide valuable insights into the roles and responsibilities of different team members in ensuring quality.

The Scrum Team Structure

Before diving into the ownership of quality, it is important to understand the structure of a Scrum team. A typical Scrum team consists of three key roles:

  • Product Owner: The Product Owner is responsible for defining and prioritizing the product backlog, which is a list of features and requirements. They represent the stakeholders and ensure that the team is building the right product.
  • Scrum Master: The Scrum Master is the facilitator and coach of the team. They ensure that the Scrum framework is followed, remove any impediments, and help the team improve their processes.
  • Development Team: The Development Team is responsible for delivering the product increment. They are self-organizing and cross-functional, meaning they have all the skills necessary to complete the work.

Shared Responsibility for Quality

In Scrum, quality is a shared responsibility among all team members. The Agile Manifesto emphasizes the importance of “working software” as the primary measure of progress. Therefore, every team member has a role to play in ensuring that the software meets the required quality standards.

Let’s take a closer look at the specific responsibilities of each role:

Product Owner

The Product Owner plays a crucial role in ensuring quality by:

  • Defining clear and testable acceptance criteria for each user story.
  • Prioritizing the product backlog based on the value and quality of the features.
  • Collaborating with the Development Team to clarify requirements and address any questions or concerns.
  • Participating in sprint reviews to provide feedback on the delivered increment.

Scrum Master

The Scrum Master supports the team in maintaining and improving quality by:

  • Facilitating discussions on quality-related topics, such as code reviews, automated testing, and continuous integration.
  • Helping the team identify and address any obstacles or challenges that may impact quality.
  • Encouraging the use of Agile engineering practices, such as test-driven development and refactoring.
  • Facilitating retrospectives to reflect on the team’s performance and identify areas for improvement.

Development Team

The Development Team is responsible for delivering high-quality software by:

  • Collaborating with the Product Owner to clarify requirements and ensure a shared understanding of the expected outcomes.
  • Writing clean and maintainable code that adheres to coding standards and best practices.
  • Performing thorough testing, including unit tests, integration tests, and acceptance tests.
  • Conducting code reviews to ensure code quality and identify potential issues or bugs.
  • Continuously improving their skills and knowledge through training and self-learning.

Case Study: Spotify

One of the most successful companies that has embraced the Scrum framework is Spotify. They have implemented a unique approach to quality ownership within their teams. At Spotify, quality is considered a shared responsibility, but they have a dedicated role called the “Quality Guild” to ensure a strong focus on quality.

The Quality Guild at Spotify consists of representatives from different teams who are passionate about quality. They collaborate to define and promote best practices, share knowledge, and drive continuous improvement in quality-related areas. This approach ensures that quality is not just an afterthought but a core value embedded in the culture of the organization.


Q1: Can the Product Owner reject work based on quality concerns?

A1: Yes, the Product Owner has the authority to reject work if it does not meet the required quality standards. However, it is important for the Product Owner to collaborate with the Development Team and provide clear feedback on the quality concerns to ensure a shared understanding.

Q2: Should the Scrum Master be involved in the testing process?

A2: While the Scrum Master is not directly responsible for testing, they should encourage and support the team in adopting effective testing practices. The Scrum Master can facilitate discussions on testing strategies, help remove any obstacles that may hinder testing efforts, and promote a culture of quality within the team.

Q3: How can the Development Team ensure quality in a time-constrained sprint?

A3: The Development Team should prioritize quality throughout the sprint by following Agile engineering practices. This includes writing automated tests, conducting regular code reviews, and refactoring code to improve maintainability. By investing in quality upfront, the team can reduce the risk of introducing bugs and technical debt.

Q4: Who is responsible for maintaining the test automation suite?

A4: Maintaining the test automation suite is a shared responsibility between the Development Team and the Quality Guild (if applicable). The Development Team is responsible for writing and maintaining the automated tests, while the Quality Guild can provide guidance and support in defining best practices for test automation.

Q5: How can a Scrum team measure and track quality?

A5: There are several metrics and techniques that a Scrum team can use to measure and track quality. Some examples include:

  • Defect density: The number of defects found per unit of code.
  • Test coverage: The percentage of code covered by automated tests.
  • Customer satisfaction: Feedback from stakeholders and end-users on the quality of the delivered product.
  • Velocity: The amount of work completed by the team in each sprint, which indirectly reflects the quality of the delivered increment.


In a Scrum team, quality is a shared responsibility among all team members. The Product Owner, Scrum Master, and Development Team each have specific roles and responsibilities in ensuring quality. The Product Owner defines clear acceptance criteria and prioritizes features based on quality. The Scrum Master facilitates discussions on quality-related topics and helps the team improve their processes. The Development Team delivers high-quality software through collaboration, testing, and continuous improvement.