Scrum Master Resume Example (2026)
By FindAJobAI team Updated How we built this page
Scrum Master job ads often repeat the same checklist: run ceremonies, remove blockers, coach the team. What separates candidates is evidence that teams actually got better under them, faster delivery, fewer carried-over stories, happier retros. A Scrum Master resume should say which team, which metric moved, and by how much.
The example below is a Scrum Master with five years across two product teams at a logistics software company. Notice how each bullet names the team, the problem in the process and the measurable change, instead of listing ceremonies facilitated.
Scrum Master resume template
This example as a one-page template: one column, standard headings and plain text, the format applicant tracking systems read most reliably.
After you sign up, Create my CV builds your own resume in this same one-column layout, from your real experience.
Mid-level Scrum Master resume example
A complete one-page example for a fictional Scrum Master: every bullet pairs an action with what changed because of it.
Example resume · fictional person
Summary
Scrum Master with 5 years supporting software delivery teams at a logistics technology company, certified CSM and working across Jira and Confluence. Cut sprint carryover for a 9-person team from 35% to 12% and coached 2 teams through a transition to a healthier Definition of Done. Known for calm facilitation and turning retro themes into action that sticks.
Experience
Scrum Master, Haulwell Logistics Software
Denver, CO · Feb 2023 – Present
- Coach a 9-person cross-functional team shipping a dispatch platform, cutting sprint carryover from 35% to 12% over 6 months by tightening story refinement.
- Facilitated 48 sprint retros and turned the 3 most common themes, unclear acceptance criteria, into a Definition of Ready the team still uses.
- Tracked velocity and cycle time in Jira and flagged a recurring QA bottleneck, which led to adding a dedicated QA swimlane and cut average cycle time by 2 days.
- Ran dependency mapping across 3 teams ahead of a platform migration, surfacing 11 cross-team blockers before sprint planning instead of mid-sprint.
Scrum Master, Fieldline Software
Denver, CO · Aug 2020 – Jan 2023
- Served as Scrum Master for 2 teams totaling 14 engineers, running daily standups, sprint planning and reviews for both on a staggered schedule.
- Coached a team transitioning from ad hoc Kanban to Scrum, reaching a stable 2-week sprint cadence within 3 sprints.
- Built a Jira dashboard of sprint burndown and escaped-defect counts that product managers checked weekly, replacing a manual status email.
- Partnered with 2 product owners to improve backlog refinement, raising the share of stories estimated before sprint planning from 60% to 95%.
Skills
- Agile Delivery: Scrum, Kanban, sprint planning, backlog refinement, Definition of Done, release planning
- Tools: Jira, Confluence, Azure DevOps, Miro, Slack
- Metrics: Velocity, cycle time, sprint burndown, escaped defects
- Facilitation: Retrospectives, conflict resolution, stakeholder communication, cross-team dependency mapping
Certifications
- Certified ScrumMaster (CSM), Scrum Alliance, 2020
- PMI Agile Certified Practitioner (PMI-ACP), 2022
Education
- B.A. Business Administration, University of Colorado Denver, 2018
Fictional example by the FindAJobAI team: the person, employers and numbers are invented. Keep the structure; use your own work and numbers you can explain in an interview.
Entry-level Scrum Master resume example
A former QA coordinator moving into Scrum Mastery with one year of hands-on experience and a fresh CSM certification. The bullets lean on process changes she helped drive even before the title was official, and the summary is upfront about being early-career.
Entry-level example resume · fictional person
Summary
Associate Scrum Master with CSM certification and 1 year supporting an 8-person engineering team, transitioning from a QA coordinator role. Ran daily standups and sprint reviews, and helped the team move from inconsistent story sizing to a repeatable planning poker process. Comfortable in Jira and looking for a full-time Scrum Master role.
Experience
Associate Scrum Master, Brightlane Software
Raleigh, NC · Jun 2025 – Present
- Co-facilitate daily standups and sprint reviews for an 8-person team, stepping in as lead facilitator for 10 sprints while the senior Scrum Master was on leave.
- Introduced planning poker for story estimation, cutting the spread between the highest and lowest estimate on a story from 8 points to 3.
- Built a simple Jira filter board surfacing stories stuck in review for more than 2 days, which the team now checks each morning.
- Logged retro action items in a shared tracker and followed up weekly, raising the share of completed action items from about half to 9 in 10.
QA Coordinator, Brightlane Software
Raleigh, NC · Aug 2023 – May 2025
- Coordinated test cycles for a 6-person QA team across 2 sprints at a time, flagging scope changes to the product owner before sign-off.
- Noticed recurring late-sprint bug spikes and proposed moving QA involvement earlier in the sprint, a change the team adopted and credits with fewer last-day fire drills.
Skills
- Agile Delivery: Scrum, sprint planning, daily standups, backlog refinement, planning poker
- Tools: Jira, Confluence, Slack, Miro
- Foundations: QA-to-delivery handoff, basic velocity tracking, retro facilitation
Certifications
- Certified ScrumMaster (CSM), Scrum Alliance, 2025
Education
- B.S. Information Technology, North Carolina State University, 2023
Senior Scrum Master resume example
A senior Scrum Master and Agile coach ten years in, now running a Scrum of Scrums across multiple teams and mentoring junior Scrum Masters. The bullets move from running ceremonies to redesigning how the whole organization plans and releases.
Senior example resume · fictional person
Patricia Osei
Senior Scrum Master / Agile Coach
Minneapolis, MN · [email protected] · (612) 555-0176 · LinkedIn · Portfolio
Summary
Senior Scrum Master and Agile coach with 10 years supporting software delivery, the last 4 at a healthcare SaaS company. Leads a Scrum of Scrums for 40 engineers across 6 teams, mentors 3 junior Scrum Masters, and redesigned the quarterly release train, cutting planning time from 2 weeks to 3 days.
Experience
Senior Scrum Master, Meridian Health Software
Minneapolis, MN · May 2021 – Present
- Lead a Scrum of Scrums for 6 teams and 40 engineers, surfacing cross-team dependencies 2 sprints ahead instead of discovering them mid-release.
- Redesigned quarterly release-train planning, cutting prep time from 2 weeks to 3 days by moving dependency mapping into a shared async board.
- Mentor 3 junior Scrum Masters through monthly 1:1s and shadowed retros, 2 of whom have since taken on teams independently.
- Rolled out a standard set of delivery metrics (cycle time, carryover, escaped defects) across all 6 teams, replacing 6 inconsistent tracking spreadsheets.
Scrum Master, Ferncrest Digital
Minneapolis, MN · Jul 2017 – Apr 2021
- Supported 3 teams totaling 22 engineers through a transition from waterfall to Scrum, reaching a stable sprint cadence within 2 quarters.
- Facilitated a cross-team PI planning event for 3 teams twice a year, cutting mid-quarter re-planning incidents from 5 to 1 per quarter.
- Built the team's first Jira dashboard tying velocity to release dates, used by 2 product directors for roadmap commitments.
Scrum Master, Oakline Systems
Saint Paul, MN · Mar 2015 – Jun 2017
- Ran ceremonies for a 10-person team, improving sprint predictability from roughly 60% of commitments met to 85%.
- Introduced a Definition of Ready that cut mid-sprint scope clarification requests by half.
Skills
- Agile Leadership: Scrum of Scrums, PI planning, release trains, Agile coaching, metrics governance
- Tools: Jira, Confluence, Azure DevOps, Miro, LucidChart
- Mentoring: Coaching junior Scrum Masters, facilitation training, stakeholder alignment
Certifications
- Professional Scrum Master II (PSM II), Scrum.org, 2019
- SAFe Program Consultant (SPC), 2022
Education
- B.A. Communication, University of Minnesota, 2014
How to write a Scrum Master resume
Five steps, in the order a recruiter reads the page. The format around them stays plain for every job: one column, standard headings, newest role first.
Header: name, target title and links
Use the title “Scrum Master” even if your actual title was Agile Coach or Delivery Lead, and list your certification (CSM, PSM, PMI-ACP) right after your name or in the summary. Hiring managers scan for the certification first.
Summary: what you do and your best proof
State your years of experience, your certification, the kind of team or industry you support, and one metric you moved, carryover, velocity or cycle time. Skip lines like “passionate about Agile”; show it through the number instead.
Experience: newest first, a result in every bullet
Open each bullet with the team or process problem, then the change you made and the measured result: carryover dropped, estimation stabilized, blockers surfaced earlier. Listing ceremonies run says little; a metric that moved because of a specific change says a lot.
Skills: grouped, in the ad's words
Group into Agile practices (Scrum, Kanban, PI planning), tools (Jira, Azure DevOps, Confluence) and metrics you track. Name the specific metrics you report on, since many ads ask for familiarity with delivery metrics by name.
Education and certifications
List your degree with the year, and your Scrum certifications with the certifying body and year. Without Scrum Master experience, describe process improvements you drove in an adjacent role, like QA or project coordination, in your experience section.
Skills to put on a Scrum Master resume
Hard skills are the tools and methods of the job; soft skills are how you work with people. Each comes with one way to prove it, because a skill named only in a list counts for little. Add the ones you really have.
Hard skills
- Sprint planning
- Name the team size and a change you made to estimation or scoping, with the before-and-after outcome.
- Backlog refinement
- Give the share of stories that were estimate-ready before planning, before and after your involvement.
- Retrospectives
- Name a format you used and one working agreement or process change a retro produced.
- Jira / Azure DevOps
- Point to a dashboard or board you built and who checks it, not just that you administer the tool.
- Velocity tracking
- Give actual story-point numbers and what you changed to move them, not just that you tracked it.
- Cycle time / sprint carryover
- State the metric before and after a specific process fix, with a timeframe.
- Dependency mapping
- Name how many teams were involved and how many blockers you surfaced before they hit a sprint.
- Definition of Done / Ready
- Describe what was missing before and the rework or clarification requests it cut after you introduced it.
- Release/PI planning
- Give the number of teams involved and how planning time or re-planning incidents changed.
- Stakeholder communication
- Name who you report metrics to and how often, and one decision your reporting informed.
- Scrum of Scrums
- State how many teams and engineers you coordinate and one cross-team issue you caught early.
- Risk and blocker escalation
- Give an example blocker, how fast you escalated it, and the time or scope it saved.
Soft skills
- Facilitation
- Describe a tense meeting or disagreement you guided to a decision, naming the outcome.
- Conflict resolution
- Give a specific conflict between roles or teams you helped resolve and what changed after.
- Coaching
- Count the people or teams you coached and a measurable change in how they work.
- Servant leadership
- Point to a time you removed a blocker or took on grunt work so the team could keep moving.
- Adaptability
- Describe a process you changed mid-stream because it wasn't working, and what you replaced it with.
- Transparency
- Name a metric or status report you made visible to stakeholders that wasn't before.
- Active listening
- Give an example where a retro comment led directly to a process change you implemented.
Scrum Master resume bullet examples: weak vs strong
The same work, written two ways. The strong version names the tool, the scope and a result; the numbers are examples, yours must be real.
Weak: Facilitated Scrum ceremonies.
Strong: Facilitated daily standups, planning and retros for a 9-person team, cutting average standup length from 22 to 11 minutes by moving blockers to a parking-lot channel.
Names the ceremonies and a measured outcome from facilitation style.
Weak: Removed blockers for the team.
Strong: Unblocked a stalled API integration by escalating a cross-team dependency within a day instead of letting it sit 2 sprints, keeping the release on schedule.
Shows a specific blocker, the action taken and the time saved.
Weak: Improved team velocity.
Strong: Raised average velocity from 28 to 41 story points over 4 sprints by right-sizing stories during refinement, not by adding people.
Quantifies velocity change and names the real cause, not headcount.
Weak: Ran retrospectives.
Strong: Ran 20 retros using varied formats (Start-Stop-Continue, Sailboat) and turned the top recurring theme into a team working agreement that cut rework tickets by a third.
Shows retro variety and a concrete outcome from the themes raised.
Weak: Coached the team on Agile practices.
Strong: Coached a team new to Scrum from inconsistent story sizing to 90% of sprints closing within 10% of their committed points.
Turns a vague coaching claim into a measurable before-and-after.
Weak: Worked with product owners.
Strong: Partnered with the product owner to rewrite acceptance criteria templates, cutting stories reopened for clarification from 6 to 1 per sprint.
Shows collaboration with a specific process fix and its result.
15 more Scrum Master resume bullet examples
Grouped by area of the job, so you can find the ones closest to your work. Keep the shape (action, scope, result) and replace the invented numbers with your own.
Sprint health and metrics
- Cut sprint carryover for a 12-person team from 40% to 15% over 3 months by capping work-in-progress during planning.
- Raised the share of stories with clear acceptance criteria at sprint start from 55% to 95% using a Definition of Ready checklist.
- Tracked cycle time across 5 sprints and traced a 3-day average delay to code review queueing, leading to a rotating reviewer schedule.
- Stabilized velocity for a newly formed team from a 15-point swing between sprints to a 4-point swing within 2 quarters.
Facilitation and ceremonies
- Shortened daily standups from 25 to 12 minutes by moving detailed technical discussion to a separate sync, without losing visibility on blockers.
- Ran a Sailboat retro that surfaced a recurring deployment-day stress theme, leading to a shift from Friday to Tuesday releases.
- Facilitated sprint review demos for 6 stakeholders, restructuring the format so feedback is captured live instead of over email afterward.
- Introduced a parking-lot process for off-topic standup items, resolving 90% of them within the same day instead of letting them linger.
Cross-team and organizational work
- Coordinated a joint sprint boundary across 2 interdependent teams, cutting handoff delays on shared features from 4 days to 1.
- Built a dependency board reviewed in planning that surfaced 15 cross-team blockers a quarter before they reached mid-sprint.
- Ran a Scrum of Scrums for 4 teams, reducing duplicate work discovered mid-sprint from 3 instances to 0 over 2 quarters.
Coaching and process improvement
- Coached a team resistant to story pointing into consistent estimation, cutting sprint scope changes mid-sprint from 6 to 2 per sprint.
- Mentored 2 new Scrum Masters through shadowed ceremonies, both of whom took over teams independently within 6 months.
- Replaced a 10-page status report with a 1-page metrics dashboard, cutting stakeholder reporting time from 3 hours to 30 minutes a week.
- Introduced a team working agreement on code review turnaround and definition of done, cutting items reopened after review from 9 a sprint to 3.
Scrum Master resume summary examples
Two or three lines on what you do and your strongest proof. Start from the one closest to your level and use your own facts.
Scrum Master with CSM certification and 1 year supporting an 8-person engineering team as an associate Scrum Master and former QA coordinator. Ran daily standups and sprint reviews, and helped the team move from inconsistent estimation to a repeatable planning poker process.
Scrum Master with 5 years supporting software delivery teams, certified CSM and PMI-ACP. Cut sprint carryover for a 9-person team from 35% to 12% and coached 2 teams through healthier Definition of Done practices.
Senior Scrum Master and Agile coach with 10 years supporting delivery across 6 teams at a healthcare SaaS company. Leads a Scrum of Scrums for 40 engineers, mentors 3 junior Scrum Masters, and redesigned the release train that cut quarterly planning time from 2 weeks to 3 days.
Common Scrum Master resume mistakes
Each one is easy to make and quick to fix before you apply.
Listing ceremonies with no outcome
“Ran standups, sprint planning and retros” describes the job description, not your impact. Pair at least one ceremony with a metric or process change it produced.
No certification visible
CSM or PSM are often a screening filter. Put the certification in the summary or right under your name, not buried at the bottom of the resume.
Treating velocity as the only metric
Velocity alone can be gamed. Show carryover, cycle time or escaped defects alongside it to demonstrate a fuller picture of team health.
Sounding like a project manager
Budgets, Gantt charts and vendor management belong on a Project Manager resume. Keep a Scrum Master resume focused on team coaching, process health and ceremony facilitation.
No team size or scale
“Supported the engineering team” hides scope. State how many people and how many teams you supported, and whether you worked with one team or coordinated several.
ATS tips for a Scrum Master resume
Applicant tracking systems turn your file into text that recruiters search, mostly for the skills and titles in the ad. They rarely reject a resume on their own; one that parses badly or misses the ad's words just doesn't come up.
- Name your certifications (CSM, PSM, PMI-ACP) up top; many Scrum Master filters screen for them specifically.
- Show a sprint metric you moved, carryover, velocity or cycle time, with before-and-after numbers.
- Describe retros by the theme they surfaced and the change it led to, not by how many you ran.
- List the tools you ran ceremonies and dashboards in by name (Jira, Azure DevOps, Confluence), since ads usually ask for one.
- If you coach multiple teams or run a Scrum of Scrums, say how many teams and how many engineers.
For the format itself, run the free ATS resume checklist.
Everything for Scrum Masters
- Scrum Master cover letter examplesThree example letters and a short email version
- Scrum Master interview questions30 questions with sample answers
- Scrum Master job descriptionDuties, skills and requirements
- How to tailor your resume without lying
Other resume examples
Scrum Master resume FAQ
What certifications matter most for a Scrum Master resume?
CSM (Scrum Alliance) and PSM (Scrum.org) are the most recognized, with PMI-ACP useful if the company already runs other PMI processes. List the certifying body and year.
How do I show impact as a Scrum Master if I don't write code?
Track team-level metrics you influence: sprint carryover, cycle time, velocity stability and escaped defects. Pair each with the process change that moved it.
Should a Scrum Master resume include a Projects section?
It's optional. If you're new to the role, describing a specific team transition, like moving from Kanban to Scrum, in your experience section works better than a separate projects list.
Scrum Master vs Project Manager: how should the resume differ?
A Scrum Master resume emphasizes team coaching, ceremonies and process health; a Project Manager resume emphasizes scope, budget and cross-team timelines. Match your bullets to the title you're applying for.
How we built this page
The FindAJobAI team wrote the three example resumes, the bullets, the skills and the advice for Scrum Master roles. The people, employers and numbers in the examples are invented; the structure, the tools and the way each bullet is built are the parts to copy.
Once we track enough live Scrum Master job ads, this page also shows the skills they ask for most, counted the same way as our in-demand skills report.
Last reviewed on November 1, 2026.