Scrum Master Exam: Mastering Scrum Accountabilities (2026 Guide)

If there's one area where PSM I and CSM candidates consistently lose points, it's on questions about Scrum accountabilities. Not because the concepts are complicated, but because the exam tests nuance—the kind that only comes from truly understanding why each accountability exists, not just memorizing a job description. The difference between a passing score and a near-miss often comes down to whether you can instantly recognize, in a scenario you've never seen before, which accountability owns a specific decision.

The 2020 Scrum Guide made a deliberate and meaningful shift: it replaced the word "roles" with "accountabilities." That single word change carries enormous weight. A role is something you fill. An accountability is something you own. That distinction shapes how you should think about every question on your exam, and it shapes how high-performing Scrum Teams actually operate in the real world.

This guide will walk you through all three Scrum accountabilities—Product Owner, Scrum Master, and Developers—with the depth and precision you need to answer situational exam questions confidently. Whether you're sitting the PSM I through Scrum.org or the CSM through Scrum Alliance, these principles apply equally. By the time you finish reading, you won't just know what each accountability does. You'll understand the reasoning behind the boundaries, and that's what the exam is really testing.

---

Understanding the Scrum Team Structure

The 2020 Scrum Guide describes the Scrum Team as a single cohesive unit of professionals consisting of one Scrum Master, one Product Owner, and Developers. Notice the language—one team, not three separate departments. This is fundamental to getting exam questions right, because a huge number of incorrect answers are built around the assumption that these three groups are siloed from each other.

The Scrum Team is small by design, typically ten people or fewer. This isn't arbitrary. Small teams communicate faster, adapt more quickly, and maintain the shared understanding that makes self-management possible. When teams grow beyond this threshold, the Scrum Guide recommends considering reorganizing into multiple cohesive Scrum Teams, each focused on the same product, sharing the same Product Goal.

One Team, Three Distinct Accountabilities

Here's the mental model that makes everything click: think of the Scrum Team as a triangle. Each corner represents an accountability, and the strength of the triangle depends on all three corners doing their specific job. When corners overlap incorrectly—when a Scrum Master starts prioritizing the backlog, or a Product Owner starts telling Developers how to build—the structure collapses.

The Scrum Guide defines the Scrum Team as self-managing, meaning the team internally decides who does what, when, and how. This is a critical exam concept. Self-management doesn't mean chaos or absence of leadership—it means the team has the autonomy and accountability to make those decisions without being directed by someone external to the team. No traditional project manager. No external authority assigning tasks.

The team is also cross-functional, possessing all the skills necessary to create value each Sprint without depending on people outside the team. This principle is tested frequently. If a question describes a team that needs external approval before they can release, or that lacks a skill and is waiting for someone outside the team to provide it, something is wrong with that team's structure.

---

The Product Owner: Maximizing Value and Backlog Management

The Product Owner accountability is probably the most misunderstood on the exam. Many candidates think of the Product Owner as "the customer's representative" or "the requirements person." Those descriptions aren't wrong, but they're incomplete in ways that will lead you to wrong answers.

The 2020 Scrum Guide defines the Product Owner as accountable for maximizing the value of the product resulting from the work of the Scrum Team. Every other responsibility the Product Owner has flows from that core accountability. Backlog management isn't the job—value maximization is the job. Backlog management is one of the tools used to do that job.

Product Backlog Ownership and Ordering

The Product Owner is the single person accountable for the Product Backlog. Not the team, not the stakeholders, not the Scrum Master—the Product Owner. This means:

• Creating and communicating the Product Goal, which provides long-term direction for the Scrum Team
• Adding and ordering Product Backlog items so that the most valuable work is always at the top
• Ensuring the Product Backlog is transparent, visible, and understood by everyone who needs to understand it
• Refining Product Backlog items in collaboration with Developers, breaking them down and making them precise enough to be done within a Sprint

An important nuance the exam loves to test: the Product Owner may delegate the work of managing the backlog to others, but they remain accountable for it. Delegation of tasks doesn't equal delegation of accountability. If something goes wrong with the Product Backlog, the Product Owner is answerable for it.

The One-Person Rule and Stakeholder Management

The Scrum Guide is explicit that the Product Owner is one person, not a committee. This is tested directly. If stakeholders want their needs represented in the backlog, they do that through the Product Owner, not by bypassing them. The exam will sometimes present scenarios where multiple stakeholders are trying to add items to the backlog directly, or where a "Product Owner committee" is making decisions. Recognize both of these as red flags—violations of Scrum's design.

Exam mindset tip: When you see a question about who decides what gets built next, who prioritizes, or who communicates the product vision—the answer is almost always the Product Owner. When you see a question about how something gets built, the answer is almost never the Product Owner.

---

The Scrum Master: Servant Leadership and Facilitation

The Scrum Master accountability is the one that trips up the most candidates, because it's simultaneously the least like a traditional management role and the most misrepresented in popular culture. Many people come to the exam with a mental model of the Scrum Master as a "team secretary" or "meeting organizer." That model will fail you.

