In 30 seconds
- Helps the team and organization understand and use Scrum well.
- Removes impediments and protects the team's focus.
- Leads by serving, without authority over the work.
Who they serve
| Serves | How |
|---|---|
| Developers | Coaching self-management, removing blockers, keeping events useful |
| Product Owner | Backlog techniques, clear goals, stakeholder collaboration |
| Organization | Leading Scrum adoption, removing barriers between teams and stakeholders |
A typical week
Facilitating events when helpful, chasing an impediment the team can't clear alone, coaching someone on splitting user stories, and spotting patterns in retrospectives that need wider attention.
Anti-patterns
- Secretary: only books meetings and updates tools.
- Project manager in disguise: assigns tasks and chases status.
- Scrum police: enforces rules without explaining why.
Myth vs reality
Myth · The Scrum Master manages the team.
Reality · They have no authority over the work; they coach.
Myth · A Scrum Master must run every meeting.
Reality · They make sure events happen and are useful; others can facilitate.
Myth · Mature teams don't need one.
Reality · The focus shifts from the team to the wider organization.
The AI angle
Scrum Masters help teams agree how AI fits their way of working: review norms, working agreements, review capacity and keeping events focused on people talking.
FAQ
Is a Scrum Master a project manager?
No. Project managers plan and control; Scrum Masters coach and enable self-management.
Can a developer also be the Scrum Master?
Yes, but the role tends to get squeezed by delivery work.
How many teams can one Scrum Master support?
Often one or two; it depends on the teams' maturity.