Skip to main content
New: 9 PM Courses with hands-on exercises and certificates
← Back to Glossary
DeliveryS

Scrum Master

Definition

A Scrum Master is a role in the Scrum framework responsible for ensuring the team understands and follows Scrum theory, practices, and rules. The Scrum Master serves the team as a facilitator and coach, not as a boss or task assigner. They help the team improve its processes, remove obstacles that impede progress, and protect the team from external disruptions.

The 2020 Scrum Guide describes the Scrum Master as an "accountable for establishing Scrum." This means the Scrum Master is responsible for the effectiveness of the Scrum process itself. They facilitate sprint planning, daily standups, sprint reviews, and retrospectives. They also coach the broader organization on how to interact with the Scrum team.

The Scrum Master serves three constituencies. They serve the developers by coaching self-management and cross-functionality. They serve the Product Owner by helping with effective backlog management and stakeholder communication. They serve the organization by leading Scrum adoption and removing organizational impediments that slow teams down.

Why It Matters for Product Managers

The Scrum Master is the PM's partner in delivery. While the PM focuses on what to build and why, the Scrum Master focuses on how the team works together to build it. A good Scrum Master makes PMs more effective by ensuring that ceremonies run smoothly, blockers are escalated quickly, and the team has a sustainable pace.

PMs should invest in their relationship with the Scrum Master. Share context about upcoming priorities so the Scrum Master can help the team prepare. Flag stakeholder dynamics that might create pressure on the team. When the Scrum Master pushes back on scope during planning, treat it as a signal about team capacity rather than resistance. The stakeholder management glossary entry covers more about managing these cross-functional relationships.

How to Apply It

  • ☐ Meet with your Scrum Master weekly (outside of ceremonies) to align on team health and upcoming priorities
  • ☐ Share your quarterly OKRs and roadmap with the Scrum Master so they understand the strategic context
  • ☐ Let the Scrum Master facilitate ceremonies without PM interference (resist the urge to take over sprint planning)
  • ☐ Support the Scrum Master when they protect the team from mid-sprint scope changes
  • ☐ Ask the Scrum Master for their perspective on team capacity before making delivery commitments to stakeholders
  • ☐ Use retrospective outputs to identify process improvements you can support as PM

For teams using the Kanban method instead of Scrum, the equivalent role is often called an Agile Coach or Flow Manager. The responsibilities shift toward optimizing flow metrics rather than facilitating Scrum events, but the servant-leader mindset is the same. See the Scrum vs Kanban comparison for more on how these approaches differ.

Related Terms

ScrumSprint PlanningSprint RetrospectiveProduct OwnerAgile

Frequently Asked Questions

What is the difference between a Scrum Master and a project manager?+
A project manager plans, assigns tasks, tracks progress, and is accountable for delivery timelines. A Scrum Master does none of those things. The Scrum Master coaches the team to self-organize, facilitates Scrum events, and removes impediments. They do not assign work or create Gantt charts. The team decides how to accomplish the sprint goal. In practice, some organizations rename project managers to Scrum Masters without changing the role, which creates confusion. A true Scrum Master is a coach and facilitator, not a manager. They have influence but not authority over the team's daily decisions.
Can a product manager also be the Scrum Master?+
The Scrum Guide explicitly separates the Product Owner and Scrum Master roles. Combining them creates a conflict of interest: the PM wants to maximize scope and speed, while the Scrum Master protects team sustainability and process health. In practice, some small teams do combine these roles out of necessity. If you must, be aware of the tension. When you are wearing the PM hat, you push for more features. When you are wearing the Scrum Master hat, you protect the team from being overloaded. These are opposing forces, and one role usually suffers.
What does a Scrum Master do all day if they are not writing code or managing the backlog?+
Good Scrum Masters spend their time on: removing impediments (escalating blocked dependencies, securing access to test environments), facilitating Scrum events (sprint planning, daily standup, retrospective, sprint review), coaching team members on agile practices, shielding the team from interruptions and ad hoc requests, working with the Product Owner to ensure the backlog is healthy, and helping the organization understand and adopt Scrum. In a mature team, some of these activities shrink over time, which is why experienced Scrum Masters often support multiple teams.
← PreviousScrumNext →Segmentation Analysis

Explore More PM Terms

Browse our complete glossary of 100+ product management terms.

Full GlossaryExplore Frameworks