Scrum Master vs Agile Coach vs Delivery Manager: The Agile Title Mess (And Why These Jobs Are Disappearing)

In 2023, I saw 15,000+ Scrum Master job postings on LinkedIn. In 2026, there are fewer than 5,000. What happened?

I'll tell you what happened, because I watched it in real time. I was working with a mid-size fintech company in 2023 that had four Scrum Masters for six engineering teams. They also had an Agile Coach — a senior person whose job was to "drive organizational agility transformation." The Agile Coach ran workshops. The Scrum Masters ran standups, retros, and sprint planning. The engineering managers ran... the actual teams. By late 2024, three of the four Scrum Masters had been laid off. The Agile Coach's contract wasn't renewed. The engineering managers absorbed the ceremonies into their weekly rhythm. Nobody missed the old structure. The teams actually moved faster.

This isn't a one-company story. It's an industry-wide correction that's been building for years, and it's forcing thousands of agile practitioners to rethink their careers. The question isn't whether Agile is dead — it isn't. The question is whether dedicated agile roles are dying. And the honest answer is: many of them are.

If you're a Scrum Master, an Agile Coach, or someone considering these career paths, this article is going to be uncomfortable but necessary. I'm going to walk through what each role actually does, what the market data says, why the decline is happening, and — most importantly — what to do about it.

The Numbers First

Let's start with the salary and market data, because the numbers tell a story that job titles alone can't.

According to Glassdoor's 2025-2026 salary data, the average Scrum Master salary in the United States sits between $108,000 and $126,000, depending on location and experience level. That's not bad — but it's been essentially flat for three years. In 2023, the range was $105,000–$125,000. Compare that to Product Manager salaries growing 8–12% over the same period, and you start to see the problem: the market is telling you that Scrum Master skills are becoming commoditized.

Built In's data corroborates this, showing average Scrum Master compensation around $113,000–$128,000 across major US tech hubs, with significant variation. A Scrum Master in San Francisco might earn $135K; the same role in Austin might pay $95K. But the more important data point from Built In is volume: the number of Scrum Master postings on their platform has dropped roughly 40% since 2023.

For Agile Coaches, the picture is even more stark. Humanizing Work's research shows that only 18% of organizations hire dedicated Agile Coaches — and that number has been shrinking, not growing. When organizations do hire Agile Coaches, they pay well: $130,000–$175,000 for experienced coaches, with some enterprise-level coaches earning above $200K. But the jobs are rare, the contracts are often short-term, and the first budget line cut during layoffs is "agile transformation consulting."

Delivery Managers, by contrast, are on the rise. Program Strategy HQ's salary data shows Delivery Manager compensation ranging from $110,000 to $160,000, with senior Delivery Managers at large tech companies earning $170K–$200K+. More importantly, the number of Delivery Manager job postings has increased roughly 25% year-over-year since 2024. Companies are consolidating agile facilitation, project management, and execution accountability into one role — and calling it Delivery Manager.

The Scrum Alliance's own research shows that while Scrum remains the most popular agile framework (used by ~58% of agile teams), the percentage of teams using Scrum with a dedicated Scrum Master has dropped from about 54% in 2020 to around 37% in 2025. Teams are still doing Scrum — they're just not hiring a separate person to run it.

What Each Role Actually Does (In Practice, Not Theory)

Part of the problem with agile roles is that the theoretical descriptions sound important, but the day-to-day reality often doesn't match. Let me break down what each role looks like in practice.

Scrum Master: The Ceremony Facilitator

In theory, a Scrum Master is a "servant leader" who helps the team follow Scrum practices, removes impediments, shields the team from distractions, and coaches the team toward continuous improvement. The Scrum Guide describes the role in almost spiritual terms — the Scrum Master is accountable for the team's effectiveness and serves the broader organization by leading and coaching agile adoption.

In practice, here's what most Scrum Masters actually do day-to-day:

• Run ceremonies: Sprint planning, daily standups, sprint reviews, and retrospectives. This takes 5–8 hours per week for a single team.
• Update Jira: Maintain the backlog, update sprint boards, generate velocity reports and burndown charts. Another 3–5 hours per week.
• Remove impediments: This is the high-value work — escalating blockers, coordinating with other teams, unblocking dependencies. In practice, this takes 2–4 hours per week, and a lot of it overlaps with what an engineering manager already does.
• Coach the team: Running retro action items, introducing new practices, facilitating team agreements. Maybe 2–3 hours per week in an established team.

