The Scrum Master is a facilitator whose goal is to remove obstacles blocking the team. A role often confused with project management, but one that requires radically different skills.
The Scrum Master is first and foremost a facilitator. Their role is to remove all impediments the development team encounters. Their goal: keep the team focused throughout the Sprint, whatever means are required — financial, organisational, or human.
An essential caveat: a good project manager can be a bad Scrum Master, and vice versa. The two roles require very different skills. The project manager plans, controls, directs. The Scrum Master protects, facilitates, and develops collective autonomy.
Key skills
- Communication and courage: be transparent regardless of circumstances, even when it's uncomfortable
- Teaching ability: guide without imposing — one of the most delicate aspects of the role
- Consensus-building: resolve conflicts, synthesise stakeholder perspectives
- Empathy: understand human tensions before seeking technical solutions
- Team spirit: develop collective strength over individual performance
- Scrum mastery: know the framework well enough to explain and defend it
What the Scrum Master is not
- Not a domain expert of the team's field (but knows how to find the right resources)
- Not a budget manager (they ensure deadlines are met and Sprint events are held)
- Not necessarily a team member (ideally not, but pragmatically not always possible)
- Not the team's line manager
- Not the project decision-maker: they facilitate consensus and collegial decisions
An effective Scrum Master gradually makes themselves redundant. Their success is measured by the team's growing autonomy — the day the team no longer needs them to resolve obstacles is a sign of a job well done.