Three accountabilities in a Scrum Team and their primary focuses

WHAT THIS TESTS: This question checks if you understand the Scrum Team structure as defined in the 2020 Scrum Guide and whether you can distinguish the three accountabilities by their primary focus. It reveals whether you are relying on the actual guide or on outdated terminology and assumptions from older frameworks.

A GOOD ANSWER COVERS: First, name the three accountabilities explicitly: the Product Owner, the Developers, and the Scrum Master. Second, state that the Product Owner orders the work for a complex problem into a Product Backlog. Third, explain that the Developers are the people who do the work and that they turn a selection of the work into an Increment of value during a Sprint, which means they hold the skills needed to create the increment. Fourth, describe the Scrum Master as the person who fosters an environment where the Product Owner can order the backlog and the team can produce increments, which includes enabling transparency, inspection, and adaptation.

COMMON WRONG ANSWERS: A major red flag is using the word roles instead of accountabilities, since the 2020 Scrum Guide intentionally moved to the latter term to emphasize ownership rather than job titles. Another mistake is injecting project manager responsibilities into the Scrum Master, such as assigning tasks or controlling deadlines, which contradicts the guide's intent. Candidates also err by suggesting the Product Owner is the boss of the team or that Developers are only programmers; the provided text explicitly notes that developers in Scrum is a simplification that includes researchers, analysts, scientists, and other specialists who collectively have all the skills and expertise to do the work.

LIKELY FOLLOW-UPS: An interviewer may ask how these accountabilities interact during Sprint Planning or who is responsible if an Increment is not created. They might also ask how the Scrum Master fosters the environment without having formal authority, or why the guide uses the word developers to cover all specialists.

ONE CONCRETE EXAMPLE: Imagine a team building a healthcare analytics platform. The Product Owner orders the backlog so that regulatory compliance stories are addressed before visualization features. The Developers, including data scientists and compliance analysts, turn the selected backlog items into an Increment of value during the Sprint. The Scrum Master fosters an environment where empirical process control is upheld by ensuring transparency into the backlog and progress, which allows the team and stakeholders to inspect results and adapt for the next Sprint. This mirrors the guide's emphasis on empiricism and lean thinking.