Add it up, and you get roughly 12–20 hours of actual work per week for a single-team Scrum Master. This is why many companies assign Scrum Masters to 2–3 teams — and why many eventually ask: couldn't the engineering manager or tech lead just... do this?

Agile Coach: The Organizational Transformer

An Agile Coach operates at a higher level than a Scrum Master. Where a Scrum Master works with one or two teams, an Agile Coach works across the organization. Their mandate is typically:

• Assess organizational agility: Evaluate how teams work, identify bottlenecks, recommend structural changes.
• Coach leaders: Work with VPs, directors, and C-suite to adopt agile mindsets and practices.
• Design processes: Create frameworks for how multiple teams coordinate — especially relevant in scaled agile (SAFe, LeSS, Nexus).
• Train: Run workshops, certifications, and training programs for teams and leaders.
• Measure: Define and track agile maturity metrics, team health, delivery metrics.

The problem? "Organizational transformation" is nebulous. It's hard to measure. And after 2–3 years of coaching, most organizations either feel "transformed enough" or conclude the transformation didn't work. Either way, the Agile Coach's engagement ends. This is why Humanizing Work notes that many Agile Coaches work on contract or consulting basis — the role is inherently temporary.

Delivery Manager: The Accountable Executor

The Delivery Manager role is newer and less standardized, but it's eating the Scrum Master and Agile Coach roles alive. Here's what Delivery Managers typically own:

• End-to-end delivery: They're accountable for getting features and projects shipped on time, not just for facilitating the process.
• Cross-team coordination: Managing dependencies between 3–6 teams, running program-level ceremonies, maintaining roadmaps.
• Risk management: Identifying delivery risks early, escalating to leadership, creating mitigation plans.
• Stakeholder communication: Regular status updates to business stakeholders, product leadership, and executives.
• Process improvement: Continuously improving how teams work — but with an explicit focus on delivery outcomes, not agile purity.

The key difference? Accountability. A Scrum Master facilitates. A Delivery Manager is on the hook for outcomes. When a project is late, nobody asks the Scrum Master why. They ask the Delivery Manager. This accountability is why companies are willing to pay more for the role — and why it's growing while pure agile roles shrink.

The Comparison: Side by Side

The Decline: What's Actually Happening

The decline of dedicated agile roles isn't happening in a vacuum. It's driven by several converging forces.

1. The Big Tech Layoffs Targeted Agile Roles

When Meta cut 11,000 jobs in late 2022 and another 10,000 in 2023, entire categories of roles were eliminated — and agile roles were disproportionately hit. Amazon's 27,000-person layoff wave in 2023 similarly targeted program managers and agile coaches across AWS and retail divisions. Google's 2024 restructuring eliminated hundreds of program management and agile facilitation roles.

The pattern was consistent: when companies needed to cut costs, they looked at roles that facilitated work versus roles that produced work — and agile practitioners were categorized as the former. Right or wrong, this sent a powerful signal to the rest of the industry.

2. Engineering Managers Absorbed the Work

As companies eliminated Scrum Masters, the work didn't disappear — it got redistributed. Engineering managers picked up sprint planning and retros. Tech leads started running standups. Product managers took ownership of backlog refinement. And the uncomfortable truth emerged: most of it was already part of their jobs anyway.

Atlassian's team practices survey found that in teams without a dedicated Scrum Master, 67% of agile facilitation work is done by the engineering manager, 22% by the tech lead, and 11% by the product manager. Teams adapted. Many adapted quickly.

3. The Anti-Process Backlash

There's a growing sentiment in the tech industry — especially among senior engineers and engineering leaders — that agile processes have become the very bureaucracy they were designed to eliminate. The original Agile Manifesto valued "individuals and interactions over processes and tools." But somewhere along the way, Agile became synonymous with more processes and more tools: SAFe ceremonies, PI planning, multiple levels of standup, story point debates, velocity tracking.

When developers spend more time in ceremonies than coding, something has gone wrong. And the backlash has been fierce. Posts like "Agile is Dead" regularly go viral on LinkedIn. While most of these are clickbait oversimplifications, they reflect a real frustration that dedicated agile roles sometimes create process overhead rather than reducing it.

4. AI Tools Are Eating Administrative Work

A significant chunk of what Scrum Masters do — updating boards, generating reports, tracking metrics, writing sprint summaries — is increasingly automated. Tools like Jira's AI features, LinearB, and Jellyfish can automatically track sprint progress, identify bottlenecks, generate velocity reports, and flag at-risk stories. When the tooling handles the administrative work, the remaining human value of the Scrum Master role shrinks further.

Is Agile Dead?

No. And anyone telling you it is doesn't understand what's happening.

