Was this sample helpful? Rate it!
Average: 4.5 (38 votes)
Contents
What Matters Most
Why This Scrum Master Resume Works
How to Write a Scrum Master Resume That Gets Interviews
What to Include in a Scrum Master Resume
Scrum Master Resume Summary Examples
Scrum Master Work Experience Examples
Top Scrum Master Skills
Scrum Master Certifications
Common Scrum Master Resume Mistakes
Scrum Master Resume FAQs
Summary
Scrum master with seven years helping software teams deliver well at companies in São Paulo. Serves the team, not the other way round — facilitating the scrum events, clearing the blockers that slow delivery, shielding the team from churn, and coaching everyone toward genuinely agile ways of working rather than just the ceremonies. Helped teams lift their delivery and predictability and coached a struggling team back to health. Facilitates scrum events, removes impediments, coaches the team and product owner, tracks delivery metrics, and drives continuous improvement. Servant-leading, perceptive and steady. Looking for a scrum-master role with an organisation that wants agile done genuinely, not just performed.
Professional Experience
Scrum Master
São Paulo Software Company, São Paulo, Brazil
Jan 2019 – Present
- Serve the team, not the other way round, clearing blockers and shielding them so they can deliver well.
- Helped teams lift their delivery and predictability and coached a struggling team back to health.
- Facilitate the scrum events so they are useful, not ritual, keeping planning, standups and reviews focused.
- Remove impediments fast, chasing down the blockers and dependencies that quietly slow the team down.
- Coach the team and product owner toward genuinely agile working, not just going through the ceremonies.
- Track delivery metrics and drive improvement, helping the team get a little better every sprint over time.
Developer / Agile Team Member
Brazil Technology Group, São Paulo, Brazil
Jul 2015 – Dec 2018
- Worked as a developer in agile teams and gradually took on facilitation, learning scrum from the inside out.
- Supported sprints and helped the team improve, steadily building the facilitation skills the role demands.
- Learned agile delivery, facilitation and team dynamics on the job across more than three years.
- Gained the certification and experience that led into a full scrum-master role of my own.
Education
BSc in Computer Science, Computer Science
University of São Paulo
Feb 2011 – Dec 2015
- Degree in computer science covering software engineering, teams and process, with projects. The programme built the technical grounding to credibly serve software teams. It led from development into agile facilitation and coaching.
Certified Scrum Master (CSM), Agile
Scrum Alliance
Jan 2016 – Jun 2016
- Certified Scrum Master credential covering scrum, facilitation and agile practice to a recognised standard. It validated agile competence. It supported facilitating teams and coaching genuinely agile ways of working.
Certifications
Certified Scrum Master (CSM)
Scrum Alliance
Jun 2016 – Present
- Certified Scrum Master credential covering scrum, facilitation and agile practice to a recognised standard, which validated agile competence and supports facilitating teams and coaching genuinely agile ways of working.
Highlights
Lifted delivery and predictability
- Helped teams improve both their delivery and their predictability. A team that ships steadily and hits its forecasts is far more valuable to the business, so improving both is exactly what a scrum master is there to enable.
Healed a struggling team
- Coached a struggling, demoralised team back to health and delivery. Turning a team around takes patience, trust and skilled facilitation, and is among the most valuable things a scrum master can do.
Recognition
A scrum master teams want
- Valued by teams as a servant-leader who genuinely clears their path and helps them improve, and by leadership for lifting delivery and turning a struggling team around through real agile coaching.
Languages
- Portuguese — Native or Bilingual Proficiency
- English (US) — Full Professional Proficiency
Technical Skills
- Scrum Facilitation
- Impediment Removal
- Agile Coaching
- Team Health
- Delivery Metrics
- Continuous Improvement
- Stakeholder Management
- Conflict Resolution
- Backlog & Flow
- Servant Leadership
Personal Skills
- Servant Leadership
- Perceptiveness
- Steadiness
- Facilitation
- Communication
Activities & Interests
- Feed Baby
- News paper
- Cleaning
- Cinema
- Kite Flying
What Matters Most
Before the detail, here is what actually decides whether a scrum master resume gets a screening call:
- Show facilitation of the actual scrum events by name, not a vague claim of running agile: planning, daily scrum, review, retrospective and refinement each have their own failure modes.
- Impediment removal is the clearest evidence of value, so name the blockers you cleared and how long the team was blocked before and after.
- Quote flow metrics you influenced (cycle time, throughput, work in progress, sprint goal achievement) rather than velocity alone, which hiring managers read as a vanity number.
- Say explicitly what you did not own. A scrum master who claims budget authority, a Gantt chart and line management reads as a project manager wearing a scrum label.
- Coaching counts twice: coaching the developers and coaching the product owner. Most candidates mention only the first and lose half the role.
- One certification (PSM or CSM) opens the ATS gate; what you actually changed on a team is what carries the interview.
Why This Scrum Master Resume Works
The sample above belongs to a seven-year scrum master in Sao Paulo who moved into the role from development. Here is what a hiring manager notices in the first pass:
- The summary opens on service to the team rather than on tools or frameworks, which sets the servant-leadership frame before any bullet is read.
- The experience section separates facilitation, impediment removal, coaching and metrics into distinct lines, so a reader can see all four pillars of the role instead of one blurred paragraph.
- Coaching is explicitly split between the team and the product owner, which signals the candidate understands the role serves both.
- The developer years at the earlier employer are framed as the route into facilitation rather than hidden, which answers the obvious question about how the candidate learned scrum.
- The scrum master certification sits in both education and certifications, so the credential is visible whichever section a recruiter scans first.
- Nothing in the resume claims schedule ownership, resourcing or headcount, so the profile never blurs into project or line management.
How to Write a Scrum Master Resume That Gets Interviews
Agile hiring managers screen for evidence that you changed how a team works, not that you attended its meetings. Five moves do most of the work:
Open the summary with who you serve and at what scale
Name the team size, the product domain and the number of teams in the first line. "Scrum master serving two eight-person platform teams in regulated fintech" tells a hiring manager more than five sentences about agile values. Add your strongest certification in the same line so the ATS finds it early.
Write each scrum event as a problem you fixed, not an item you attended
Anyone can say they ran retrospectives. Say what the retrospective format was, why you changed it, and what happened: "replaced a round-robin retro with a timeline format after three sprints of silence, and action-item completion moved from one in five to three in four." Same for planning, refinement and review.
Quantify impediment removal with time, not count alone
The number that lands is blocked time. "Cleared 43 logged impediments" is fine; "cut average blocked days per sprint from seven to under two by escalating cross-team dependencies within 24 hours" is what gets you asked about in the interview. Track this in your own notes now if you are not already.
Report flow metrics, and show you know what velocity is for
Put cycle time, throughput, work in progress and sprint goal achievement on the page. If you quote velocity, frame it as a forecasting input for the team rather than a productivity score for management. A line like "replaced a velocity league table across four teams with a cycle time and WIP-age dashboard" reads as genuine agile maturity.
Name the coaching you did on the product owner side
Story slicing, backlog ordering, outcome-framed acceptance criteria, saying no to mid-sprint additions. "Coached the product owner on vertical slicing, shrinking the average story from thirteen points to three" shows you serve the whole scrum team. Most candidates skip this entirely, so it is cheap differentiation.
State the boundary of the role in plain words
One clause is enough: "no budget or line-management responsibility; accountable for team effectiveness and flow." It sounds like a limitation and reads as confidence. Hiring managers who have been burned by project managers rebadged as scrum masters will notice it immediately.
What to Include in a Scrum Master Resume
Beyond the standard blocks, a few things carry unusual weight on this particular resume:
If you would rather build the layout than fight with it, our free tool keeps the scrum sections in a clean single-column order that applicant tracking systems parse cleanly. Start with a scrum master resume template and fill in your own metrics.
Team topology: how many teams, how big, co-located or distributed, and across how many time zones. Facilitating a standup across an eight-hour gap is a different job.
The framework flavour in use: pure Scrum, Scrum with Kanban practices, SAFe, LeSS or Nexus. Say which one, because scaled-agile roles screen for it directly.
Tooling with the depth implied: Jira with custom workflows and board configuration, Azure DevOps, Miro or Mural for remote facilitation, and whichever flow-metrics plugin you used.
A metrics line that names the baseline and the after figure, because a scrum master with no before-and-after numbers looks like a meeting host.
The engineering context you can hold a conversation in, especially if you came from development. It buys credibility with the team you would serve.
Certification with the awarding body and year, since PSM and CSM are not interchangeable and interviewers will ask which one.
Scrum Master Resume Summary Examples
Three summaries at different points in a scrum master career, each pronoun-free and written the way a strong candidate would actually open the page:
Entry-level resume summary example
Certified scrum master (PSM I) stepping into full-time facilitation after four years as a developer inside scrum teams, with hands-on experience running refinement and retrospectives for a nine-person squad. Facilitates the full event cycle, keeps the sprint backlog visible on a physical and digital board, and chases cross-team dependencies before they harden into blocked work. Cut sprint planning from three hours to ninety minutes by moving refinement to a weekly slot, and lifted retrospective action completion from one in five to three in four. Reads cycle time and work in progress alongside velocity, and coaches product owners on slicing stories vertically. Seeking a scrum master role on a product team that wants agile practised rather than performed.
Mid-level resume summary example
Scrum master with six years serving product and platform teams in regulated fintech, holding PSM II and A-CSM. Facilitates planning, daily scrum, review and retrospective for two teams of eight, and runs the refinement cadence that keeps the top of the backlog ready two sprints ahead. Raised sprint goal achievement from four sprints in twelve to eleven in twelve by coaching forecasting against measured throughput instead of optimistic capacity. Halved cycle time from eighteen days to nine by capping work in progress at five items. Coaches product owners on outcome-framed backlog items and absorbs mid-sprint scope churn so the team keeps its sprint goal. Looking for a scrum master role in an organisation willing to change its own process, not only the team's.
Senior-level resume summary example
Senior scrum master with eleven years across single-team and scaled delivery, currently supporting six teams building one payments platform under SAFe. Runs quarterly planning for sixty-plus people, owns the dependency board, and facilitates scrum of scrums that surface cross-team blockers eight to ten days earlier than the previous escalation path. Replaced a velocity league table with a flow dashboard covering cycle time, throughput and work-in-progress age, which changed how leadership reads delivery risk. Mentored five scrum masters through their first year and runs a fortnightly community of practice. Holds no budget or line-management authority by design; the value sits in coaching, facilitation and clearing impediments. Seeking a scaled scrum master or agile coaching role in a product organisation.
Scrum Master Work Experience Examples
Three contexts a scrum master resume is usually written from. Borrow the shape, then swap in your own baselines and after-figures:
First scrum master role, single delivery team
- Facilitated the full scrum event cycle for a nine-person product team, cutting sprint planning from three hours to ninety minutes by moving backlog refinement into a weekly session instead of planning day itself.
- Cleared 43 logged impediments across the year and escalated cross-team dependencies to the platform lead inside 24 hours, dropping average blocked time from seven days a sprint to under two.
- Raised sprint goal achievement from four sprints in twelve to eleven in twelve by coaching the team to forecast against measured throughput rather than the optimistic capacity used previously.
- Redesigned the retrospective format each quarter and tracked every action on the board, lifting action-item completion within two sprints from roughly one in five to 78 percent across the year.
- Coached the product owner through vertical story slicing, shrinking the average backlog item from thirteen points to three and all but ending the mid-sprint scope renegotiation that had cost the team two days.
Scaled delivery across multiple teams
- Facilitated scrum of scrums across four teams building one payments platform, surfacing shared dependencies eight to ten days earlier and cutting cross-team wait time from eleven days to three per quarter.
- Ran quarterly planning for 62 people across six teams, driving the dependency board and the confidence vote so 90 percent of committed objectives landed without triggering a mid-quarter replan.
- Introduced a shared definition of done across four teams, cutting defects escaping to staging by 41 percent in two quarters and settling a long-running argument over who owned integration testing.
- Coached three newly appointed scrum masters through their first six months with a fortnightly community of practice, taking every one of their teams above 80 percent sprint goal achievement by quarter three.
- Built a flow dashboard covering cycle time, throughput and work-in-progress age per team, retiring a velocity-only report that leadership had been reading as a productivity league table between squads.
Turning around a struggling team
- Inherited a team that had missed nine consecutive sprint goals and rebuilt its predictability by cutting work in progress from fourteen concurrent items to five, halving cycle time from 18 days to 9 in two months.
- Ran a blameless retrospective series that surfaced an unspoken single-person dependency in the core service, then coached deliberate pairing until three developers could ship in that codebase safely.
- Renegotiated how stakeholders reached the team by routing every ad hoc request into one refinement session, cutting mid-sprint interruptions from around nine a week to two within a single quarter.
- Restored forecasting credibility by coaching the team to size against its own historical cycle time, moving sprint forecast accuracy from 40 percent to 88 percent over the following eight sprints.
- Rebuilt the daily scrum around the board rather than person-by-person status, which cut the meeting from 25 minutes to 11 and moved the conversation onto the items closest to done each morning.
Top Scrum Master Skills
Scrum master job ads screen for facilitation craft first and tooling second. These are the skills worth naming explicitly:
Hard skills
- Sprint planning facilitation
- Daily scrum facilitation
- Backlog refinement
- Sprint review facilitation
- Retrospective design
- Impediment removal and escalation
- Servant leadership
- Agile coaching
- Product owner coaching
- Sprint forecasting
- Cycle time analysis
- Work-in-progress limits
- Cumulative flow diagrams
- Definition of done
- Definition of ready
- User story slicing
- Jira workflow and board configuration
- Scrum of scrums
- SAFe PI planning
- Kanban flow metrics
Soft skills:
- Facilitation
- Active listening
- Conflict resolution
- Coaching presence
- Neutrality
- Influence without authority
- Patience
Extra tips
Recruiters filter on framework keywords before a human reads the page, so write SAFe, LeSS or Nexus explicitly rather than the umbrella word agile.
If you have only run single-team scrum, say so plainly; claiming scaled experience you lack collapses in the first interview question about dependency management.
Scrum Master Certifications
One scrum credential is effectively the entry ticket for this role, and most job ads name either Scrum.org or Scrum Alliance by hand. These are the ones that carry weight:
-
PSM I
— Scrum.org No mandatory course and no renewal fee, so it is the cheapest credible entry credential. The assessment is genuinely hard, which is why hiring managers respect it.
-
PSM II
— Scrum.org Optional, and worth listing once you have two or more years facilitating. It tests applied coaching judgement rather than Scrum Guide recall.
-
CSM
— Scrum Alliance Requires a two-day course with a certified trainer and renews every two years. Widely recognised by recruiters, which matters for keyword screening.
-
A-CSM
— Scrum Alliance Optional next step on the Scrum Alliance track; needs twelve months of scrum master experience, so it doubles as proof of time served.
-
SAFe Scrum Master
— Scaled Agile Only worth the money if you are targeting enterprises running SAFe. In those job ads it is often a hard filter rather than a nice-to-have.
Common Scrum Master Resume Mistakes
These are the errors that get a scrum master resume rejected by people who have hired for the role before:
- Writing a project manager resume with scrum vocabulary sprinkled on top. Milestone plans, budget figures and resource allocation on a scrum master resume tell a hiring manager you were never actually serving the team.
- Listing scrum events as duties attended. "Facilitated daily standups" says nothing; what changed about the standup, and what did it cost or save the team?
- Reporting velocity as if higher is better. Velocity is a team-specific forecasting input, and quoting a rise as an achievement is the fastest way to reveal a surface understanding of flow.
- Claiming line management. Performance reviews, hiring and headcount belong to an engineering manager, and mixing them in makes the agile part of your profile look decorative.
- Leaving the product owner out entirely. Half the coaching in this role points at the backlog side, and omitting it reads as a facilitator who only ran meetings.
- Padding with agile manifesto principles. Nobody is screening for whether you can recite the values; they are screening for what happened to a real team while you served it.
- Hiding the developer or tester years you came from. That background is why an engineering team will listen to you, so put it on the page rather than burying it.
Scrum Master Resume FAQs
The questions candidates most often search before writing a scrum master resume:
Put the scrum events you facilitate, the impediments you removed with before-and-after blocked time, the flow metrics you moved, and the coaching you did with both the developers and the product owner. Add team size, framework flavour and one certification. Anything that reads like schedule or budget ownership belongs on a project manager resume, not this one.
In practice yes, because most job ads list PSM or CSM as a screening requirement even though scrum itself mandates nothing. PSM I from Scrum.org has no course requirement and no renewal fee; CSM from Scrum Alliance needs a two-day class and renews every two years. One is enough to clear the filter.
Lead with facilitation of the specific scrum events, impediment removal, agile coaching and flow metrics such as cycle time, throughput and work-in-progress limits. Follow with the tooling (Jira board and workflow configuration, Miro for remote facilitation) and the scaling framework you have worked in. Skip generic leadership adjectives; every candidate claims those.
One page up to about eight years of experience, two pages beyond that or when you have worked across multiple scaling frameworks. Scrum master resumes bloat easily because every sprint feels like an anecdote, so keep four to six bullets per role and cut anything that does not name a team, a change or a number.
No. A project manager owns scope, schedule and budget against a plan; a scrum master owns how effectively the team works and holds no delivery authority over it. Writing your resume as if the two are interchangeable is the single most common reason agile hiring managers pass on a candidate.
Lead with facilitation you already did inside a scrum team as a developer, tester, analyst or team lead, and name it precisely: running refinement, hosting retrospectives, chasing dependencies. Add PSM I to clear the certification filter, then quantify one change you drove in how your team worked. The sample above follows exactly that path from development into facilitation.
Include them only as context for a forecasting improvement, never as a performance score. "Moved sprint goal achievement from four in twelve to eleven in twelve" lands well; "increased velocity by 40 percent" invites a sceptical follow-up about story point inflation in almost every interview.
Get Started With Our
Free Resume Creator today!
Free sign-up. No credit card required.
