Executive & Management · Senior (6+ yrs)

Certified Agile Scrum Master Resume

This sample shows how a Scrum Master can describe team facilitation, impediment removal, and delivery improvements across two product teams. A strong resume connects those practices to specific outcomes and makes relevant Scrum credentials and tools easy to find.

Resume check

What recruiters and tracking systems look for. A guide, not a prediction.

100 / 100Complete

100%
  • Contact20 / 20
  • Summary20 / 20
  • Experience30 / 30
  • Skills20 / 20
  • Education10 / 10

Contact details

Put these at the top; recruiters and tracking systems look for them first.

Optional. In the US, UK and Canada resumes usually have no photo.

40 words

One job per paragraph; start each achievement on a new line with “-”.

10 skills

Separate skills with commas, for example: Excel, SQL, project planning.

More sections

Projects, certifications, languages or anything else that supports your application.

Licenses & Certifications
Tools

Alex Morgan

Certified Agile Scrum Master

  • alex.morgan@example.com
  • +1 555 0100
  • Denver, CO

Summary

Certified ScrumMaster with 6 years of experience supporting software product teams in B2B SaaS. Facilitates Scrum events, coaches teams on backlog readiness, and tracks delivery trends to help teams improve predictability. Holds the Certified ScrumMaster (CSM) credential from Scrum Alliance.

Experience

Senior Scrum Master at Juniper Basin Software, Denver, CO (2022 – Present) - Facilitated sprint planning, reviews, and retrospectives for two product teams, helping reduce carryover work from 7 to 4 stories per sprint over six months. - Partnered with product owners to refine Jira backlogs and clarify acceptance criteria, cutting average story clarification time from 3 days to 2. - Removed cross-team dependencies with engineering leads and tracked sprint trends, reducing blocked work from 18% to 12% across four quarters. Scrum Master at Copperleaf Product Studio, Boulder, CO (2020 – 2022) - Guided one 8-person Scrum team through sprint events and backlog refinement, improving completion of planned work from 70% to 82% over three quarters. - Worked with product and engineering leads to surface release risks earlier, reducing late scope changes from 6 to 3 per release.

Education

B.S. in Information Systems — High Country Institute of Technology, Fort Collins, CO (2019)

Skills

  • Scrum facilitation
  • Sprint planning
  • Backlog refinement
  • Retrospectives
  • Sprint reviews
  • Jira
  • Scrum metrics
  • Impediment removal
  • Release coordination
  • Agile coaching

Licenses & Certifications

• Certified ScrumMaster (CSM), Scrum Alliance • Professional Scrum Master I (PSM I), Scrum.org

Tools

• Jira for sprint boards and backlog tracking • Confluence for team working agreements and decision notes

How to write a Certified Agile Scrum Master resume

Lead with team scope

Put your current Scrum Master title, product or delivery setting, and number of teams near the top of the experience section. Show whether you supported software, platform, or another product group so readers can place your work quickly. Avoid describing yourself as a project manager unless that was also your formal responsibility; Scrum Master work is centered on team effectiveness and Scrum practice.

Connect practices to outcomes

Use bullets that pair the action with a team or delivery measure: carryover work, blocked time, release changes, or completion of planned work. Explain the period and scope when you can, and keep the number modest and defensible. Avoid claiming that a Scrum event alone caused a business result; describe the collaboration or change that contributed to it.

List credentials precisely

Write Certified ScrumMaster (CSM) with Scrum Alliance as the issuer, or Professional Scrum Master I (PSM I) with Scrum.org. Include credentials you currently hold and check renewal status where the issuer requires it. Do not treat course attendance as certification, and avoid listing credential IDs or dates unless an employer requests them or they clarify current status.

Name your delivery tools

Include tools such as Jira or Confluence only when you used them, and say what you did with them: maintained a backlog, tracked sprint work, or recorded team decisions. If the job ad names another tool, use its wording when accurate. Leave out generic office software and long tool inventories that do not show how you supported a team.

Common keywords

Skills and tools often listed for this role. Use only the ones you have, in the job advert's wording. Click one to copy it.

Action verbs

FacilitatedCoachedRemovedImprovedIntroducedTrackedAligned

Questions about this role

How long should a Scrum Master resume be?

For a mid-career Scrum Master, one or two pages usually gives enough room to show team scope, delivery examples, and credentials. Keep recent roles detailed and shorten older or less relevant work. If you have supported several teams, choose examples that show different parts of the role, such as facilitation, coaching, and removing cross-team impediments.

Should I include my CSM or PSM certification?

Include Scrum credentials that you have earned and that are relevant to the posting. Use the full credential name and issuing organization, such as Certified ScrumMaster (CSM), Scrum Alliance, or Professional Scrum Master I (PSM I), Scrum.org. Check current status for credentials with renewal requirements; Scrum.org describes PSM I as lifetime certification, while credential rules can differ by issuer.

Can I move into a Scrum Master role from project management?

Yes, if your experience includes work relevant to the role, such as facilitating team planning, improving delivery practices, coaching teams, or helping resolve impediments. Use accurate examples from your current work and explain the team setting. Do not relabel project management duties as Scrum Master experience if you did not work with Scrum teams.

Do Scrum Masters need a technical degree?

There is no single degree requirement for Scrum Masters across US employers. Some postings prefer a bachelor's degree or experience in software delivery, while others focus on team facilitation and Scrum experience. List your actual education and relevant product or technical context, but do not imply that a degree or certification is universally required.