Agile practices — iterative development, continuous delivery, cross-functional teams, regular retrospectives, customer feedback loops — are more widespread than ever. The Digital.ai State of Agile Report consistently shows that agile adoption continues to grow, with 90%+ of software organizations using some form of agile practices.

What's dying is the idea that you need a dedicated person whose entire job is agile facilitation. Agile is becoming a skill that's expected of all managers and leads, not a specialization that justifies its own headcount. It's similar to what happened with "webmaster" in the early 2000s — the work didn't disappear, but it got absorbed into other roles (frontend developer, backend developer, DevOps, etc.).

There are exceptions. Very large organizations running SAFe (Scaled Agile Framework) at scale still need Release Train Engineers (essentially Scrum Masters for programs of programs). Complex regulatory environments — healthcare, finance, defense — still value dedicated process roles. And genuine Agile Coaches who can drive organizational change at the executive level remain in demand, though the bar is much higher than it was five years ago.

But for the average Scrum Master running standups for two teams at a mid-size tech company? That job is disappearing, and no certification is going to bring it back.

The Controversy: "Scrum Masters Were Never Necessary"

Here's where I'm going to make some people angry.

There's a school of thought — and it's growing — that says Scrum Masters were always a solution in search of a problem. The argument goes: competent engineering teams don't need a separate person to facilitate their meetings. Competent engineering managers can remove impediments and coach their teams. And the Scrum Master role, at its worst, created a class of process police who slowed teams down while claiming to speed them up.

The counter-argument — and it has merit — is that engineering managers are already overloaded. They're doing 1:1s, performance reviews, hiring, architecture decisions, stakeholder management, and technical mentoring. Adding ceremony facilitation and process coaching on top of all that means something suffers. A dedicated Scrum Master lets the EM focus on people and technology while someone else focuses on process.

Both sides have valid points. But the market has spoken: most companies have decided that the overhead of a dedicated process role isn't worth the benefit. The engineering manager can run the standup in 12 minutes. The team can facilitate their own retro. The product manager can manage the backlog. And the Scrum Master's salary — $110K+ in the US — is better spent on another engineer who can actually build things.

Is this short-sighted? Maybe. Some teams will suffer from worse process hygiene, fewer retros, and less focus on continuous improvement. But for every team that suffers, there are three teams that discover they were doing fine without a dedicated process person all along.

The uncomfortable truth is that the best Scrum Masters — the ones who genuinely transformed teams and drove measurable improvement — were always rare. Most Scrum Masters were okay. They kept the ceremonies running and the Jira board updated. That was useful but not essential. And "useful but not essential" is the first thing cut in a downturn.

Salary Ranges: The Full Picture

Sources: Glassdoor, Levels.fyi, Built In, Program Strategy HQ

Note how the Scrum Master has the lowest ceiling of all these roles. It's the only one where senior compensation rarely breaks $150K. Every other role listed has a credible path to $200K+. This is a career architecture problem, not just a market timing problem.

What to Do If You're a Scrum Master

If you're currently a Scrum Master — or an Agile Coach — and you're reading this with a sinking feeling, don't panic. Your skills are transferable. But you need to be intentional about where you take them.

Option 1: Pivot to Product Management

This is the most natural transition for Scrum Masters who enjoy working closely with engineering teams and understanding customer needs. You already know how to facilitate discovery, manage backlogs, and think in terms of iterative delivery. What you need to add: customer research skills, data analysis, business metrics, and the ability to say "no" to stakeholders (which is harder than it sounds).

The salary uplift is meaningful: mid-level Product Managers earn $125K–$165K, and the career ceiling is much higher. A VP of Product can earn $250K–$400K+ at a mid-size to large company.

How to make the transition: Start by volunteering to run product discovery sessions alongside your PM. Take a course in product analytics (Reforge is excellent for this). Build a portfolio of product decisions you've influenced, even from the SM seat. Apply for Associate PM or PM roles at companies where your agile background is valued — enterprise software companies, particularly.

Option 2: Pivot to Delivery Management

This is the most direct lateral move. You're already doing half the Delivery Manager job. The gap is in accountability and scope: Delivery Managers own outcomes across multiple teams, manage program-level risks, and communicate status to executives. You need to step up from "facilitating the process" to "owning the result."

How to make the transition: Start by asking to manage cross-team dependencies and program-level reporting. Volunteer to present delivery status to leadership. Learn program management fundamentals — especially risk management, dependency mapping, and executive communication. The PgMP (Program Management Professional) certification from PMI is valuable here.

Option 3: Pivot to Program Management

