Scrum master career path: from junior to agile coach and head of agile transformation
Each step up the agile ladder, from your first scrum master job to agile coach, enterprise agile coach and head of agile transformation: what changes in the job, the gap to close, how to show it on your CV and in interviews, and a realistic plan.
The cvscored team
Contents
The ladder at a glance
| Step | What you are measured on next | Typical time |
|---|---|---|
| Junior scrum master to scrum master | One team that runs Scrum well with your help | 1 to 2 years |
| Scrum master to senior scrum master | Two or three teams, or one hard one, and other scrum masters | 2 to 3 years |
| Senior scrum master to agile coach | Teams and their managers across a department | 2 to 4 years |
| Agile coach to enterprise agile coach | The leadership and structures of a large organisation | Several years |
| Enterprise agile coach to head of agile transformation | The organisation's whole change programme | After leading change at scale |
The steps up to senior scrum master
Junior scrum master to scrum master
What changes: you serve a team on your own. You run the events without help, notice what slows the team, and start to coach the product owner and the developers rather than tell them.
The gap: a deep reading of the Scrum GuideKnow the Scrum Guide well enough to explain the reason behind each event, and to adapt without losing it., facilitation of events that people value, KanbanVisualise the work, limit work in progress and manage flow; often used next to Scrum or instead of sprints. basics, a board in JiraSet up boards, workflows and simple reports in Jira so they show the work, without the tool running the team. that shows the real work, and questions that help people thinkAsk good questions, listen, and say hard things kindly; most of the job is conversation..
On the CV and in interviews: the team you served and one or two changes it made with you, such as sprint goals met more often. Expect a role play of a short retrospective and questions on the purpose of each event.
Plan (6 to 12 months, on the job): run every event for one team and ask for feedback after each; try a new retrospective format each month; keep an impediment list and close the oldest item; prepare for a scrum master certificate if your market names one.
Scrum master to senior scrum master
What changes: you serve two or three teams, or one in serious trouble, and other scrum masters come to you for advice. You work more outside the teams: on dependencies, on managers and on the way work arrives.
The gap: coaching rather than facilitating, flow measures and reading team dataRead flow data, such as cycle time and work in progress, to start a useful conversation, not to judge people., stakeholdersHelp the product owner work with stakeholders: reviews they attend, and requests that go through the backlog. who want different things, conflict between people, and the basics of scaling with SAFeThe Scaled Agile Framework for many teams on one programme: release trains, PI planning and its roles. or a lighter framework.
On the CV and in interviews: several teams and their results, a hard situation you helped resolve, and scrum masters you mentored. Expect questions on conflict, on velocity used badly by management, and on teams that depend on each other.
Plan (9 to 12 months): take on a second team; mentor a new scrum master; run a joint planning or review for teams that share a product; read a book on coaching and practise it in one-to-ones.
The steps up from senior
Senior scrum master to agile coach
What changes: you no longer belong to one team. You coach several teams, their scrum masters and product owners, and the managers around them, and you change how a department plans, funds and measures its work.
The gap: coaching of leaders, organisation design basics, training and workshops for groups, leading without authorityLead without authority: coach, facilitate and change the system around the team. across a department, and presenting changeRun a sprint review or a workshop that people want to attend, and keep it to time. to senior managers.
On the CV and in interviews: a department you helped change, what changed in figures, and the leaders you coached. Expect a case: a department wants to become agile in six months; what do you do first?
Plan (12 months or more): lead the agile change of one department with its manager; design and run a training for product owners; set up a community of practice for scrum masters; find a coach who coaches you.
Agile coach to enterprise agile coach
What changes: you work with the leadership of a large organisation on structures that teams cannot change: budgets, portfolio decisions, approvals, careers. You lead other agile coaches.
The gap: portfolio and funding models, scaling frameworks at the level of many trains or products, change management, the language of executives, and patience over years.
On the CV and in interviews: an organisation-wide change you shaped, how it was measured, and the coaches you led. Expect questions on resistance from leaders and how you measure an agile transformation.
Plan (several years): work with one executive on a structural change, such as funding teams instead of projects; lead a group of coaches; publish an honest internal review of what worked and what did not.
Enterprise agile coach to head of agile transformation
What changes: you own the change programme of the whole organisation: its goals, its budget, its coaches, and its report to the executive board. You answer for the outcomes, not for the methods.
The gap: running a large programme with a budget, hiring and leading a coaching team, choosing which frameworks to use where, and a seat among the senior leaders.
On the CV and in interviews: the scale of change you led, its business results, and the team you built. Expect a discussion of your first year: what you would measure and what you would stop.
Plan (several years): lead the change of a business unit end to end; own its budget; report the results to the board with numbers that matter to it, such as time to market.
Your CV for the next step
A step up the agile ladder shows on a CV as proof that you changed more than one team. Three rules:
- Leave past titles alone. Add the wider work as lines under each job.
- Use the next level's words. Senior wants "several teams", "mentored", "dependencies"; agile coach wants "department", "leaders", "training"; the top steps want "transformation", "portfolio", "executive".
- One result per line. Time to market, predictability, waiting time, people grown.
| Skill | Weak line | Strong line, with proof |
|---|---|---|
| Coaching leadersLead without authority: coach, facilitate and change the system around the team. | Coached managers. | Coached 5 department heads on funding teams instead of projects; 3 moved their budgets within a year. |
| Community of practice | Built an agile community. | Started a community for 14 scrum masters with monthly sessions; two new scrum masters ran teams alone within 6 months. |
| TrainingRun a sprint review or a workshop that people want to attend, and keep it to time. | Ran agile training. | Designed a 2-day product owner training run 8 times; refinement time across teams fell by a third. |
| Transformation | Supported the agile transformation. | Led the move of a 120-person department to product teams; release lead time fell from 3 months to 3 weeks. |
Key takeaways
- The ladder runs junior scrum master, scrum master, senior, agile coach, enterprise agile coach, head of agile transformation.
- Each step widens the circle: a team, several teams, a department, the whole organisation.
- From agile coach on, most of the work is with leaders and structures, not with teams.
- Proof is change that lasted, in figures, not events you ran.
- Write the proof in the next level's words, one result per line.
Frequently asked questions
- What comes after scrum master?
- Senior scrum master, then agile coach, then enterprise agile coach and head of agile transformation.
- How long does it take to become an agile coach?
- Often several years of serving teams, including more than one team at a time. What counts is change you can show across teams, not the years.
- Do I need a coaching certificate to move up?
- No certificate is required. Many agile coaches learn coaching through courses and supervised practice; proof of change across teams matters most in interviews.
- Is agile coach a management role?
- Usually not: an agile coach leads through influence. Head of agile transformation often does manage a team of coaches.
- What should the CV show for an agile coach role?
- A department or several teams you helped change, the leaders you coached, and results in figures.