What is a Scrum Master?
A Scrum Master is not a meeting organizer, a task tracker, or a junior project manager. The role is harder to explain than Product Owner or Developer because the value is invisible when done well — and painfully obvious when done poorly. The best SMs don't run the team. They make the team capable of running itself.
Scrum Master definition
The Scrum Master is accountable for the Scrum Team's effectiveness. They do this by enabling the team to improve practices within the Scrum framework, removing impediments to progress, and ensuring all Scrum events are productive and stay within time-boxes. The Scrum Master serves — not manages — the team, the Product Owner, and the organization.
What a Scrum Master is not
Half the confusion about this role comes from what people assume it is. Let's be direct about the most common misconceptions.
Not a project manager
A PM controls — the SM enables. The SM has no authority over the team's work, can't assign tasks, and doesn't own the timeline.
Not a secretary
If the SM's only job is booking rooms and taking notes, the organization has a role vacuum. Someone needs to do facilitation and Agile coaching — that's the SM.
Not a team lead
Developers self-organize. The SM protects that self-organization — they don't override it. A SM who tells developers how to do their work is doing the wrong job.
Not a people manager
Performance reviews, salary decisions, and career paths are not part of the Scrum Master role. Mixing these creates a power dynamic that undermines psychological safety.
What a Scrum Master actually does
Facilitates Scrum events
Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective — the SM makes sure these happen, are effective, and don't drag on past their time-box.
Removes impediments
Anything slowing the team down that they can't resolve themselves — technical blockers, organizational friction, unclear requirements — the SM owns resolution.
Coaches on Scrum
The SM helps the team understand Scrum theory and practice. This is ongoing work: teams drift, new members join, and Scrum is easy to do badly.
Shields the team
Uninvited stakeholders in standups, mid-sprint feature requests, scope creep — the SM protects the team's ability to focus on the Sprint Goal.
Frequently asked questions
How do you measure a Scrum Master's effectiveness?
Not by meetings facilitated or tickets updated. Effective SMs show up in team metrics: fewer recurring impediments, more consistent velocity, higher psychological safety in retrospectives. The quieter the SM needs to be, the better the team is doing.
Is a Scrum Master needed for small teams?
Yes — and often more than for large ones. Small teams have fewer people to notice and correct Scrum drift. An SM who spends a few hours per week with a small team can prevent months of accumulated bad habits.
Can one person be Scrum Master for multiple teams?
It's possible but demanding. Each team needs enough SM presence to get impediments resolved and events facilitated well. More than two teams per SM usually means someone is getting short-changed.
AI coaching for Scrum Masters
Try the Scrum Master Coach — get instant answers to facilitation and impediment questions.
Try Scrum Master Coach →