The Scrum Guide gives the Scrum Master one primary accountability: the Scrum Team's effectiveness. The most practical expression of that is removing impediments.
Simple to say. Hard to do well. Because impediments are not just broken build pipelines or missing access to a tool. They include:
- Unclear requirements that the team re-interprets every sprint
- Stakeholders who say yes in the meeting and block in the ticket
- Organizational processes that require four approvals for a two-hour task
- A team dynamic where people don't speak up in retrospectives
A Scrum Master who only handles the technical blockers is operating at maybe 20% of their potential. The high-leverage work is organizational — changing the system the team operates in, not just patching the symptoms.
The Scrum Guide describes three service areas: serving the Scrum Team (coaching, facilitating events), serving the Product Owner (helping with backlog practices and goal clarity), and serving the organization (driving agile adoption, restructuring how work flows). That last one is where most SMs underinvest.
For PSM candidates: the exam heavily tests your instinct about who the SM serves and when. You'll see scenarios with management pressure, poorly run sprints, and team conflicts — and in each case, the right answer will come back to "what would restore the team's ability to deliver?"
Exam tip: The Scrum Master does not assign tasks to developers, does not manage the team, and does not decide what goes in the sprint. Any scenario where an SM does these things is describing an anti-pattern.