Scrum Master Resume: Examples (2026)

Scrum master resume example with summary and bullet examples, agile skills, PSM, CSM and PMI-ACP certifications, official pay data and a free template.

Template:

Fictional example: a scrum master with four years of experience, previously a software tester, applying for a senior scrum master role at a larger software company. Names and career details in the samples are invented for illustration.

Why this resume works

  • The fictional sample gives three teams and twenty-two people in total, without implying twenty-two per team.
  • Coaching, backlog support and a Definition of Done describe contributions alongside team results.
  • The earlier testing role and earned credentials remain distinct from current Scrum accountabilities and broad organizational authority.
Edit & download this resume

Create a free account to edit this example and download a PDF with no watermark. Classic is free; Compact, Creative, and Bold require a Job Search Pass.

A Scrum Master resume should explain how you helped a team use Scrum, address impediments and improve its practices. Describe the product, team and contribution before claiming a delivery improvement. The Scrum Guide defines self-managing teams and distinct accountabilities; the Daily Scrum belongs to the Developers. This guide includes a fictional software example, its full text version and choices for career-change, team and senior applications.

Scrum master resume example: text version

This is the fictional example shown above in selectable text. Use its structure, then replace every sample detail with your own. The image and editable example use the same resume data.

Rachel Ingram

Scrum Master, Agile Coaching and Team Delivery

rachel.ingram@example.com

(303) 555-0174

Denver, CO, US

Summary

Scrum master with four years supporting software teams that build scheduling tools for clinics, currently serving 3 teams of 22 people in total. Helps teams ship smaller changes more often, makes problems visible early and coaches product owners on backlog planning. Former software tester. Professional Scrum Master I and PMI-ACP certified. Seeking a senior scrum master role.

Experience

Scrum Master

Front Range Health Software

From: Aug 2022

To: Present

  • Serve as scrum master for 3 teams of 22 people in total, running planning, daily scrums, reviews and retrospectives for each.
  • Helped the patient booking team move from releases every 10 weeks to every 2 by splitting work into smaller pieces and automating a release checklist.
  • Raised the share of sprints that met their goal from 50 to 85 percent over 4 quarters by coaching the team on realistic planning.
  • Coached 2 new product owners on writing and ordering the backlog; both teams now have 2 sprints of work ready at all times.
  • Introduced a shared definition of done with the testers, cutting bugs found after release by 45 percent.

Software Quality Assurance Analyst

Front Range Health Software

From: Jun 2019

To: Jul 2022

  • Tested 4 product releases a year and organized the team's first retrospectives, which led to a new scrum master role being created.

Training and certificates

PMI Agile Certified Practitioner (PMI-ACP)

Project Management Institute

2025

Professional Scrum Master I (PSM I)

Scrum.org

2022

Skills

Scrum and Kanban

Facilitating retrospectives and planning

Coaching product owners

Removing blockers

Jira and Confluence

Miro for remote workshops

Flow metrics (cycle time, throughput)

Conflict resolution

Education

Bachelor of Arts

Psychology

Mesa Ridge University

To: 2019

Choose Scrum Master evidence for your experience

Rachel's fictional example covers software-team support. Explain your actual coaching and facilitation contribution without borrowing the team's whole delivery result.

Moving from testing, development or coordination

Keep the original title. Describe a retrospective, dependency discussion or temporary coverage you actually handled, with what the team agreed and reviewed next. A credential or personal project does not become professional Scrum Master employment.

Dedicated team responsibility

Explain the product, team and impediment. Show how you helped the team inspect and adapt its work. Distinguish ensuring productive events from directing the Developers' Daily Scrum or assigning their tasks.

Multiple teams or organizational coaching

State the actual people and teams supported and the coordination involved. Three teams do not automatically establish a Release Train Engineer role, a particular scaling framework or direct management authority.

Senior applications

Describe a difficult dependency, coaching intervention or experiment and how its effect was reviewed. Explain limits and unintended results when relevant. Do not use story points as individual productivity or compare teams with incompatible estimates.

Worked revision from the fictional sample

Ambiguous: Improved sprint performance by 35 percent.

Defined: Coached planning while the share of sprints meeting their goal rose from 50 to 85 percent over four quarters.

The difference is thirty-five percentage points. Rachel's measure concerns Sprint Goals, not the fraction of story points completed. Her release cadence and reported post-release bug change are separate measures and do not establish sole causation or a normalized defect rate.

Prepare your application

Create a free account, edit Classic and save with Update. Inspect the PDF and copied text. Use permitted process examples without private team feedback or restricted delivery reports.

Scrum master pay and job outlook

Official figures for Information Technology Project Managers.

