The most common misconception about the Scrum Master role is that it is primarily about facilitation. Facilitation is part of the job — an important part — but reducing the Scrum Master to a meeting facilitator misses what the accountability actually requires.

The Scrum Guide's definition is more useful: the Scrum Master is accountable for establishing Scrum as defined by the Scrum Guide and for the effectiveness of the Scrum Team. That is a broader and more demanding brief than running ceremonies on time.

What a Scrum Master actually does

The Scrum Master serves three constituencies, each with distinct needs.

Serving the Scrum Team. The Scrum Master coaches the team on Scrum theory, practice, and self-management. They remove impediments — anything outside the team's control that is slowing them down or preventing them from working effectively. They ensure that Scrum events happen, are productive, and stay within their allocated time. They create the conditions for the team to develop real autonomy rather than dependence on the Scrum Master to make things work.

Serving the Product Owner. This is the part most frequently overlooked. The Scrum Master helps the Product Owner develop effective Product Backlog management techniques, facilitates stakeholder engagement, and supports the Product Owner in understanding what the team needs from them to deliver well. A Product Owner who does not understand how to write clear, appropriately-sized backlog items, or who does not engage meaningfully with Sprint Reviews, limits the team's effectiveness in ways the Scrum Master is accountable for addressing.

Serving the organisation. The Scrum Master helps the organisation understand what Scrum requires and how to create the conditions for Scrum to work. This often means navigating the gap between how the organisation is currently structured — approval gates, resource sharing, hierarchical decision-making — and what Scrum needs to function effectively. This is change management work, and it is often the most challenging part of the role.

The coaching stance

Effective Scrum Masters tend to operate from a coaching stance by default: observing, asking questions, helping people develop their own understanding rather than providing answers. This is not passivity — it is a deliberate approach to building capability rather than dependency.

When the team lacks knowledge, the Scrum Master teaches. When they need to develop new habits, the Scrum Master coaches. When they encounter structural obstacles, the Scrum Master facilitates or advocates. The skill is in knowing which mode is appropriate and switching between them fluidly.

What the role is not

A Scrum Master is not a project manager. They do not own the delivery plan, manage dependencies on behalf of the team, or carry responsibility for the outcome of the Sprint. The team owns the work; the Scrum Master owns the process quality.

A Scrum Master is not a secretary. Scheduling meetings, taking notes, and chasing actions are not what the Scrum Guide describes as accountability-level work for this role. These tasks may need doing, but they should not consume the capacity that belongs to the coaching and change management dimensions of the job.

A Scrum Master is not an optional add-on for small teams. The accountability exists precisely because the transition to effective Scrum is harder than it looks, and because the systemic obstacles that prevent it from working tend not to solve themselves. Teams that skip the Scrum Master tend either to get a Scrum Master in everything but name (the lead developer or Product Owner absorbing the work) or to plateau at a level of Scrum competence that good coaching would have moved them past.

Becoming a Scrum Master

Our Certified Scrum Master programme develops the understanding and practical capability the role requires — not just the framework knowledge, but the coaching skills and change management capability that distinguish effective Scrum Masters from people who are good at running stand-ups.