Scrum Master
Definition
A Scrum Master is a servant-leader role within a Scrum team responsible for ensuring the team understands and applies Scrum correctly, facilitating Scrum ceremonies, and removing impediments that block developers from doing their work.
The Scrum Master is one of three accountabilities in Scrum. The term "servant-leader" captures the essential tension of the role: the Scrum Master serves the team by helping them work better, but doesn't manage the team or make decisions about what to build.
What a Scrum Master actually does:
- Facilitates sprint planning, daily standup, sprint review, and retrospective
- Coaches the team on Scrum values and practices
- Removes impediments — blockers the team can't resolve themselves
- Shields the team from outside interruptions during the sprint
- Works with the Product Owner to refine the backlog process
- Coaches the organization on how to work effectively with the Scrum team
What a Scrum Master does not do:
- Manage the team or assign work
- Make product decisions (that's the Product Owner)
- Guarantee delivery (the developers own their commitments)
- Act as a project manager
The Scrum Master role is frequently misunderstood. In organizations that conflate it with project management, Scrum Masters end up doing status reporting and ticket shuffling rather than process coaching. This is a common failure mode.
Scrum Master certification: Two main certification bodies — Scrum Alliance (CSM) and Scrum.org (PSM). PSM is exam-based; CSM requires a course. Neither guarantees a good practitioner.
In small teams, the Scrum Master role is sometimes taken on by a developer who also writes code. In larger organizations, it's a dedicated full-time role — sometimes one SM supporting two or three teams.
Examples
- SM facilitates a sprint retrospective using Start / Stop / Continue format
- SM escalates to CTO after a third-party vendor blocks the team for the second sprint in a row
- SM coaches a new developer on how to surface blockers in standup without derailing the 15-minute limit
- SM works with PO to improve the quality of acceptance criteria before stories hit sprint planning
- Team of 8 shares a Scrum Master who also writes code three days a week
Snap a scrum master. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.