Median pay (2025)
$116,580 per year ($56.05 per hour)
Projected growth, 2025 to 2035
Faster than average (5% to 6%)
Projected annual openings, 2025 to 2035
27,000

Scrum master is not tracked as its own occupation here. O*NET lists the title under Information Technology Project Managers, while these wage and projection figures refer to the parent occupation Computer Occupations, All Other. They are not Scrum Master-specific pay or forecasts.

Source: O*NET OnLine: Information Technology Project Managers, checked October 2026.

How to write a scrum master resume

1

Describe the product and team

Give the setting and actual scope, distinguishing people per team from total people supported.

2

Explain a contribution

Use an impediment, coaching discussion or improvement experiment you actually handled.

3

Define results

State the measure and period. Distinguish goal achievement, release frequency, cycle time and defect counts.

4

Respect accountabilities

Describe coaching and productive events while retaining Product Owner and Developer responsibilities. Do not invent assignment authority.

5

List actual qualifications and tools

Separate earned credentials, study and practical framework experience. Explain tasks in systems you used.

6

Review the file

Save the edited example, inspect the PDF and copied text and follow format and length instructions.

Skills and keywords for a scrum master resume

Select relevant skills and systems supported by your own work. Explain the contribution rather than copying every framework or tool.

Hard skills

  • Scrum events: sprint planning, daily scrum, sprint review and retrospective
  • Backlog support: helping the product owner keep work clear and ordered
  • Kanban: managing work as a flow with limits on work in progress
  • Flow metrics such as cycle time and throughput
  • Facilitating workshops and remote meetings
  • Removing blockers and managing dependencies between teams
  • Scaled frameworks such as SAFe for multi-team programs
  • Release planning and forecasting
  • Coaching teams and managers on agile practices
  • Tracking risks and making them visible

Soft skills

  • Listening and asking good questions
  • Handling conflict calmly
  • Leading without authority
  • Coaching instead of directing
  • Honest, clear communication with leaders
  • Patience with change

Tools and software

  • Jira and Confluence
  • Azure DevOps Boards
  • Miro or Mural whiteboards
  • Rally or Jira Align for scaled programs
  • Microsoft Teams or Slack
  • Retrospective tools such as EasyRetro or Parabol

Scrum master resume summary examples

These separate fictional summaries illustrate different applications. Replace the team, scope, qualifications and results with your own experience.

New scrum master

Project coordinator with three years on software projects, including a year acting as scrum master for one team of 7 while the role was vacant. Ran all Scrum events, kept the board current in Jira and cut the team's open blockers from about 12 to 3 a sprint. Certified ScrumMaster (CSM); seeking a first full-time scrum master role.

Experienced scrum master

Scrum master with five years supporting web and mobile teams at a bank, currently 2 teams of 16 people. Helped both teams move to releasing every sprint and introduced flow metrics that cut average cycle time from 9 days to 4. PSM I and SAFe Scrum Master certified; seeking a scrum master role in financial technology.

Senior scrum master or agile coach

Agile coach and former scrum master with ten years, now supporting 8 teams and their managers in a 120-person software department. Led the move from yearly releases to monthly, trained 40 people in Scrum and Kanban, and built the department's community of practice for scrum masters. PMI-ACP; seeking an enterprise agile coach role.

Scrum master resume bullet examples

These fictional illustrations show different team contributions. Define your actual measure and review period, keeping your action distinct from a demonstrated cause.

  • Supported 2 teams through a move from yearly to monthly releases over 3 quarters.
  • Cut average cycle time from 11 days to 5 by limiting work in progress and splitting large tasks.
  • Ran 60 retrospectives in 2 years; the team tracked and finished 85 percent of the actions agreed.
  • Resolved a long-running dependency with the data team by setting up a shared weekly planning slot, ending 3 sprints of delays.
  • Trained 35 new team members and managers in Scrum basics with a half-day workshop.
  • Raised team satisfaction in quarterly surveys from 3.1 to 4.2 out of 5 after changes agreed in retrospectives.
  • Facilitated planning for a SAFe program of 6 teams and 55 people each quarter.
  • Introduced a visible blocker board that cut the average time to clear a blocker from 4 days to 1.
  • Coached a product owner new to the role, bringing the backlog from 1 to 3 sprints of ready work.
  • Moved 4 teams from spreadsheets to Jira boards with shared reports for leadership.
  • Helped a team cut bugs found after release by 30 percent by adding testing to its definition of done.

Certifications for scrum masters

