Scrum master resume example

What recruiters look for

• Team outcomes you influenced: sprint goal completion, cycle time, throughput, escaped defects, release frequency.
• How many teams and what kind: one co-located team is different from three teams inside a scaled framework.
• Coaching, not secretarial work: product owners you coached, teams that learned to run their own events.
• Removing impediments that matter: dependencies, environments, approvals. Name one you fixed for good.
• Recognized certifications: PSM, CSM or SAFe. Many job ads filter on one of them.

Writing the summary

Say how many teams you serve, in what organization, and whether you work in plain Scrum, Kanban or a scaled framework. Then one line on what you are good at (flow, coaching product owners, scaling) and your certifications.

Bullet points that work

Strong lines for this role, beyond the ones in the example. Borrow the shape and put in your own numbers.

• Helped a team go from releasing quarterly to every two weeks in 5 months by splitting stories and automating the regression suite with QA.
• Mapped dependencies across 6 teams on a shared board, cutting blocked work items by 45% in one program increment.
• Reduced escaped defects by 30% by bringing testers into refinement and adding a definition of done the team wrote itself.
• Coached a product owner whose sprint reviews grew from 4 stakeholders to 25, with feedback captured in the backlog.
• Replaced a 90-minute daily status meeting with a 15-minute Daily Scrum and a written async update.
• Started a scrum master community of practice that grew to 22 members and runs monthly sessions.
• Got test environments provisioned on demand with the platform team, removing a 3-day wait that blocked every sprint.
• Trained 60 managers and stakeholders on Scrum roles in four half-day workshops.
• Moved a support team to Kanban with WIP limits, cutting average ticket age from 9 days to 4.

Skills to list

Certifications and licenses worth listing

• Professional Scrum Master I and II (PSM I, PSM II), Scrum.org: exam-based and well regarded; PSM II shows depth.
• Certified ScrumMaster (CSM) and Advanced CSM, Scrum Alliance: course-based and widely requested in job ads.
• SAFe Scrum Master (SSM), Scaled Agile: expected in companies running SAFe; the SAFe Release Train Engineer certification is the next step.
• ICAgile ICP-ACC: a good signal if you are heading toward agile coaching.
• Kanban Management Professional (KMP), Kanban University: useful for Kanban-heavy teams.

Length and format

One page is enough for most scrum masters with under eight years; two if you have served many teams across several companies. Put certifications near the top or in the sidebar of a two-column layout, because recruiters check them first.

Common mistakes

• Describing Scrum events (“facilitated daily stand-ups, sprint planning and retrospectives”) as if they were achievements. Every scrum master does that; say what improved.
• Taking credit for the team’s velocity. Velocity is the team’s planning tool, not your result; flow and predictability are safer measures.
• No numbers at all, as if coaching could not be measured. Cycle time, goal completion and defects all can.
• Listing every agile buzzword (“servant leader”, “agile mindset”, “continuous improvement”) without an example behind one.
• Hiding the business context. Insurance, healthcare and banking teams have constraints that make your results more impressive.