What is a Scrum Master?
The Scrum Master is the role on a Scrum team responsible for protecting the team from interrupts, removing blockers, and coaching both the team and stakeholders on healthy sprint practice. Despite the title, they are not a project manager and not a team lead.
Scrum Master vs Project Manager
- Project Manager — owns scope, dates, and reporting upward. Makes commitments on behalf of the team.
- Scrum Master — owns process and team health. Does not commit work; the team commits to its own sprint goal.
Some organisations conflate the two roles. Where they do, the Scrum Master title becomes a project manager with extra ceremonies. Done well, the role is closer to a coach than a manager.
What a Scrum Master actually does
- Removes blockers — the most concrete, daily activity. If a ticket is stuck on something outside the team, the Scrum Master is the path to unblocking.
- Protects the team — pushes back on mid-sprint scope changes, gates the team from random stakeholder pings during a sprint.
- Facilitates ceremonies — runs sprint planning, retrospectives, and reviews so the team focuses on the content.
- Coaches — the team on Scrum practice; the Product Owner on backlog health; stakeholders on what Scrum actually is.
- Surfaces patterns — uses retros and metrics (velocity, cycle time, blocker frequency) to flag systemic issues before they become crises.
Failure modes
- Becoming a status reporter — running every standup as a manager-update meeting kills team ownership.
- Owning the backlog — that is the Product Owner's job. Conflating roles muddles authority.
- Process zealotry — refusing to deviate from textbook Scrum even when the team's context demands it.
- Staffing the role part-time — works for a stable team. For a team with frequent blockers, part-time Scrum Mastering means the blockers stack.