Scrum master CVs have a structural problem that most candidates never solve: the role is facilitation and coaching, not delivery — which means the CV cannot simply list features shipped or systems built. The temptation is to describe the ceremonies ("facilitated sprint planning, retrospectives, and daily standups", "managed the backlog with the product owner", "removed impediments") and treat that as evidence of performance. It isn't. Every scrum master facilitates ceremonies. The evidence that matters is what changed because you were in the room: did team velocity improve, did sprint predictability increase, did cycle time fall, did a specific team dysfunction get identified and resolved? Those outcomes are measurable, and they are what separates a scrum master CV that shortlists from one that describes a job title. The second structural issue is certification placement: CSM, PSM, and SAFe certifications are the primary filter signals for scrum master applications — they belong in the headline, not the footer. This guide covers the metrics, keywords, and bullet patterns that make a scrum master CV work.

What Scrum Master Job Descriptions Require in 2026

Scrum master JDs have evolved. The pure ceremony-facilitator role is under pressure as many engineering organisations expect teams to self-organise at the ceremony level. What JDs increasingly screen for is coaching depth, metrics fluency, and the ability to operate at scale.

Core requirements across the majority of scrum master JDs in 2026:

  • Agile coaching capability — the ability to diagnose team dysfunction, introduce targeted improvements, and coach team members on Agile principles rather than just enforcing process. JDs increasingly use "Agile coach" language for senior SM roles and expect evidence of behavioural change in teams, not just ceremony compliance.
  • Agile metrics ownership — velocity tracking, burndown chart analysis, cycle time and lead time measurement, sprint predictability (planned vs. completed), and WIP limit management. Scrum masters who understand and use these metrics to drive coaching decisions are operating at a different level from those who only view them as reporting artefacts.
  • Impediment management — identifying, escalating, and resolving blockers that span beyond the team boundary (dependencies on other teams, organisational process blockers, resource constraints). Senior SM roles list "organisational impediment removal" and "stakeholder alignment" explicitly.
  • Scaling Agile — SAFe (Scaled Agile Framework), LeSS (Large-Scale Scrum), or Nexus. Programme-level and enterprise-level Agile experience is increasingly expected for senior scrum master and RTE (Release Train Engineer) roles. PI Planning facilitation appears in SAFe-specific JDs.
  • Tooling — Jira (dominant), Azure DevOps (Microsoft-stack organisations), Linear (tech companies), and Miro or MURAL for distributed retrospectives and planning events. Name the specific tools you've used.
  • CSM or PSM certification — Certified Scrum Master (Scrum Alliance) and Professional Scrum Master (Scrum.org) are the baseline. PSM II/III and SAFe SSM or RTE credentials signal advanced practice.

Scrum master salaries in 2026: £40K–£65K UK; £60K–£90K for senior and RTE roles. US: $80K–$120K; SAFe RTE $100K–$145K.

ATS Keywords for a Scrum Master Resume

Scrum master ATS filtering uses certification names, Agile framework terms, and team metric vocabulary. "CSM", "SAFe", and "velocity" as explicit strings are the primary filters.

Essential ATS terms for a scrum master resume:

  • Title variants: Scrum Master, Senior Scrum Master, Agile Coach, Release Train Engineer, RTE, SAFe Scrum Master, Kanban Coach, Agile Delivery Lead
  • Certifications: CSM, Certified Scrum Master, PSM, PSM I, PSM II, PSM III, SAFe Agilist, SAFe SSM, SAFe RTE, AgilePM, ICAgile
  • Scrum events and artefacts: sprint planning, daily standup, retrospective, sprint review, backlog refinement, definition of done, definition of ready, sprint goal, burndown chart
  • Metrics: velocity, sprint predictability, cycle time, lead time, throughput, WIP, work in progress, burndown, burnup, cumulative flow diagram
  • Coaching: impediment removal, servant leadership, team coaching, Agile coaching, continuous improvement, team maturity, self-organisation
  • Scaling: SAFe, PI Planning, Agile Release Train, ART, LeSS, Nexus, Scrum of Scrums, programme increment
  • Tools: Jira, Azure DevOps, Confluence, Miro, MURAL, Linear, Trello, Monday.com
  • Long-tail phrases: scrum master resume examples, how to write a scrum master resume, agile coach cv, CSM resume, SAFe RTE resume, agile delivery lead resume

