Example · Scrum Master
Facilitation holds up well, but the Scrum Master title itself is at risk.
27 of your 40 hours still need you
- 21 stay yours
- 6 faster with AI
- 13 tools could take
A typical week at the middle pace. Your plan uses your own tasks.
Is scrum master a dying role?
By our task-by-task count, 27 of a typical 40-hour week as a scrum master still need a person. Tools could already take about 13 hours. The visible part of your week, 33% of it, is work models already do well, including the sprint report, the board tidying, the notes and the epic breakdown. If your Jira has Rovo, Atlassian's AI assistant, turned on, you have watched it break an epic into stories in one click.
Read more
The bigger thing is older and has nothing to do with AI. Companies have been folding this job into engineering managers since before today's tools existed. If a peer has left and not been replaced, or an engineering manager has started running their own standup, that is the risk to name first.
The work that holds is solid. You know which engineering manager to call. You get blockers moved when you outrank nobody, keep sprints from being raided and run rooms where people say the true thing. No model or dashboard does that. However, nobody writes a job posting for it, and when the Scrum Master title goes, the work is handed to whoever is left. This report is about making that work yours in writing, with a title the market still hires for, before the decision is made for you.
The hard truth
Scrum certificates are common, so results set you apart.
Scrum Alliance alone has issued more than 2 million credentials, the CSM among them. A certificate shows you know the framework.
Sources (1)
- Scrum Alliance says its community has passed 2 million professional credentials earned. Scrum Alliance press release via GlobeNewswire, 2026-06
What stays yours
Knowing who actually owns a thing across your squads
This rests on context. The real ownership map is in people's heads and in years of watching handoffs break. A model can read the Jira component field, but it cannot know that the component owner left and the person who actually answers sits on another squad.
Getting a blocker moved when you outrank nobody
This depends on relationships and context. The blocker clears because of a favor, a history and a well-timed ask. An agent can post the reminder, but nobody owes it a favor.
Facilitating a retro where someone says the true thing
This takes presence. People say the hard thing to a person they trust, in a room with norms that person built. AI notes can capture it afterward, but they can't make it happen.
Protecting a sprint from a mid-sprint raid
This takes context, and you answer for the team. You know which raids to let through and which to fight, and you fight them on the team's behalf. Nobody delegates that to software.
Turning a retro item into an actual change in how the team works
What protects this is context. Working agreements stick because of who proposed them and how they were negotiated. A model can draft the agreement, but it cannot make the senior engineer keep it.
What's next after scrum master?
Plan A is your best move inside the work you do now. Most sessions in the 13-week plan build toward it.
- A
Own cross-squad delivery risk: delivery manager or technical program manager
Why it fits
Why you. "Who actually owns a thing" across squads is the whole job of a technical program manager, and you already do it without the title. If you came from QA (software testing) or support, you can read a release risk from the inside; most program managers cannot.
The gap. You probably have no written dependency or risk register yet. The risk conversation is spoken and borrowed from a head of delivery. You track velocity but not cycle time. Nothing you know is on paper that anyone outside the squads can read.
The trade-off. You become the person whose name is on the date that slipped. It is more exposure, in writing, for the same pay until a title changes. Program management also involves more spreadsheet work than the job you like, and some weeks you will miss the retro.
Other moves that fit
These are also good bets in this field. Read them if Plan A doesn't suit you.
Product ownership: associate PM or product owner on one of your squads
Why it fits
Why you. Refinement prep with the PM is part of your week and you already draft the acceptance criteria. A QA or support background means you know what "done" has to prove.
The gap. You have no customer contact and no outcome you have owned yet, and the PM on your squad may not want a deputy.
The trade-off. Entry-level product is one of the most compressed hiring doors in the Canaries data, and associate PM postings often want a product portfolio you do not have. It is a valid path, but it is slower than the delivery move and depends on a PM's goodwill.
The hedge: release and change management
Why it fits
Why you. You have watched releases from the Scrum chair, and you may have a QA or support background. You know what breaks and which team it belongs to.
The gap. You are not yet on the change board, the group that approves releases, and you may not know who owns the change control, the audited rule for how releases get approved.
The trade-off. It is a smaller job than the one you have, with a lower ceiling, and if you came from QA it pulls you back toward the function you left on purpose. Keep it as a hedge.
What's a plan B for scrum masters?
Plan B is a job AI is creating that these skills already fit. One session a week in the plan trains you for it, so it is ready if your job shrinks or you want a change.
BPlan B, picked for this role
AI enablement and adoption lead
Your experience coaching teams through change carries straight into helping people adopt AI.
Other options
AI product owner
Your daily work with backlogs, working agreements and Agile ceremonies is most of this job.
AI workflow builder
Your eye for blockers and cycle time helps you spot the slow, repetitive steps worth rebuilding.
In your own plan you can switch to any of the 47 roles.
The first two weeks
The first 2 of 13 weeks. Three sessions a week: 30 minutes on Monday, 60 on Wednesday and 60 on Friday. Every session ends in something written or a number. The plan is built around a delivery ledger: you write down the dependencies, risks and decisions you already carry in your head, one sprint at a time. You also do one 40-minute Plan B session a week. By week 13 you'll have a working risk register with named owners, a two-page evidence pack with four before and after numbers, and one outside application sent.
- Week 1: Measure your week
What you do
- AKeep a time log for one week and compare it with the task list in this report.
- AFor each squad's last six sprints, count work committed and delivered, carryover (unfinished work moved to the next sprint) and work added mid-sprint.
- AList every blocker you escalated last quarter, who held it, how long it sat and what moved it.
- BTake the first half of Anthropic's AI Fluency course, a free online class.
- Week 2: Find who owns what
What you do
- AAsk your head of delivery in writing who is accountable for release risk on your squads, and who sits on the change board, the group that approves releases.
- AFind out whether your company is audited under SOC 2 or SOX, two common security and finance audits, and who owns the change management control.
- AMap every service your squads touch, with its owner in Jira, the team's tracking tool, next to the person who really owns it. Count the mismatches.
- BFinish AI Fluency and pass its final assessment.
Three courses from the plan
Checked 2026-10-11.
- Certified ScrumMaster (CSM)Scrum Alliance · $250 to $2,495, trainer-set; the range on the provider's page is dated October 2023
If you have it, keep renewing it only while a posting you want lists it. Do not buy a second course.
- Professional Scrum Master I (PSM I)Scrum.org · $200 per attempt
Only if a posting demands it and you do not already hold CSM. Its only advantage is that it costs less than renewing CSM for life.
- Professional Scrum Master II (PSM II)Scrum.org · $250 per attempt
No. It goes deeper into the same category.
Risks beyond AI: highRole-fold risk
This risk outranks the AI one, and no model is involved. Companies have been eliminating dedicated Scrum Master and agile coach seats and handing the duties to engineering managers and product managers since well before any agent could break down an epic. Capital One cut about 1,100 roles in its agile job family in January 2023 and said the duties would move into existing engineering and product positions. We score this separately because blaming AI for it would get the remedy wrong.
Where this could be wrong
- Facilitation may be less durable than we scored. We gave it a low capability score because no model runs a room. If your squads are remote-first and standups are async updates in chat, the ceremony is already a document, and that task becomes more exposed.
- The decision to fold the role into other jobs may already be made. If your head of delivery has a headcount target for next year, the Week 12 ask won't change it, and the plan should run Weeks 10 to 13 first. Ask in Week 2, directly.
- The market signals are thin. Capital One is one company, the UK postings series is small and noisy, and the training-business numbers come from one vendor's own classes. We weighted the direction more than the size. A US Scrum Master postings series would change our confidence, but probably not the conclusion.
- The delivery move assumes the engineering managers do not want delivery risk. Some do. If they claim the risk register work in Week 4 and keep it, your path to the title runs outside, and the Week 13 application matters more than the Week 12 memo.
Also matched: scrum master, agile delivery lead, agile coach. Research checked 2026-10-11. Page updated .