What are the three Scrum accountabilities and their focus?

WHAT THIS TESTS: This question isn't just a vocabulary quiz. It tests your understanding of Scrum's fundamental principle of a small, cross-functional, self-managing team. The interviewer wants to see if you grasp how these three distinct accountabilities work together to deliver value without traditional management overhead. They are checking if you understand the separation of concerns: product direction ("what"), delivery execution ("how"), and process facilitation. For a senior role, simply listing the roles is not enough; you must articulate their purpose and interaction.

A GOOD ANSWER COVERS: A complete answer names the three accountabilities and then explains their primary focus. First, the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are the sole person responsible for managing the Product Backlog, representing stakeholder needs, and making the final call on product direction. Second, the Developers are the people committed to creating any aspect of a usable Increment each Sprint. They are accountable for creating the Sprint plan (Sprint Backlog), adhering to the Definition of Done to ensure quality, and adapting their plan daily to meet the Sprint Goal. They own the "how". Third, the Scrum Master is accountable for the team's effectiveness with Scrum. They are a true leader who serves the Scrum Team, the Product Owner, and the organization by coaching in self-management, removing impediments, and ensuring Scrum theory and practice are understood and enacted.

COMMON WRONG ANSWERS: The most common red flag is describing the Scrum Master as a project manager, a "team lead," or the "boss" of the developers. The Scrum Master does not assign work or manage timelines; they are a coach and facilitator. Another mistake is implying the Product Owner is the "boss" of the Developers; the entire Scrum Team is a self-managing unit with no hierarchy or sub-teams. Using the outdated term "Development Team" instead of "Developers" indicates you may not be current with the 2020 Scrum Guide.

LIKELY FOLLOW-UPS: "Who resolves conflicts between the Product Owner and the Developers about how much work can be done in a Sprint?" (Answer: The Developers have the final say on what they can forecast for a Sprint. The Scrum Master may facilitate the conversation to ensure a collaborative outcome.) "How does a Scrum Master serve the wider organization?" (Answer: By leading, training, and coaching the organization in its Scrum adoption, and helping remove barriers between stakeholders and Scrum Teams.)

ONE CONCRETE EXAMPLE: Imagine a team building a mobile banking app. The Product Owner, after market research, decides the highest value feature is "biometric login" and adds it to the Product Backlog. During Sprint Planning, the Developers (iOS, Android, and backend engineers) pull this item into the Sprint Backlog, create a plan to build and test it, and forecast they can complete it. The Scrum Master observes that the team is being pressured by an external stakeholder to add more work mid-sprint. They intervene to protect the team and coach the stakeholder on how to properly engage with the Product Owner and respect the Sprint's integrity.