Example · Scrum Master
68% of your week as a scrum master is still yours.
AI now writes sprint reports and breaks down epics. Helping a team work well together stays with you.
Make my planA typical week at the middle pace. Your plan uses your own tasks.
Is scrum master a dying role?
In a typical week at the middle pace, 53% of this work needs your judgment and 15% is work you do using AI. AI could do about 32%. 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 week, task by task
Who does each hour of a typical 40-hour week.
See every task
Needs your judgment.
- Facilitating the live ceremonies: standup, planning, review, retro18%
- Impediment removal: chasing blockers across teams, escalating10%
- Retro follow-through: turning items into working agreements and real change7%
- Coaching individuals: 1:1s, conflict, the quiet conversation after a bad retro7%
- + 2 smaller tasks10%
AI does the slow parts. You still own it.
- Refinement prep: drafting acceptance criteria and splitting stories with the PM8%
- Onboarding new team members to the process; agile training4%
- Jira administration: workflow config, automation rules3%
AI could do most of it.
- Sprint reports and metrics: velocity, burndown, status updates to leadership12%
- Board hygiene: tidying tickets, breaking epics into stories, backlog grooming prep10%
- Meeting notes, action items, retro write-ups, wiki pages6%
- Scheduling, calendar logistics, cross-team dependency spreadsheets5%
Why some tasks still need a person
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.
Good to know
What is hard about this field, and what you can do about it.
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's next after scrum master?
Plan A is the best move inside the work you do now.
Grow in the job you have
The main focus. Most weekly sessions build toward it.
- Each week
- 4 sessions
- Ready in
- About 4 weeks to a working risk register
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.
2 other moves that fit
- Product ownership: associate PM or product owner on one of your squadsReady in about 8 weeks for the pspo i product owner exam
- The hedge: release and change managementReady in about 2 weeks to find the change control owner
What's a plan B for scrum masters?
Plan B is meant to be different from this job. It was picked because skills from this role carry over.
Get ready for a new kind of job
A second option. A newer job AI is creating that these skills already fit.
Your work running scrums and coaching teams through change is what AI rollouts need most.
- Each week
- 1 session
- Outlook
- Hiring now
- Pay
- $150K to $180K a yearOne Beacon Hill posting in King of Prussia, PA, March 2026, asking for 5+ years.
2 other options
- AI enablement and adoption leadYour experience coaching teams through change carries straight into helping people adopt AI.
- AI product ownerYour daily work with backlogs, working agreements and Agile ceremonies is most of this job.
In your own plan you can switch to any of the 47 roles.
The 13 weeks
Small steps that add up. One plan for both: most sessions build Plan A, one a week builds Plan B.
By week 13 you will have
AFor Plan A
- A working risk register with named owners
- A two-page evidence pack with four before and after numbers
- One outside application sent
BAnd for Plan B
- A plan for measuring adoption
- An AI rollout readiness pack for your portfolio
- 1Measure your week
- 2Find who owns what
- 3Measure cycle time
- 4Start a risk register
You finish withA shared register link and a list of who opened it
- 5Let tools draft the status
- 6Call a risky date
- 7Test product ownership
- 8Run a cross-squad standup
You finish withAttendance and the register rows that changed
- 9Make a second risk call
- 10Check the job market
- 11Build your evidence pack
- 12Make your ask
- 13Apply and choose your path
You finish withA one-paragraph decision on your next move
Three courses from the plan
- 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.
Checked 2026-10-11.
The fuller picture
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 .