Check the vacancy and list the exact earned credential, issuer and status. Training and certification have different requirements, and neither guarantees employment or a delivery outcome.

  • PSM I: Scrum.org requires its assessment; course attendance is not a prerequisite. The certification is lifetime with no annual renewal fee.
  • CSM: Scrum Alliance requires approved training followed by its test. Renewal includes continuing education on a two-year cycle. Do not present course enrollment as an earned award.
  • SAFe Scrum Master: Scaled Agile's current certification page describes an examination route. Identify the actual award and framework experience separately rather than claiming enterprise-scale practice from the badge alone.
  • PMI-ACP: PMI's credential covers agile approaches beyond Scrum, with eligibility pathways, formal training and continuing certification requirements. Check the current pathway before applying.

The example, line by line

Rachel Ingram is fictional. Testing employment starts in June 2019, and the Scrum Master role begins in August 2022.

Scope: three teams contain twenty-two people in total. Her event support should be understood alongside self-management: the Developers own the Daily Scrum, while the Scrum Master ensures events happen productively. It is not authority to assign their work.

Delivery: the booking team moves from releases every ten weeks to every two. This is release frequency, not a fivefold productivity or revenue increase. The Sprint Goal measure rises from 50 to 85 percent over four quarters, separate from story completion.

Backlog and quality: coaching two Product Owners and having two sprints of prepared work describe this organization's practice, not a Scrum requirement. The reported 45 percent reduction in bugs found after release has no supplied denominator or comparison period, so it is not a normalized rate or proof of one cause.

Earlier background: testing four product releases yearly is earlier work, not the current release cadence for every team. The psychology degree is her educational background, not a required Scrum qualification.

Credentials and tools: PSM I and PMI-ACP are different awards. Jira, Confluence and Miro are listed without implying every scaling framework or a Release Train Engineer designation.

Mistakes that cost scrum masters interviews

  • Taking the team's whole result: describe the contribution and review period rather than claiming one intervention caused every change.
  • Confusing measures: Sprint Goal achievement, story completion, release frequency and defect counts are different.
  • Directing self-managed work: distinguish coaching and event support from assigning Developers' tasks.
  • Using credentials as work history: label training, earned awards and practical experience separately.
  • Borrowing scale: multiple teams do not automatically mean a particular framework or organizational title.
  • Comparing incompatible points: explain team context instead of ranking people or teams by story estimates.

Other resume examples close to this one:

Every example is in the resume examples hub, grouped by job and situation.

Build it free, no watermark

Create a free CVPoet account before editing. Start from this example in the free Classic template or start a blank page, and download a PDF with no watermark. Compact, Creative, and Bold are available with a Job Search Pass.

Frequently asked questions

What belongs on a Scrum Master resume?

The product and team context, coaching or facilitation contribution, relevant results and actual qualifications. Define the measure and explain your part in the team's work.

How do I apply without a dedicated Scrum Master role?

Keep your original title and describe real temporary coverage, retrospectives or dependency work. Label projects and training accurately rather than inventing professional employment.

Does the Scrum Master run the Daily Scrum?

The Scrum Guide defines it as an event for the Developers. The Scrum Master helps ensure productive Scrum events and supports self-management, rather than assigning tasks or using the event as a manager's status meeting.

Which metrics help?

Use supported measures relevant to the problem, such as goal achievement, cycle time or release frequency. Define the period and limits. Story points are not a universal productivity scale.

How do I report a goal-achievement change?

Give the share of sprints and the review window. A rise from 50 to 85 percent is thirty-five percentage points. It does not establish the fraction of planned stories completed.

How do I show multiple-team experience?

State the actual teams, total people and coordination work. Do not infer direct management, a scaling framework or an RTE title merely from team count.

Which certification should I list?

List the one you actually earned and check the vacancy. PSM, CSM, SAFe and PMI-ACP have different assessment, eligibility and renewal requirements. No badge guarantees employment.

Must the backlog have two sprints ready?

That can be a local practice, but it is not a universal requirement in the Scrum Guide. Explain the problem and the approach your team used without presenting every tactic as a rule.

Does earlier testing or development belong?

Keep relevant background with accurate titles and concise evidence. Explain how it helps collaboration without claiming that the background alone caused a later team outcome.

How do I edit Rachel's example?

Create a free account, replace the fictional details in Classic and select Update. Check the full PDF and copied text and follow the application's format and length instructions.

Build your scrum master resume now

Start from Rachel's example or a blank page. Free, a free account is required to edit, and the PDF has no watermark.

Build your resume, free
Scrum master resume example
Scrum master resume example The example above as an image, to save or share. To change it, use Edit & download this resume at the top of the page. Open the full-size image
Premium

More ways to make your CV yours

Unlock all three premium designs with a Job Search Pass. Your written content stays exactly as it is. Classic is always free.

Included with your pass

$12 once for 30 days

No subscription. Nothing renews. A 90-day pass is also available.

See Job Search Passes

Pass options open in a new tab. Your draft stays here.