Scrum Master

Close

The Scrum Master helps the Scrum Team and organization use Scrum effectively.

That sounds simple, but it is a demanding role. A Scrum Master coaches, facilitates, removes impediments, protects useful feedback loops, and helps the organization see where its habits are making Scrum harder than it needs to be.

The Scrum Master is not the team’s boss. The Scrum Master does not assign work to Developers, decide product priorities, or manage the sprint for the team. A good Scrum Master helps the Scrum Team improve how it works so Scrum becomes useful rather than mechanical.

Who This Page Is For

This page is for people who want a practical understanding of what Scrum Masters do and how the role should work.

It is especially useful for:

  • Scrum Masters who want a clearer description of their accountability
  • Scrum Teams that expect the Scrum Master to run every meeting
  • Managers trying to understand how the Scrum Master differs from a project manager
  • Product Owners who want a healthier partnership with the Scrum Master
  • Organizations where impediments are larger than the Scrum Team can solve alone

What This Page Covers

This page explains what a Scrum Master is accountable for, what the Scrum Master does for the Scrum Team, Product Owner, and organization, and what problems appear when the role is misunderstood.

It also explains the Scrum Master’s authority over the process, why impediments are broader than obvious blockers, and why the role should not be reduced to meeting facilitation.

What Is a Scrum Master?

The Scrum Master is accountable for helping the Scrum Team use Scrum well.

That includes helping the Scrum Team understand Scrum values, roles, events, artifacts, and commitments. It also includes helping the team inspect and adapt, remove impediments, improve collaboration, and work toward the Sprint Goal.

The Scrum Master pays attention to how Scrum is working.

  • Are Scrum events creating useful feedback?
  • Are Developers able to own the Sprint Backlog?
  • Is the Product Owner available enough for the Scrum Team?
  • Are impediments being removed or merely discussed?
  • Is the Definition of Done helping the Scrum Team create real increments?
  • Is the organization helping or interfering with Scrum?

A good Scrum Master keeps asking those questions and helps the Scrum Team act on the answers.

What a Scrum Master Does

A Scrum Master does anything useful to help the Scrum Team improve its use of Scrum.

That often includes:

  • Coaching the Scrum Team in Scrum
  • Helping the Scrum Team improve how it works
  • Removing impediments to progress
  • Facilitating useful conversations
  • Helping the Product Owner with backlog and stakeholder collaboration
  • Protecting the Sprint Goal from unnecessary disruption
  • Helping the organization understand how to work with Scrum Teams
  • Making recurring problems visible
  • Encouraging follow-through after retrospectives

Facilitation is part of the work, but it is not the whole job. A Scrum Master who only schedules meetings and updates tools is missing the deeper purpose of the role.

Impediments Are Broader Than Blockers

Some people use the word blocker for anything that stops a Scrum Team from moving forward. I prefer impediment because it is broader.

A blocker is obvious. Work cannot continue until something is resolved.

An impediment may be subtler. It may slow the Scrum Team down, weaken quality, increase handoffs, reduce Product Owner availability, delay feedback, create unnecessary dependencies, or make it harder for Developers to finish work inside the sprint.

Examples include:

  • A test environment that is unreliable
  • A Product Owner who is too busy to answer questions
  • Too many people split across multiple Scrum Teams
  • Leaders adding work during the sprint
  • An approval process that delays releases
  • A Definition of Done the Scrum Team cannot meet
  • Stakeholders who skip Sprint Reviews
  • Retrospective improvements that are never followed up

A Scrum Master does not have to solve every impediment personally. But the Scrum Master should help make impediments visible and help the right people act on them.

The Scrum Master and Scrum Events

The Scrum Master helps Scrum events serve their purpose.

Early in a Scrum Team’s development, the Scrum Master may facilitate events actively. That can be useful while the team is learning. Over time, the Scrum Master should help the Scrum Team own more of the events itself.

Over time, Scrum meetings should become less dependent on the Scrum Master.

