Agile Coach vs. Scrum Master: What's the Difference?
The Scrum Guide makes the Scrum Master accountable for a Scrum Team's effectiveness. Here is how that overlaps with an agile coach, where it differs, and which you need.
The Agile Coach · Last reviewed October 21, 2026 · 5 min read
People often use "Scrum Master" and "agile coach" as if they were the same thing, and job postings blur the line even further. There is real overlap: both roles help teams improve, both facilitate, and both coach. But one is defined by a specific framework and the other is not, and that difference matters when you are deciding what a team actually needs.
This guide starts with what the official Scrum Guide says about the Scrum Master, then compares the two roles side by side and finishes with practical questions to help you decide.
What the Scrum Guide Says
The Scrum Guide, written by Ken Schwaber and Jeff Sutherland, is the official definition of Scrum. The current edition, published in 2020, says that "Scrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and the Scrum Master." The guide uses the word accountability rather than job title on purpose: it describes responsibilities, not positions on an org chart.
Two sentences carry most of the weight for the Scrum Master. The guide says the Scrum Master "is accountable for establishing Scrum as defined in the Scrum Guide," and that the Scrum Master "is accountable for the Scrum Team's effectiveness." It also describes Scrum Masters as "true leaders who serve the Scrum Team and the larger organization."
The guide then lists the ways a Scrum Master serves three groups.
- The Scrum Team, for example by "coaching the team members in self-management and cross-functionality" and "causing the removal of impediments to the Scrum Team's progress."
- The Product Owner, for example by "helping find techniques for effective Product Goal definition and Product Backlog management."
- The organization, for example by "leading, training, and coaching the organization in its Scrum adoption."
Notice how far that reaches beyond running meetings. On paper, a Scrum Master already coaches individuals, the team and the wider organization.
Where the Two Roles Overlap
A lot of the day-to-day work looks the same. Both roles move between teaching, facilitating, mentoring and coaching. Both focus on how effectively a team works rather than on assigning tasks. Both help surface impediments and get them removed. And both, when done well, influence the organization around the team, not just the team itself.
In other words, a strong Scrum Master who is doing the full job described in the Scrum Guide is, in effect, an agile coach working inside the Scrum framework. The differences are about scope, position and definition rather than about the kind of skills involved.
Where They Differ
The main differences show up in five areas.
- Framework. The Scrum Master accountability exists only within Scrum. An agile coach is not tied to any one framework and may work with teams using Scrum, Kanban, a hybrid or no named method at all.
- Membership. The Scrum Master is a member of the Scrum Team. Agile coaches often sit outside any single team and support several teams or leaders.
- Depth versus breadth. A Scrum Master usually goes deep with one team. A coach more often works across multiple teams, or with leadership on organization-wide issues.
- Formal definition. The Scrum Master is defined in the Scrum Guide. "Agile coach" has no single official definition, so expectations vary widely between employers.
- Duration. A Scrum Master is part of the team for as long as it uses Scrum. Coaching engagements are often time-bound, with an explicit goal of building internal capability.
Because "agile coach" is loosely defined, always ask what a particular organization means by it. Some use it for an experienced Scrum Master, others for an organizational change consultant.
Common Misconceptions
A few misunderstandings come up again and again.
The first is that a Scrum Master is a junior agile coach. The Scrum Guide does not frame the role that way, and the accountabilities it lists, including coaching the organization in its Scrum adoption, are demanding. Some people do move from Scrum Master to coach roles, but that is a career path, not a definition.
The second is that the Scrum Master is the team's project manager or note taker. The guide gives the Developers accountability for "creating a plan for the Sprint, the Sprint Backlog," and the Product Owner accountability for the Product Backlog. The Scrum Master helps the team work effectively but does not direct the work.
The third is that hiring an agile coach removes the need for a Scrum Master. If a team uses Scrum, the Scrum Guide still expects someone to hold the Scrum Master accountability. A coach can support that person, but does not replace the accountability.
Which One Does Your Team Need?
There is no universal answer, but these questions help.
- Is the team using Scrum, or planning to? If so, it needs someone holding the Scrum Master accountability.
- Are the main problems inside one team, or between teams and the wider organization?
- Is the team new to agile ways of working, or experienced but stuck on a plateau?
- Does the organization use several different approaches across teams?
- Is there someone inside the organization who could grow into the role with support?
Two hypothetical situations show how the answers play out. A single product team adopting Scrum for the first time, with mostly team-level problems, is usually well served by a capable Scrum Master who has time to focus on the team. A company with fifteen teams, inconsistent practices and recurring cross-team dependencies may benefit from an enterprise-level coach working with leaders, alongside Scrum Masters embedded in the teams.
Many organizations end up with both. In that arrangement, coaches often focus on developing Scrum Masters and leaders, while Scrum Masters focus on their teams.
Making the Two Roles Work Together
When both roles exist, a little clarity prevents a lot of friction. Agree on who coaches whom, for example with the coach mentoring Scrum Masters and Scrum Masters coaching their teams. Avoid giving a team conflicting advice from two directions. Share observations privately before raising them in front of the team. Above all, the coach should strengthen the Scrum Master's position with the team, never bypass it.
Key takeaways
- The 2020 Scrum Guide makes the Scrum Master accountable for establishing Scrum and for the Scrum Team's effectiveness, serving the team, the Product Owner and the organization.
- Agile coaches use the same core skills but are not tied to a framework and often work across teams or with leadership.
- "Agile coach" has no single official definition, so clarify what an organization means by it.
- A team using Scrum still needs someone in the Scrum Master accountability, even if a coach is also present.
Sources
Spotted something out of date? Let us know.