Most organizations hire based on the title they've heard most often, not the problem they're actually trying to solve. That's how a company with a broken engineering culture ends up hiring a Scrum Master to run standups, or a single ten-person team ends up paying for an Agile Coach to do work a Scrum Master could handle for a third of the cost.
The two roles overlap in vocabulary — sprints, retrospectives, velocity, ceremonies — but they operate at completely different altitudes. Here's how to actually tell them apart, and which one solves the problem you have.
What a Scrum Master Actually Does
A Scrum Master is a team-level role, embedded with a single Scrum team, focused on making that team's delivery process work smoothly.
Core responsibilities:
Facilitating Scrum ceremonies: sprint planning, daily standups, sprint review, retrospectives Removing blockers that are stopping the team from delivering this sprint Protecting the team from scope creep and interruption during a sprint Coaching the team on Scrum mechanics — how to write good user stories, how to estimate, how to run a healthy retro Tracking and surfacing team-level metrics: velocity, burndown, cycle time
A Scrum Master is the right hire when:
You have one or a few teams already using Scrum, but ceremonies are messy, unfocused, or skipped Sprints regularly fail to deliver what was planned, and no one owns figuring out why The team has a process but not the discipline to run it well You need someone hands-on, in the day-to-day, every single sprint What an Agile Coach Actually Does
An Agile Coach is an organizational-level role, working across multiple teams, leadership, and sometimes the whole company, focused on whether the organization's structure supports agile delivery at all.
Core responsibilities:
Diagnosing why multiple teams are slow, siloed, or delivering low-quality work — often a structural or cultural problem, not a ceremony problem Coaching leadership on how to fund, structure, and measure agile teams (this is usually the actual bottleneck, not the engineers) Designing or fixing team topology — who owns what, how teams depend on each other, where handoffs create delay Introducing and adapting scaling frameworks (SAFe, LeSS, or a custom hybrid) when a single-team Scrum setup no longer fits Building agile capability that outlasts their own engagement — a good Agile Coach works to make themselves unnecessary
An Agile Coach is the right hire when:
You have multiple teams and the problems are between teams, not within one Leadership itself doesn't understand or support agile ways of working, and that's the actual blocker You're scaling from one team to many and don't have a structure for it yet Previous attempts at "going agile" stalled because of politics, incentives, or org design — not because ceremonies were run badly The Test: Where Does the Pain Actually Live?
Ask this one question before you write a job description: is the problem inside a team, or between teams and leadership?
Symptom Points To Standups run long and off-topic Scrum Master Sprint commitments are missed most sprints Scrum Master Retros happen but nothing ever changes Could be either — depends on whether the team lacks discipline (Scrum Master) or lacks authority to act on findings (Agile Coach) Two teams keep blocking each other on dependencies Agile Coach Leadership still funds and measures work in a waterfall way despite teams "doing Scrum" Agile Coach You're scaling from 1 team to 5+ and don't know how to structure it Agile Coach A single team's velocity is inconsistent sprint to sprint Scrum Master A Common Mistake: Hiring an Agile Coach to Fix a Scrum Master Problem
This happens constantly, and it's expensive. A company with one struggling team hires an Agile Coach — a senior, org-wide role — to fix what is actually a basic facilitation and discipline problem. The coach spends months in meetings meant for a single team's daily mechanics, leadership sees no organizational change because there was never an organizational problem, and the engagement gets written off as "agile coaching doesn't work here."
The inverse mistake is just as common: hiring a Scrum Master to fix cross-team dependency chaos or a leadership funding model that punishes iterative delivery. No amount of well-run standups fixes a structural problem.
Can One Person Do Both?
In smaller organizations, yes — often as a fractional or part-time engagement rather than one full-time role trying to do both jobs at once for a large org. A single practitioner can run Scrum Master duties for one or two teams while also advising leadership on structure, as long as the scope stays proportional to the size of the organization. What doesn't work is expecting one full-time Scrum Master, hired at Scrum Master compensation and scope, to also fix organizational design problems on the side — that's an Agile Coach's job, and it deserves being scoped and resourced as one.
The Bottom Line
If the pain is inside a single team's sprint execution — messy ceremonies, missed commitments, unclear stories — hire a Scrum Master. If the pain is between teams, or between engineering and leadership, or you're trying to scale agile practices across an organization that was never structured for it — that's an Agile Coach's problem to solve. Hiring the wrong one for your actual bottleneck doesn't just waste budget; it can convince leadership that "agile doesn't work here" when the real issue was a role mismatch from day one.
If you're not sure which one your organization actually needs, that diagnosis itself is worth getting right before you write the job description.
Book a free 30-minute consultation and I'll help you figure out exactly where your bottleneck lives before you hire for it.