The 2020 Scrum Guide defines the Scrum Master as accountable for establishing Scrum as defined in the Scrum Guide. The Scrum Master serves the Scrum Team and the broader organization in making Scrum effective. The operating model is servant leadership—leading by enabling others, removing obstacles, and creating conditions where the team can do their best work.

Serving the Scrum Team

The Scrum Master's service to the Developers includes:

• Coaching in self-management and cross-functionality, helping the team develop their own capacity to solve problems
• Helping remove impediments that are blocking progress—note the phrasing: helping to remove, not necessarily removing every impediment single-handedly
• Facilitating Scrum events as requested or needed, ensuring they happen and are productive
• Protecting the team from external interruptions and interference during the Sprint

That last point deserves emphasis, because it shows up constantly in scenario questions. When a stakeholder bypasses the Product Owner and tries to add work directly to the Sprint, the Scrum Master's job is to educate and protect. When leadership wants a status report that will consume half the Sprint, the Scrum Master addresses that impediment. "Protecting the Sprint" is a real, active part of servant leadership.

Serving the Product Owner

The Scrum Master also serves the Product Owner by:

• Helping find techniques for effective Product Goal definition and Product Backlog management
• Facilitating stakeholder collaboration when requested or needed
• Helping the Product Owner understand the need for clear, concise Product Backlog items
• Coaching the Product Owner on empiricism and the Scrum framework when necessary

Serving the Organization

Beyond the team, the Scrum Master serves the wider organization by leading, training, and coaching in Scrum adoption; helping employees and stakeholders understand Scrum and empirical product development; and working with other Scrum Masters to increase the effectiveness of Scrum practices across the organization.

Exam mindset tip: When a question presents a problem—an impediment, a team conflict, a stakeholder interference—and asks what the Scrum Master should do, look for the answer that coaches and enables rather than the one that controls or decides. The Scrum Master doesn't solve problems for the team. The Scrum Master creates conditions where the team can solve problems themselves.

---

The Developers: Self-Management and Quality Standards

When the Scrum Guide says "Developers," it doesn't mean software engineers exclusively. The term refers to any member of the Scrum Team who is committed to creating any aspect of a usable Increment each Sprint. That could include testers, UX designers, analysts, or anyone else contributing to the actual work of building product.

The Developers are accountable for creating a usable Increment every Sprint. That's it—that's the core accountability. Everything else the Developers do serves that purpose.

Key Developer Responsibilities

The 2020 Scrum Guide specifies that Developers are accountable for:

• Creating a plan for the Sprint—the Sprint Backlog
• Instilling quality by adhering to a Definition of Done
• Adapting their plan each day toward the Sprint Goal
• Holding each other accountable as professionals

That third point is significant. Developers don't wait for the Scrum Master or Product Owner to tell them to adapt. The Daily Scrum exists specifically to help Developers inspect their own progress and adjust their plan. The Scrum Master isn't running the Daily Scrum—the Developers own it.

Self-Management in Practice

Self-management means Developers decide how to accomplish the work. The Product Owner determines what to build and why. The Developers determine how to build it and how much they can take on in a Sprint. No one outside the Developers tells them how to do their technical work. This is non-negotiable in Scrum, and the exam tests it heavily.

A practical example: during Sprint Planning, the Product Owner presents the Product Backlog items they'd like addressed. The Developers then forecast how many items they can complete, decompose the work into Sprint Backlog tasks, and create their plan. The Product Owner does not dictate the size of the Sprint Backlog. Leadership does not mandate the velocity. The Developers own that decision.

The Definition of Done is another Developer-owned concept worth studying carefully. It's a formal description of the state a product must be in to be considered complete. If the organization has a Definition of Done, all Developers must follow it. If the organization doesn't have one, the Scrum Team creates one. The exam will test whether you recognize that cutting corners on the Definition of Done to hit a deadline is a violation of Scrum values, specifically the value of commitment and courage.

---

How Accountabilities Interact During Scrum Events

Understanding each accountability in isolation is necessary but not sufficient. The exam will also test your ability to see how they interact—especially during Scrum events.

Sprint Planning

All three accountabilities participate. The Product Owner presents the most valuable items from the Product Backlog and communicates the desired outcome—the Sprint Goal. The Developers select work and plan how to accomplish it. The Scrum Master facilitates and ensures everyone understands the purpose of the event. The Sprint Goal is collaboratively crafted by the entire Scrum Team, not dictated by the Product Owner alone.

Daily Scrum

This is a Developers event. The Scrum Master is not required to attend, and the Product Owner typically doesn't attend unless they're also doing development work. The Scrum Guide states clearly that the Daily Scrum is for the Developers to inspect progress and adapt their Sprint Backlog. Exam questions that describe a Scrum Master running the Daily Scrum or mandating a specific format are describing a Scrum anti-pattern.

Sprint Review

The entire Scrum Team and key stakeholders attend. The Scrum Team presents the results of their work and the progress toward the Product Goal. This is not a demonstration or approval meeting—it's a collaborative working session. Stakeholders provide input, and the Product Backlog may be adapted as a result. The Scrum Master facilitates; the Product Owner manages the conversation around value and next steps.