For example:

  • Sprint Planning should help the Scrum Team create a Sprint Goal and a realistic starting plan.
  • The Daily Scrum should help Developers coordinate, not report status to the Scrum Master.
  • The Sprint Review should help the Scrum Team and stakeholders inspect the increment and adapt the Product Backlog.
  • The Sprint Retrospective should lead to real improvement, not just conversation.

The Scrum Master watches for drift. When a Daily Scrum becomes a status meeting, a Sprint Review becomes a staged presentation, or a retrospective produces the same complaints every sprint, the Scrum Master helps the Scrum Team recover the purpose of the event.

Authority Over Process, Not People

A Scrum Master does not have traditional management authority over Scrum Team members.

The Scrum Master should not assign tasks, evaluate individual performance, or tell Developers how to do the technical work. The Developers own the plan for how to create the increment. The Product Owner orders the Product Backlog. The Scrum Master helps the Scrum Team use Scrum effectively.

The Scrum Master does have influence over the process.

For example, a Scrum Master might say, “Our Sprint Reviews are not giving us useful stakeholder feedback. Let’s change how we invite stakeholders and what we ask them to react to.”

That is different from saying, “I want this person to review all code before it is checked in.” The first helps improve how Scrum is being used. The second crosses into deciding how Developers do the work.

The boundary is not always perfectly clean, but it matters. Scrum Masters lead through coaching, facilitation, observation, influence, and persistence.

The Scrum Master Helps the Product Owner

The Scrum Master also helps the Product Owner use Scrum well.

That does not mean the Scrum Master owns the Product Backlog. The Product Owner is accountable for the Product Backlog, Product Goal, ordering, and product-value decisions.

The Scrum Master can help by noticing when:

  • Product backlog items are too large or unclear
  • The Product Owner is unavailable to Developers
  • Stakeholders are bypassing the Product Owner
  • Sprint Planning is painful because refinement is weak
  • The Product Owner is pushing Developers to take more work than they believe they can finish
  • The Product Backlog is not transparent or understood

A strong Scrum Master and Product Owner partnership helps the Scrum Team stay focused on both product value and team effectiveness.

The Scrum Master as Coach and Change Agent

Many Scrum problems are outside the Scrum Team.

Approval processes, reporting expectations, staffing decisions, budgeting habits, too many simultaneous initiatives, and individual-performance incentives can all interfere with Scrum.

A Scrum Master helps the organization see those problems.

This work can be uncomfortable because organizational impediments are rarely solved by one person. A Scrum Master may need to work with managers, leaders, other Scrum Masters, Product Owners, or stakeholders. The goal is to improve the environment so Scrum Teams can deliver better results, not to blame the organization.

A Scrum Master is often a change agent. That means helping people notice when old habits are weakening Scrum and helping them try better ones.

Should a Scrum Master Do the Work of the Sprint?

In general, the Scrum Master should avoid becoming one of the Developers doing sprint work, especially on a new Scrum Team.

Combining Scrum Master and Developer work can create conflicts. A Scrum Master who is deeply involved in a technical debate may stop noticing whether the conversation is useful, whether quieter people are being excluded, or whether the Scrum Team is drifting from the purpose of the event.

That does not mean a Scrum Master can never contribute. Small organizations may need people to wear multiple hats. But there are costs. The more a Scrum Master becomes a contributor to the sprint work, the harder it is to remain neutral, facilitative, and focused on Scrum effectiveness.

Is Scrum Master a Full-Time Role?

Often, yes.

A Scrum Team that is new to Scrum usually needs more help than it expects. The Scrum Master may need to coach the team, help the Product Owner, facilitate early events, remove impediments, teach Scrum, work with leaders, and help the organization adapt.

Over time, the amount of hands-on facilitation may decrease. But that does not mean the role becomes unimportant. As one set of problems is solved, deeper problems usually become visible.

Some organizations cannot justify a full-time Scrum Master for every Scrum Team. That may be a practical constraint. But do not assume the work disappears just because no one is assigned to do it.

Can One Person Be Both Scrum Master and Product Owner?

It is usually a bad idea.

The Product Owner focuses on product value, priorities, stakeholders, and tradeoffs. The Scrum Master focuses on Scrum effectiveness, team improvement, facilitation, impediment removal, and organizational change.

