The Scrum Master is a role defined by Scrum as a “servant leader” responsible for ensuring the Scrum framework is understood and enacted — a job description that, depending on the organization and the individual, produces either the most valuable person on the team or the most expensive facilitator of meetings that didn’t need facilitating.
The Scrum Master is Scrum’s most paradoxical role: a leader who serves, a coach who doesn’t direct, a process guardian who must eventually eliminate the need for process guardianship. The good Scrum Master removes obstacles, shields the team from organizational interference, and quietly makes themselves unnecessary. The bad Scrum Master is the obstacle, creates organizational interference, and makes themselves indispensable by generating the very complexity they claim to manage.
Both are certified. Both attended the same two-day course. The certificate does not distinguish between them.
The Two-Day Certification
The Certified ScrumMaster (CSM) requires:
- Two days of classroom training (£1,000–£1,400)
- A multiple-choice exam (pass mark: 74%, 37 of 50 questions)
- No prior experience in software development, team leadership, or facilitation
Two days. Fourteen hours of instruction. An exam that 98% of attendees pass. This is the barrier to entry for a role that involves coaching teams, resolving conflicts, removing organizational impediments, and navigating the politics of enterprise software delivery.
For comparison: a barista certification takes longer. A first aid course is more rigorous. A driving test has a higher failure rate.
The CSM grants the holder the title “Certified ScrumMaster” and the authority to facilitate ceremonies, coach teams, and remove impediments. It does not grant the judgment to know which impediments to remove, the political capital to remove organizational impediments, or the self-awareness to recognize when the Scrum Master is the impediment.
The Good Version
The good Scrum Master is invisible. You notice them by their absence — by the impediments that don’t reach the team, the meetings that don’t happen, the organizational noise that gets absorbed before it becomes a distraction.
The good Scrum Master:
- Intercepts the VP who wants “a quick status update” (which is never quick and never just an update)
- Fixes the CI pipeline at 7 AM so the team doesn’t discover it’s broken at standup
- Notices that two teams have a dependency and introduces the right people before it becomes a blocker
- Runs a retrospective that surfaces real issues, not “we need better snacks”
- Knows when to enforce the process and when to get out of the way
- Makes themselves unnecessary — and then has the courage to notice
This person exists. This person is worth their weight in unblocked JIRA tickets. This person is also rare, because the skills required — organizational empathy, political navigation, technical credibility, facilitation mastery, and ego suppression — are not taught in a two-day course. They are earned over years.
The good Scrum Master was probably already doing the job before the title existed. They were the team lead who ran interference, the senior developer who mentored juniors, the project manager who knew when to break the process. Scrum gave them a name. The certificate confirmed what the team already knew.
The Bad Version
The bad Scrum Master is visible. Extremely visible. They are visible in the same way a speed bump is visible — technically serving a purpose, but mostly slowing everything down.
The bad Scrum Master:
- Enforces the 15-minute standup timebox while running 47-minute standups
- Facilitates conflicts between team members who were not in conflict until the facilitation began
- Schedules a meeting to discuss whether the standup should be at 9:15 or 9:30
- Runs retrospectives about the retrospective format
- Asks “did you update your JIRA tickets?” as though JIRA is the product
- Shields the team from the organization while exposing the team to Scrum
- Creates process overhead and then offers to facilitate a retrospective about the process overhead
The bad Scrum Master is not malicious. The bad Scrum Master is certified — trained to see the world through the Scrum Guide, equipped with ceremonies and artifacts, and deployed into an organization where the ceremonies and artifacts become the work. When your only tool is Scrum, every problem looks like a sprint planning meeting.
The pathology is structural: the Scrum Master’s relevance depends on the team needing a Scrum Master. A team that has internalized Scrum’s principles no longer needs a Scrum Master, which makes the Scrum Master’s success indistinguishable from the Scrum Master’s obsolescence. Self-preservation, even unconscious, produces complexity — new ceremonies, additional process, “maturity improvements” — that justify continued employment.
“The Scrum Master is the only role in software development whose success condition is its own elimination and whose survival instinct prevents it.”
The Servant Leader Problem
The Scrum Guide calls the Scrum Master a “servant leader.” This is a beautiful concept and an impossible job description.
A servant leader serves the team by leading, and leads the team by serving. In practice, this means: doing whatever the team needs, with no formal authority over anything except the process. The Scrum Master cannot fire anyone, promote anyone, assign work to anyone, or make technical decisions. The Scrum Master can facilitate, coach, and remove impediments.
This works when the impediments are within reach — a broken build, a missing requirement, a miscommunication between developers. This fails when the impediments are structural — the VP who keeps changing priorities, the architecture that makes deployment painful, the hiring freeze that leaves the team understaffed.
A servant leader without authority is a suggestion. A suggestion without authority is a sticky note. The Scrum Master’s impediment board is, in many organizations, a collection of sticky notes that describe problems the Scrum Master cannot solve, posted on a wall that the people who can solve them never visit.
The Heartbeat Lesson
At a Scandinavian telecommunications company, a weekly cross-team meeting called The Heartbeat succeeded so thoroughly that the developers stopped attending — they had already found each other and were solving problems in real time (see: Big Room Planning). A manager panicked. A consultant investigated. The empty room was not failure. It was graduation.
The Scrum Master faces the same dynamic. A team that has internalized the principles — short feedback loops, regular inspection, direct communication — no longer needs someone to facilitate these things. The standup happens naturally. The retrospective is a conversation, not a ceremony. The impediments are raised and resolved without a board.
The good Scrum Master recognizes this and steps back. The bad Scrum Master sees an empty room and mandates attendance.
Measured Characteristics
Days of CSM training: 2
Cost of CSM certification: £1,000–£1,400
CSM exam pass rate: ~98%
Barista certification duration: longer
Skills taught in 2 days: vocabulary
Skills required for the job: years of judgment
Good Scrum Masters per 100 certified: ~15
Time for good SM to become unnecessary: 6–12 months
Time for bad SM to become indispensable: 2 sprints
Impediments removed (good SM): dozens per quarter
Impediments created (bad SM): approximately equal
Retrospectives about retrospective format: too many
Standup duration (timeboxed): 15 minutes
Standup duration (actual): 47 minutes
Meetings about whether to have meetings: nonzero