Sprint Retrospective

This is a Scrum Team event focused on improving how they work together. The Scrum Master is accountable for ensuring the event is positive and productive, and participates as a team member. The most actionable improvements identified should be added to the next Sprint Backlog—this is explicitly stated in the Scrum Guide.

---

Common Exam Pitfalls: Misconceptions About Roles

Let's address the specific traps that catch candidates off guard.

Pitfall 1: Thinking the Scrum Master manages the team. The Scrum Master has no authority over Developers. They don't assign work, evaluate performance, or make technical decisions. If a question implies the Scrum Master is directing the team's work, that's a red flag.

Pitfall 2: Thinking the Product Owner attends every event. The Product Owner must attend Sprint Planning, Sprint Review, and Sprint Retrospective. The Daily Scrum is typically for Developers only.

Pitfall 3: Confusing accountability with hands-on work. The Product Owner is accountable for the backlog but may delegate backlog tasks to others. The Scrum Master is accountable for Scrum adoption but coaches the team rather than doing everything themselves.

Pitfall 4: Thinking Developers report to the Scrum Master. No one in the Scrum Team reports to anyone within the Scrum Team. All three accountabilities are peers with different areas of ownership.

Pitfall 5: Misunderstanding "cross-functional." Cross-functional describes the team, not individuals. Not every Developer needs every skill—the team collectively needs all the skills required.

---

Practice Scenarios: Testing Your Knowledge of Accountabilities

Work through these scenarios before your exam:

Scenario 1: Halfway through a Sprint, a senior manager asks the Development Team to add a high-priority task to the current Sprint. What should happen?

Answer approach: The Developers are not obligated to accept work mid-Sprint that would jeopardize the Sprint Goal. The Product Owner should be involved in evaluating the priority. The Scrum Master may coach the manager on how Scrum works. If the Sprint Goal would be threatened, the Product Owner may cancel the Sprint—but that's a dramatic step, not the first one.

Scenario 2: The Scrum Master notices the Product Owner is struggling to communicate requirements clearly to the Developers. What is the Scrum Master's best course of action?

Answer approach: Coach the Product Owner on techniques for effective Product Backlog refinement and clear item descriptions. Facilitate conversations between the Product Owner and Developers to build shared understanding. Not take over the backlog or rewrite items themselves.

Scenario 3: During Sprint Planning, the Product Owner wants to include 40 story points of work even though the team's average velocity is 25. Who decides how much work gets included?

Answer approach: The Developers decide how much work they can realistically complete. The Product Owner selects the desired Sprint Goal and presents items, but Developers make the forecast. Including more work than the Developers are confident they can complete would violate their commitment and undermine empiricism.

---

Key Takeaways

• The 2020 Scrum Guide uses "accountabilities" instead of "roles" to emphasize ownership, not just task completion
• The Scrum Team is one cohesive unit—self-managing and cross-functional
• The Product Owner owns the what and why; Developers own the how and how much
• The Scrum Master serves through coaching, facilitation, and removing impediments—not directing or managing
• All three accountabilities interact during Scrum events, but each owns specific decisions within those events
• Violations of these boundaries—like a manager assigning tasks to Developers, or a Product Owner dictating how work is done—are Scrum anti-patterns the exam tests explicitly

---

The material in this guide covers the conceptual foundation, but genuine exam readiness comes from seeing these principles applied in varied, realistic situations. The PSM I in particular uses scenario-based questions that require you to synthesize multiple concepts at once—you can't just recall a definition, you have to reason through it. The best way to build that reasoning ability is to practice with scenario-based Scrum Master questions that mirror the style and complexity of the actual exam. Every scenario you work through deepens your intuition about where each accountability begins and ends.

---

Frequently Asked Questions

Q: Can one person hold multiple Scrum accountabilities on the same team?

A: The Scrum Guide explicitly states that the Scrum Master and Product Owner accountabilities should not be held by the same person. This would create a fundamental conflict of interest—the Scrum Master serves the Product Owner in some ways, and having them be the same person undermines that dynamic. A Developer can also be the Product Owner or Scrum Master in smaller teams, though the Scrum Guide notes this can be challenging and is generally not recommended, especially the Developer/Product Owner combination, which creates a conflict between maximizing value and executing the work.

Q: Who creates the Definition of Done?

A: If the organization already has a Definition of Done, the Scrum Team is required to follow it as a minimum and may make their own more stringent. If no organizational standard exists, the Scrum Team creates one. It's a shared standard owned by the Developers as part of their accountability for quality, but it's collaboratively created with input from all team members.

Q: Is the Scrum Master required to attend the Daily Scrum?

A: No. The Daily Scrum is a Developers event. The Scrum Master's role is to ensure the event occurs and that Developers understand its purpose, but they are not required to attend every session. If the Scrum Master does attend, they should observe and facilitate only if asked—not run the meeting or drive its structure. This is a commonly tested point on both the PSM I and CSM exams, and selecting "the Scrum Master facilitates the Daily Scrum" as a routine expectation would typically be an incorrect answer.