3.4 The Scrum Master

What the Scrum Master Is Accountable For

The 2020 Scrum Guide gives the Scrum Master two precise accountabilities, and PSM I tests the exact wording:

1. Establishing Scrum as defined in the Scrum Guide — done by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
2. The Scrum Team's effectiveness — done by enabling the Scrum Team to improve its practices within the Scrum framework.

Read that second line carefully. The Scrum Master's accountability is the Scrum Team's effectiveness — not merely "removing impediments," "facilitating meetings," or "making sure the team follows the process." Those activities are services the Scrum Master provides (covered in 3.5), but the accountability itself is broader and outcome-focused. A common PSM I trap states the Scrum Master is "accountable for the team's productivity" or "for delivering the Increment" — both wrong. The Increment is the whole Scrum Team's accountability; the Scrum Master is accountable for Scrum's effectiveness and its proper establishment.

The Guide adds that the Scrum Master is accountable for establishing Scrum — meaning when the framework is misapplied, it is the Scrum Master's accountability to help the team and organization understand and correct it, by teaching and coaching rather than by decree.

A True Leader Who Serves

The 2020 Scrum Guide describes the Scrum Master as a true leader who serves the Scrum Team and the larger organization. This phrasing matters for the exam: the 2020 edition broadened the earlier "servant-leader" label to "true leader who serves," but the intent is the same — the Scrum Master leads by serving, coaching, teaching, facilitating, and removing barriers, never by commanding. (If a question quotes the exact 2020 wording, "true leader who serves" is correct; "servant-leader" reflects older guides.)

Key consequences tested on PSM I:

• The Scrum Master has no authority over the people on the Scrum Team. They cannot assign tasks to Developers, cannot override the Product Owner's backlog ordering, and cannot conduct performance evaluations as part of the accountability.
• The Scrum Master is not a project manager, not a team secretary, and not a scribe whose job is to take notes, book rooms, or run status meetings.
• The Scrum Master holds the team accountable to Scrum by coaching, not by enforcing through positional authority.

Coaching Self-Management and Cross-Functionality

A core part of the Scrum Master's work with the team is coaching the team members in self-management and cross-functionality. Because the Scrum Team is self-managing, the Scrum Master's job is to make the team more self-managing over time — not to step in and make decisions for it. If the Scrum Master starts assigning tasks or resolving every dispute, they undermine the very self-management they are accountable for protecting.

The Scrum Master also helps the Scrum Team focus on creating high-value Increments that meet the Definition of Done, causes the removal of impediments to the team's progress, and ensures that all Scrum events take place and are positive, productive, and kept within the time-box. Note the verb "causes" for impediment removal — the Scrum Master does not necessarily fix every impediment personally; they cause its removal, which may mean coaching the team to handle it or escalating an organizational blocker.

Worked scenario

A manager asks the Scrum Master to act as the project manager who plans the schedule and directs the Developers' daily work. The Scrum-aligned response is to decline that mandate: the Scrum Master is a true leader who serves, has no authority over the people, and is not a project manager. Directing daily work would violate the team's self-management, which the Scrum Master is meant to coach and protect. Instead, the Scrum Master serves the organization by helping it understand why command-and-control control contradicts the empirical, self-managing approach Scrum is built on.

Stances, Misconceptions, and the 'True Leader' Test

Because the Scrum Master leads without authority, the accountability is exercised through a range of stances — teacher, coach, mentor, facilitator, and change agent — chosen to fit the situation. A Scrum Master teaches when the team lacks Scrum knowledge, facilitates when the team needs help reaching a decision it owns, coaches when the team must grow its own capability, and acts as a change agent when the organization itself blocks empiricism. What never appears in that list is commander: there is no stance in which the Scrum Master directs the Developers' work or overrides the Product Owner.

Several persistent misconceptions are tested directly on PSM I:

• "The Scrum Master is the team's manager." False. The Scrum Master has no authority over the people and does not conduct performance reviews as part of the accountability.
• "The Scrum Master is responsible for delivering the Increment." False. The whole Scrum Team is accountable for the Increment; the Scrum Master is accountable for Scrum's effectiveness.
• "The Scrum Master must attend and lead every event." False. The Scrum Master ensures events happen and stay within their time-box and are productive, but the Daily Scrum is for the Developers, and the Scrum Master need not facilitate every event once the team is mature.
• "The Scrum Master removes every impediment personally." Imprecise. The Scrum Master causes the removal of impediments — sometimes by coaching the team to remove them, sometimes by escalating organizational blockers.

A quick decision test

When a question describes the Scrum Master doing the team's work (assigning tasks, making product decisions, writing the Sprint Backlog), the Scrum-aligned answer is almost always "no" — that behavior undermines self-management. When it describes the Scrum Master helping the team become more capable (coaching, teaching, facilitating, removing barriers), it aligns with the true-leader-who-serves accountability.