3.4 Scrum Master Accountability

3.4 Scrum Master Accountability

Scrum Guide 2020: The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework.

Scrum Masters are true leaders who serve the Scrum Team and the larger organization.

PSPO I candidates sometimes under-study the Scrum Master because the credential is Product Owner focused. That is a mistake. Many items test whether you know how the SM enables the PO—and whether you incorrectly assign PO work to the SM (or SM work to the PO).

---

Two Core Accountabilities

The Scrum Master does not maximize product value (that is the Product Owner) and does not own the Sprint plan or technical delivery (that is the Developers). Effectiveness means the team gets better at using Scrum to deliver value—not that the SM becomes a delivery manager.

---

True Leader Who Serves

“True leader who serves” (servant leadership language in the Guide) means influence through coaching, facilitation, teaching, and impediment removal—not command-and-control authority over people.

If a scenario describes an SM “directing” Developers’ daily work or “approving” the Product Backlog order, the answer is almost always wrong.

---

How the Scrum Master Serves the Product Owner (PSPO Exam Angle)

The Guide is explicit about services to the Product Owner. Memorize these four; they are high-yield for PSPO I:

1. Techniques for Product Goal definition and Product Backlog management

The SM helps the Product Owner find techniques for defining the Product Goal and managing the Product Backlog effectively. Examples of help (not takeover):

• Facilitating workshops to make the Product Goal explicit and measurable enough to guide ordering
• Coaching on ordering strategies that improve transparency (value, risk, learning, dependencies)
• Helping the PO establish a refinement cadence that keeps the top of the backlog ready without turning refinement into a second Sprint Planning

The SM does not become the owner of the Product Goal or the person who orders the backlog.

2. Helping the Scrum Team understand the need for clear, concise Product Backlog items

Unclear PBIs create false forecasts, wasted Sprints, and weak Increments. The Scrum Master coaches the team (not only the PO) on why clarity matters and how to improve item quality collaboratively. Still, the Product Owner remains accountable that backlog management is effective.

3. Helping establish empirical product planning for a complex environment

Empirical product planning means plans are based on what was done and learned, not on big upfront certainty. The SM helps the PO and organization:

• Use Sprint Reviews and production feedback to adapt the Product Backlog
• Forecast with evidence (throughput, past Increments) instead of political promises
• Avoid fake certainty (detailed annual feature locks that ignore learning)

4. Facilitating stakeholder collaboration as requested or needed

Stakeholder collaboration is essential for value, but it can overwhelm a Product Owner or bypass them. The Scrum Master facilitates collaboration as requested or needed—for example, structuring a Sprint Review as a working session, coaching stakeholders to bring evidence to the PO, or removing barriers between stakeholders and the Scrum Team—without creating a shadow decision path around the Product Owner.

---

How the Scrum Master Serves the Scrum Team

Services to the Scrum Team include:

• Coaching self-management and cross-functionality so the team decides who does what, when, and how, and builds skills needed for Done Increments
• Helping the team focus on high-value Increments that meet the Definition of Done
• Causing the removal of impediments to the Scrum Team’s progress (the Guide says causing removal—not that the SM must personally fix every technical bug)
• Ensuring Scrum events happen, are positive, productive, and kept within the timebox

Product Owner partnership: When the PO sees Developers blocked by tooling access, conflicting management mandates, or missing skills, the effective move is often to engage the Scrum Master on the systemic impediment—while the PO continues owning value trade-offs.

---

How the Scrum Master Serves the Organization

Services to the organization include:

• Leading, training, and coaching Scrum adoption
• Planning and advising Scrum implementations
• Helping employees and stakeholders understand and enact an empirical approach for complex work
• Removing barriers between stakeholders and Scrum Teams

This organizational service is why “the company must respect Product Owner decisions” often involves the Scrum Master. Respect is not only a personality trait of executives; it is a change-coaching outcome. When leadership repeatedly overrides the Product Backlog, the SM works the organizational system; the PO continues to make transparent value decisions rather than silently accepting fake Scrum.

---

PO–SM Collaboration Patterns (Exam Scenarios)

Pattern A: Stakeholders bypass the PO

Symptom: Directors assign work directly to Developers.
PO response: Reassert Product Backlog as the single ordered source of work; engage stakeholders with value trade-offs.
SM response: Coach the organization and cause removal of the bypass impediment; facilitate healthier collaboration paths.

Pattern B: PO micromanages tasks

Symptom: PO assigns daily tasks and attends Daily Scrum as a status boss.
SM response: Coach the PO on self-management boundaries and Developer accountabilities; coach the team to reclaim the Daily Scrum.
PO growth: Shift energy to Product Goal, ordering, and clarity of PBIs.

Pattern C: Backlog is opaque and overloaded

Symptom: Hundreds of stale items; top items unclear; Sprint forecasts fail.
SM response: Help the PO with backlog management techniques and help the team understand the need for clear PBIs.
PO ownership: Still accountable for effective backlog management and value outcomes.

Pattern D: Fake deadlines destroy empiricism

Symptom: Leadership demands a fixed scope date with no trade-offs.
PO response: Offer evidence-based options (scope, date, capacity).
SM response: Help establish empirical product planning; coach stakeholders on complex work and forecasting limits.

---

What the Scrum Master Is Not

Keep these wrong answers out of your muscle memory:

• Not the Product Owner’s secretary for writing all stories without PO accountability
• Not the person who cancels Sprints (only the Product Owner can)
• Not the owner of product value maximization
• Not the assigner of Developer tasks
• Not optional “process police” who only schedule meetings—the SM is accountable for establishing Scrum and team effectiveness

---

Quick Comparison for PSPO Recall

Mastering the Scrum Master accountability from a Product Owner viewpoint is less about memorizing facilitation tricks and more about knowing where coaching ends and PO accountability begins. On the exam, choose the answer that keeps value ownership with the Product Owner, delivery self-management with Developers, and Scrum effectiveness with the Scrum Master—working as one Scrum Team.