Those accountabilities create useful tension.

A Product Owner may want more work in the sprint. A Scrum Master may need to help protect the Developers from overcommitment. A Product Owner may want to change direction quickly. A Scrum Master may need to help the Scrum Team protect the Sprint Goal.

One person can rarely serve both needs well at the same time. If a small organization must combine roles temporarily, be honest about the tradeoffs and separate them as soon as practical.

Common Scrum Master Problems

The Scrum Master Becomes a Meeting Scheduler

Scheduling events is administrative work. It may be necessary, but it is not the Scrum Master role.

A Scrum Master should be helping the Scrum Team improve, not merely keeping the calendar updated. For more detail, see Can the Product Owner and the Scrum Master Be the Same Person?.

The Scrum Master Becomes a Project Manager

A Scrum Master who assigns work, tracks individual status, or tells Developers how to do the work weakens Developer ownership.

Scrum Masters should help the Scrum Team inspect, adapt, and improve. They should not manage the sprint for the Developers. For more detail, see Can the Product Owner and the Scrum Master Be the Same Person?.

The Scrum Master Solves Every Problem

It can feel helpful to solve problems for the Scrum Team. But if the Scrum Master becomes the solution to every issue, the Scrum Team may stop learning how to solve problems itself.

A good Scrum Master helps the Scrum Team build its own capability. For more detail, see Can the Product Owner and the Scrum Master Be the Same Person?.

The Scrum Master Avoids Conflict

Scrum makes problems visible. Some of those problems are uncomfortable.

If the Scrum Master avoids difficult conversations, important issues may stay hidden. The Scrum Master does not need to be harsh, but the role does require courage. For more detail, see Can the Product Owner and the Scrum Master Be the Same Person?.

The Scrum Master Has No Organizational Reach

Many impediments are outside the Scrum Team. If the Scrum Master cannot work with leaders or raise organizational issues, the Scrum Team may keep encountering the same problems sprint after sprint. For more detail, see Can the Product Owner and the Scrum Master Be the Same Person?.

Is Your Scrum Master Helping Scrum Work?

Use these questions to assess the role:

  • Is the Scrum Master helping the Scrum Team improve, not just schedule meetings?
  • Are impediments being removed or at least made visible?
  • Are Scrum events producing useful inspection and adaptation?
  • Are Developers owning the Sprint Backlog and Daily Scrum?
  • Is the Product Owner getting help with Product Backlog and stakeholder collaboration?
  • Is the Scrum Master helping the organization understand how its choices affect Scrum Teams?
  • Are retrospective improvements followed through?
  • Is the Scrum Master protecting Scrum from becoming mechanical?

Use the answers to find the next conversation your Scrum Team needs to have.

FAQ

What does a Scrum Master do?

A Scrum Master helps the Scrum Team and organization use Scrum effectively.

That includes coaching, facilitation, impediment removal, helping Scrum events serve their purpose, supporting the Product Owner, and helping the organization improve the environment around Scrum Teams.

Is a Scrum Master a project manager?

No. A Scrum Master does not assign work, manage individual tasks, or direct Developers.

A Scrum Master helps the Scrum Team improve how it works and helps the organization understand and use Scrum.

Does a Scrum Master run all Scrum meetings?

Not necessarily.

A Scrum Master may facilitate Scrum events, especially while the Scrum Team is learning. Over time, the Scrum Master should help the Scrum Team own its events rather than depend on the Scrum Master to run them.

Does a Scrum Master remove blockers?

Yes, but impediments are broader than blockers.

A Scrum Master helps remove anything that slows the Scrum Team down, weakens feedback, creates unnecessary handoffs, or makes it harder to create a done increment.

Can the Scrum Master be the product owner?

It is usually a bad idea.

The Product Owner focuses on value and product decisions. The Scrum Master focuses on Scrum effectiveness and team improvement. Combining the roles often creates conflicts and weakens both.

Should a Scrum Master be full time?

Often, yes, especially when the Scrum Team or organization is new to Scrum.

Some organizations may not be able to dedicate someone full time, but the work still needs to be done. Scrum Masters help with far more than meeting facilitation.