Servant-Leader ScrumMaster¶
Definition¶
The ScrumMaster is responsible for making Scrum work: teaching others how Scrum functions, removing obstacles that block the team's progress, protecting the team from external interference during sprints, and helping the team improve its own processes in retrospectives. Critically, the ScrumMaster has no authority to assign work or mandate how the team should solve problems. The role is one of facilitation and service, not command.
In the Book¶
Schwaber describes the ScrumMaster's primary job as protection and enablement, using the metaphor of a sheepdog: the sheepdog's job is to keep the flock together and protect it from wolves, not to tell the sheep where to graze. The ScrumMaster is responsible for knowing and applying Scrum's practices, meetings, and artifacts correctly. When a team is drifting from Scrum principles—falling back into task assignment, skipping daily standups, extending a sprint—the ScrumMaster steps in to redirect them.
Several case studies illustrate the role's subtlety. In the Litware example, John Chen was assigned as ScrumMaster but didn't attend the Sprint planning meeting because of other priorities. Schwaber immediately had him replaced with Elsa, who understood that a ScrumMaster "would no more delegate his responsibilities than a sheepdog would lie down for a nap while herding the flock." John's absence sent a message that the team was not important.
In the MegaFund case study, Terry Adams (a former project manager) transitioned to ScrumMaster by removing impediments and protecting focus. When a senior VP pressured an engineer to do side work during the sprint, Terry didn't shame the VP; instead, he explained Scrum's mechanisms for handling opportunities—including the ability to terminate a sprint early if something truly urgent arises. This approach worked because Terry understood that the ScrumMaster must operate within organizational culture, even when making the case for change.
However, Schwaber also shows the limits of the role. In the Contoso.com case, Schwaber (serving as ScrumMaster) escalated an impediment too aggressively—he was fired for being seen as an obstacle rather than a facilitator. He concludes: "A dead sheepdog is a useless sheepdog." The ScrumMaster must push for change, but not in ways that put the job at risk.
Why It Matters¶
This role design shifts the project manager's focus from planning and control to enablement and learning. It recognizes that in complex work, the team knows more about how to solve problems than any single manager. The ScrumMaster's job is to remove friction so the team can apply that knowledge, and to coach the organization to support rather than undermine the team's work. This model is valuable wherever hierarchical control breaks down or where expert knowledge is distributed across the team.