Who is responsible for a scrum team's performance?

It's one of those questions that sounds simple until you actually try to answer it. Developers build the product. The product owner sets the direction. The scrum master facilitates. So when a team is struggling, whose name is on the line?

The short answer, since 2020, is the scrum master.

What Changed in the 2020 Scrum Guide

The 2020 Scrum Guide introduced a subtle but important shift: the scrum master is now accountable for the effectiveness of the scrum team. The buck stops there.

This wasn't always the case, and the change was deliberate. Before 2020, it was far too common to see scrum masters doing everything the textbook told them to do — asking thoughtful Socratic questions, observing team dynamics, encouraging reflection — while bad things quietly unfolded around them. Unhealthy conflict was brewing on their watch. Performance was slipping on their watch. Dysfunction was taking root, and nobody felt a clear sense of ownership over fixing it.

Putting someone explicitly on the hook for the team's effectiveness was the Scrum Guide's way of closing that gap.

The Tension: Accountability Without Control

Here's where it gets interesting. A scrum team is meant to be self-managing. Developers decide how to do the work. The team organizes itself. So how does a scrum master own "effectiveness" without undermining the very autonomy that makes scrum work?

The answer lies in restraint. A scrum master's interventions shouldn't be constant course corrections. They should come when the team is genuinely descending into chaos — when something harmful is happening that the team can't or won't address on its own. Until that point, observation, coaching, and gentle nudges are usually the right tools.

It's a fine line. Step in too often, and you kill the team's self-management. Step in too rarely, and you're watching the ship sink from the bridge.

Everyone Still Owns Their Part

Accountability for overall effectiveness doesn't dissolve individual responsibility. Each role still carries its own weight:

• Developers are responsible for delivering a high-quality increment.
• The product owner is responsible for maximizing the value flowing through the team.
• The scrum master coaches, mentors, teaches, advises, observes, and supports — wearing different stances depending on what the moment requires.

We're all ultimately responsible for our own performance. The scrum master's accountability sits on top of that, not in place of it.

The Scrum Master's Work Goes Beyond the Team

One of the most overlooked parts of the scrum master role is that the job often extends well outside the team itself. If the organization around the team is broken, no amount of internal coaching will make the team effective.

That means a scrum master sometimes needs to:

• Work with other teams the scrum team depends on.
• Engage with other functions across the organization.
• Help declutter processes and workflows that are slowing delivery.
• Even help declutter the product — because sometimes there are simply too many features, and the real path to better customer engagement is simplification, not addition.

A scrum master who only looks inward at their team is only doing half the job. The other half is clearing the path around it.

The Bottom Line

So, who's responsible for a scrum team's performance?

Everyone owns their piece. But if you're asking who's accountable for whether the team as a whole is actually effective — the answer is the scrum master. That's what the 2020 Scrum Guide made explicit, and it's a useful clarity to hold onto the next time a team starts to drift.