Placement: CSM or PSM (or SAFe credential) in the headline — this is the primary filter and the fastest credibility signal. Metrics vocabulary (velocity, cycle time, sprint predictability) in your Skills or throughout your experience bullets — they signal Agile maturity at a deeper level than ceremony facilitation language.

Scrum Master CV Structure and Bullets That Show Coaching Outcomes

Section order:

  1. Headline — "Scrum Master | CSM · PSM II · SAFe Agilist · Jira · Team Coaching · Agile Metrics"
  2. Certifications — CSM/PSM first, then SAFe, then any coaching credentials; near the top
  3. Skills — Agile Frameworks / Scaling / Metrics / Coaching / Tools
  4. Experience — 4–5 bullets per role; team outcome metrics, coaching interventions, impediment resolutions
  5. Education — degree; bottom

One to two pages. Every bullet should show what changed as a result of your coaching or facilitation — not what you did, but what the team did differently and what that produced.

Three elements make a scrum master bullet convincing: the team context (size, maturity, challenge), the coaching intervention (what specifically you identified and changed), and the measurable team outcome (velocity, predictability, cycle time, throughput). Three examples:

  • Coached a 9-person cross-functional scrum team from average sprint velocity of 28 to 54 story points over 6 months — diagnosed chronic scope creep and missing definition of ready as root causes through retrospective data analysis; implemented dual-track refinement process that reduced mid-sprint changes by 71%
  • Served as RTE for a SAFe programme across 4 teams and 38 people over 3 Agile Release Trains — facilitated quarterly PI Planning events, managed programme-level impediment register, and improved PI objective predictability from 61% to 84% across 3 consecutive programme increments
  • Reduced average cycle time for a platform engineering team from 14 days to 6 days by introducing WIP limits, implementing explicit queue stages on the Kanban board, and coaching on flow-based metrics; team throughput increased 40% over the following quarter without additional headcount

Scrum master interviews test coaching instinct through scenarios: "tell me about a time you identified a team dysfunction and how you addressed it" and "a team's velocity has been declining for 3 sprints — what do you do?" Your CV's outcome metrics set the depth of the coaching scenarios the interviewer designs for you.

Three Scrum Master CV Mistakes That Describe Facilitation Instead of Coaching

Listing ceremonies as achievements. "Facilitated sprint planning, daily standups, retrospectives, and sprint reviews" is not an achievement — it is the job description of every scrum master. These are the tools; what matters is what the tools produced. Did velocity improve? Did sprint predictability increase? Did the team become more self-organising? Did a specific recurring dysfunction get resolved? Answer those questions in your bullets, not the list of ceremonies you ran. The hiring manager already knows scrum masters run ceremonies; what they don't know — and can't assume — is whether your ceremonies produced anything.

No team outcome metrics anywhere in the CV. Scrum masters who don't track team metrics are operating without the primary diagnostic tool of the role. Velocity trends, sprint predictability (percentage of committed story points delivered), cycle time, and lead time are the data that tells you whether the team is improving or stagnating — and whether your coaching is working. A scrum master CV with none of these numbers anywhere looks like someone who facilitates rituals without knowing if they're helping. Pull the numbers from Jira, Azure DevOps, or your team dashboard before your next application. Even one metric per role — "improved sprint predictability from 65% to 88% over 4 months" — transforms a ceremonial CV into a coaching one.

Certification buried when it's the primary filter. CSM, PSM, and SAFe credentials are what the recruiter checks first for scrum master applications. They validate baseline knowledge in a way that a list of Agile terms cannot — anyone can write "Scrum, Kanban, SAFe" in a skills section without having been tested on any of it. A certified credential is a third-party verification of competence. Burying it in a "Certifications" section at the bottom of page two, or listing it without the full name (e.g., "Scrum Alliance certified" instead of "Certified Scrum Master, CSM"), loses the filter advantage you have earned. Put the full credential name in your headline.

If you are applying to scrum master or Agile coach roles and want your CV rebuilt around the specific CSM, SAFe, and Agile metrics requirements in a target job description, Resumegpt generates your scrum master CV from your work history in under 60 seconds — coaching outcomes surfaced, team metrics evidenced, ATS-optimised, and exported as a PDF ready to submit.