What are the three accountabilities in a Scrum Team?

WHAT THIS TESTS: This question isn't just a vocabulary quiz. It tests your understanding of the fundamental separation of concerns in Scrum. The interviewer is checking if you grasp the 'why' behind the structure: that a single, empowered Product Owner maximizes value, a self-managing team of Developers delivers that value, and a dedicated Scrum Master protects and improves the process. They are looking for precision and an understanding of how these roles interact to create a functional, empirical process.

A GOOD ANSWER COVERS: A senior-level answer is crisp and correct. First, state there are exactly three accountabilities within the one Scrum Team: the Product Owner, the Scrum Master, and the Developers. Second, define each one's primary focus. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team, primarily by managing the Product Backlog. The Developers are accountable for creating a usable Increment each Sprint and instilling quality. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide and coaching the team and organization on its effective application.

COMMON WRONG ANSWERS: The most common red flag is naming roles that are not part of the Scrum Team, such as Project Manager, Business Analyst, or QA Engineer. This shows a misunderstanding of the cross-functional nature of the Developers and the self-contained nature of the Scrum Team. Another mistake is describing the Scrum Master as a project manager, team lead, or administrator who assigns tasks. This fundamentally misrepresents the role, which is a servant-leader focused on coaching and process effectiveness, not directing work. Finally, confusing 'accountability' with 'job title' is a subtle error; these are roles people play, not necessarily their formal HR title.

LIKELY FOLLOW-UPS: Expect questions that probe the boundaries of these roles. For example: 'Who is responsible for quality?' (The Developers, as a whole team). 'Can the Product Owner and Scrum Master be the same person?' (No, this creates a conflict of interest between maximizing value and upholding the process). 'How does a Scrum Master handle conflict between the Product Owner and the Developers?'.

ONE CONCRETE EXAMPLE: In a team building a new mobile banking feature, the Product Owner's focus is on defining and prioritizing user stories like 'user can deposit a check via photo' based on market value. The Developers (including UI/UX designers, backend engineers, and testers on the team) are focused on building, testing, and integrating that feature into a usable Increment within the Sprint. The Scrum Master's focus is on ensuring the Daily Scrum is effective, removing an impediment where the team is blocked by another department's API, and coaching the PO on how to write better-defined backlog items for the next Sprint.