Program Management is a step above Delivery Management and a strong fit for Agile Coaches who are used to working across the organization. Program Managers at companies like Google, Amazon, and Microsoft earn $160K–$250K+ and are deeply embedded in how the company ships products.

The transition requires adding skills in: strategic planning, portfolio management, vendor management, budget oversight, and executive stakeholder management. But your agile background gives you a strong foundation in iterative delivery and cross-team coordination.

Option 4: Go Technical

If you came from a technical background (many Scrum Masters were developers or QA engineers), consider going back. The market for software engineers and SDETs is far healthier than the market for Scrum Masters. You'll need to brush up on your technical skills, but a developer with 3–4 years of hands-on experience plus agile process knowledge is a compelling profile for many teams.

Certifications: Which Ones Still Matter?

The agile certification landscape is a mess. There are dozens of certifications from competing organizations, and their value varies enormously. Here's my honest assessment.

My honest advice: Don't invest in more Scrum Master certifications unless you have a specific reason. If you already have CSM, getting A-CSM or CSP-SM won't change your career trajectory. Instead, invest in certifications that open new career paths: PMP for Delivery/Program Management, or product management courses (PSPO from Scrum.org, or Reforge programs) for the PM pivot.

What I Actually Think

I've watched this shift for three years now, and here's my honest, unfiltered take.

The Scrum Master role, as it's been practiced at most companies, was always partially an illusion. It took the legitimate insight that teams benefit from process facilitation and coaching, and turned it into a full-time job that often didn't have enough meaningful work to fill 40 hours a week. The best Scrum Masters were exceptional — they genuinely transformed teams, built psychological safety, and accelerated delivery. But "the best" was maybe 15–20% of the population. The rest were meeting facilitators with a certification.

Agile Coaching was similarly inflated. Real organizational transformation requires someone with deep business context, executive credibility, and the ability to change incentive structures — not just someone who can run a SAFe PI Planning session. Most "Agile Coaches" were senior Scrum Masters with a fancier title, not organizational change agents.

The market correction we're seeing is painful but healthy. It's pushing agile practitioners to develop broader skills — product thinking, delivery accountability, technical depth, executive communication — that make them genuinely valuable regardless of what the role is called.

If you're a Scrum Master reading this: the sky isn't falling, but the ceiling is lowering. You have transferable skills that are genuinely valuable. But you need to package them differently and aim for roles with higher impact and accountability. The era of "I facilitate and coach" as a complete job description is ending. The future belongs to people who facilitate AND deliver, who coach AND own outcomes, who understand process AND product.

Don't mourn the Scrum Master title. Evolve past it.

Decision Framework: Which Path Is Right for You?

Use this framework to decide where to take your career if you're currently in an agile role:

The Bottom Line

Agile isn't dead. It's been absorbed. The practices won — iterative development, continuous delivery, cross-functional teams, and retrospectives are industry standard. But the dedicated roles that were created to teach those practices are no longer needed at the same scale, because the practices are now just... how we work.

If you're a Scrum Master or Agile Coach, this is your pivot moment. The skills you have — facilitation, coaching, process design, continuous improvement — are valuable. But they're not enough on their own anymore. You need to pair them with delivery accountability, product thinking, or technical depth. The practitioners who do this will thrive. The ones who double down on pure agile facilitation will find an increasingly small market for their services.

The agile title mess is cleaning itself up. The question is whether you'll be part of the cleanup or caught in it.

Sources

• Glassdoor — Scrum Master Salary Data
• Built In — Scrum Master Compensation
• Humanizing Work — Agile Coaching Salary Guide
• Program Strategy HQ — Delivery Manager Salary
• Scrum Alliance — Agile Research and Reports
• Scrum Guide (2020 edition)
• Digital.ai — State of Agile Report
• Scaled Agile Framework (SAFe)
• Agile Manifesto
• Atlassian — Agile Team Practices
• Scrum.org — PSM Certification
• PMI — PMP Certification
• Levels.fyi — Compensation Data

BirJob.com aggregates thousands of job listings across Azerbaijan and beyond — including Scrum Master, Delivery Manager, Product Manager, and engineering roles. Whether you're pivoting or doubling down, start your search at birjob.com.

You might also like

• AI Engineer vs ML Engineer: What Actually Changed and Why It Matters
• The Analytics Role Confusion: Business Analyst, Data Analyst, BI Analyst — What's the Actual Difference?
• DevOps vs SRE vs Platform Engineer: The Infrastructure Title Mess, Explained
• Product Manager vs Project Manager vs Program Manager: A Guide for People Who Can't Tell Them Apart