Scrum Master Resume Example (2026 Guide)
Scrum Master resume example
A complete sample in the Modern template FitMyRole exports. The person and employers are fictional; the structure, skills and bullet style are what to copy.
Nicole Jansen
[email protected] • (555) 014-3907 • Minneapolis, MN • linkedin.com/in/nicolejansen
Professional Summary
Senior Scrum Master with 11 years in software delivery, 8 of them coaching Scrum and Kanban teams in health insurance and banking. Supports 3 cross-functional teams of 24 engineers, testers and designers building the member portal and claims apps for a health plan with 900,000 members, and facilitates quarterly PI planning for a 7-team release train. Cut average cycle time from 9 days to 4 and raised sprint goal completion from 55% to 88% by making work visible, limiting work in progress and fixing backlog refinement. Coaches through questions rather than mandates, protects team focus and gives leaders delivery forecasts based on throughput data.
Core Skills
- Agile Frameworks: Scrum, Kanban, SAFe, Scrumban, Lean, Extreme Programming practices
- Facilitation & Ceremonies: Sprint planning, daily scrum, sprint review, retrospectives, PI planning, workshop design, conflict resolution
- Agile Metrics: Velocity, cycle time, throughput, burndown and burnup charts, cumulative flow diagrams, Monte Carlo forecasting, sprint goal completion
- Coaching: Team coaching, product owner coaching, backlog refinement, user stories and acceptance criteria, definition of ready and done
- Tools: Jira, Confluence, Miro, Azure DevOps, Jira Align, Microsoft Teams
- Delivery & Stakeholders: Impediment removal, dependency management, release planning, risk management, stakeholder reporting
Education & Certification
- Coursework focus: Systems Analysis and Design, Project Management, Database Management and Organizational Behavior.
Work Experience
Senior Scrum MasterAugust 2021 – PresentMill City Health Plans, Minneapolis, MN
- Raised sprint goal completion from 55% to 88% across 3 Scrum teams in a year by reshaping backlog refinement around a definition of ready and setting one clear sprint goal with each product owner.
- Cut average cycle time from 9 days to 4 by introducing WIP limits on the Jira boards, splitting stories to under 3 days of work and calling out blocked items at every daily scrum.
- Run all Scrum ceremonies for 24 team members, from sprint planning to reviews and retrospectives, varying retro formats in Miro so each one ends with 1 or 2 owned actions.
- Facilitate quarterly PI planning for a 7-team release train of 70 people with the release train engineer, building the program board and dependency map that halved late cross-team blockers.
- Replaced story-point velocity promises with Monte Carlo forecasts from Jira throughput data, giving leadership release dates that landed within one sprint on 5 of the last 6 releases.
- Coached 4 product owners on writing user stories with acceptance criteria and ordering the backlog by value, reducing mid-sprint scope changes from 6 per sprint to 1.
- Removed a recurring 2-week wait for test environments by bringing the infrastructure and QA leads into a joint impediment review, which led to on-demand environments in Azure.
- Mentor 2 newer Scrum Masters through shadowing, and host a monthly community of practice for 12 agile practitioners across the IT organization.
Scrum MasterMarch 2018 – July 2021Stone Arch Financial, Minneapolis, MN
- Led 2 teams through the bank’s move from waterfall to Scrum for the online and mobile banking apps, running the first sprints and teaching the framework to 16 team members.
- Increased deployment frequency from quarterly to every two weeks by working with release management to split releases into smaller increments under a shared definition of done.
- Stabilized team velocity to within 10% sprint over sprint by tracking carryover in Jira, running capacity planning before each sprint and routing unplanned requests through the product owner.
- Built Jira dashboards and Confluence sprint reports on burndown, carryover and escaped defects that replaced a weekly status meeting for 2 directors.
- Moved production support onto a separate Kanban board with service level expectations, cutting interruptions to sprint work by about 40%.
Business AnalystJune 2015 – February 2018Lakes Region Software, Saint Paul, MN
- Wrote requirements as user stories for a policy administration system used by 12 insurance carrier clients, working with 2 development teams.
- Served as backup Scrum Master for a 7-person team for a year, running daily scrums and retrospectives, which prepared the move into a dedicated Scrum Master role.
- Ran user acceptance testing with client users for 6 releases, writing test scenarios and triaging 150 defects in Jira with the QA lead.
- Mapped current and future workflows in Visio for the claims module, clarifying 40 business rules before development and cutting rework on that release.
Want yours to read like this? Upload your resume and a job posting, and FitMyRole rewrites it for that job in this template.
Tailor my resumeWhy This Resume Works
- The results are agile delivery metrics, not meeting counts: sprint goal completion from 55% to 88%, cycle time from 9 days to 4, and forecasts that landed within one sprint on 5 of 6 releases.
- Facilitation is specific ("Run all Scrum ceremonies for 24 team members", PI planning for a 7-team release train of 70 people), which fixes the vague "facilitated meetings" line most Scrum Master resumes use.
- Each improvement says how it was done (WIP limits, a definition of ready, Monte Carlo forecasting), showing coaching skill instead of just process ownership.
- Certifications that Scrum Master postings filter on (CSM, A-CSM, SAFe Scrum Master) are dated in their own section, and Jira, Velocity and ceremonies appear in both Skills and bullets.
- The path from business analyst and backup Scrum Master to Scrum Master to senior role shows where the product and requirements depth in the coaching bullets comes from.
Common Resume Mistakes
- Vague "facilitated meetings" without team or outcome.
- No velocity, cycle time, or improvement metrics.
- Missing certification or tool keywords.
Keywords Recruiters Look For
- Scrum
- Agile
- Scrum Master
- Jira
- Velocity
- Facilitation
- CSM
- Ceremonies
Get more interviews. Tailor your resume automatically
Want to tailor your resume to the job you want? Use FitMyRole to analyze your resume and rewrite it for the role. Before sending your next application, run your resume through FitMyRole to tailor it to the job description.
Try FitMyRole free