roles

Scrum Master

What the Scrum Master is accountable for, how the role helps the team deliver, and the most common ways it gets misused.

What is a Scrum Master

The Scrum Master is one of the three accountabilities on a Scrum Team. The Scrum Master is responsible for the team's effectiveness. The role is a true leader who serves the Scrum Team and the wider organization.

The Scrum Master is not a project manager and not an administrator.

Why It Matters

A strong Scrum Master makes the team faster over time. A weak one is invisible in outcomes.

When the role works:

  • The team stays focused on the Sprint Goal
  • Impediments get removed quickly
  • The team grows in self-management and cross-functionality
  • The organization gets better at Scrum, not just the team

How It Works in Scrum

The Scrum Master serves three groups.

The Scrum Team

Coaches self-management, ensures all Scrum events happen and stay focused, and helps the team meet the Definition of Done.

The Product Owner

Helps with Product Backlog management, clarity of Product Backlog items, and stakeholder collaboration.

The organization

Leads Scrum adoption, removes barriers between teams and stakeholders, and helps the wider business understand empiricism.

The Scrum Master is accountable for the team's effectiveness. This accountability cannot be delegated.

Common Mistakes

  • Acting as an administrator. Scheduling meetings and updating tickets are not the job. The team does its own coordination.
  • Acting as a project manager. The Scrum Master does not assign work or report status up.
  • Skipping the organizational work. A Scrum Master who only facilitates events leaves most of the value on the table.
  • Too many teams per Scrum Master. Spreading the role thin slows impediment removal and weakens coaching.
  • Letting Scrum erode under pressure. Skipping events or lowering the Definition of Done to hit a date is not serving the team.

Key Takeaways

  • The Scrum Master is accountable for the team's effectiveness.
  • The role serves the team, the Product Owner, and the organization.
  • Impediment removal and organizational coaching are core, not optional.
  • A strong Scrum Master makes the team faster. A weak one shows up as no change.