Odalys Prieto Senior Scrum Master, CSM, PMP Tucson, 85719, United States [email protected] · (520) 555-1650
11 September 2026
Ms. Ilona Kalinowska Delivery Catalina Benefits Technology Phoenix, United States
Application for Scrum Master, Catalina Benefits Technology
Dear Ms. Kalinowska,
I am applying for the Scrum Master post at Catalina Benefits Technology. I currently serve four teams totaling 33 people on a claims adjudication platform, two week sprints, and I have been with the lead team for 26 months. I also coach two newer scrum masters.
The change I would most want to bring is a Definition of Done rewrite. Three increments in a row were declared done and then could not be released, because migration scripts and rollback steps were being treated as release work rather than part of the increment. I took two sprints of evidence to the teams and the product owners, and we rewrote the Definition of Done to include migration scripts, rollback steps and updated runbooks. It slowed the first two sprints visibly and I had to defend it. Releasable increments then went from 6 of 13 sprints to 12 of 13 on the lead team, and sprints ending without a met Sprint Goal fell from 5 in 13 to 1 in 13.
Your posting mentions three teams sharing one release train and a recent move to a shared test environment. Environment contention is the problem I have most recently taken above team level: I brought two sprints of blocked-story data to our platform leadership group, a second environment was funded, and stories blocked in testing went from 31 percent to 9 percent over the following two quarters. That is where I would want to start, because it is usually the impediment no single team can fix and therefore the one nobody escalates.
I hold the Certified ScrumMaster credential from Scrum Alliance, renewed in 2025, and the PMP from the Project Management Institute, and I spent three years in quality assurance on the same product area before moving into this role. I can start on four weeks' notice. Thank you for your time.
Sincerely, Odalys Prieto, CSM, PMP
Summary
A scrum master cover letter works when it gives four team facts in the first paragraph and then describes one change you made to an event or artifact the 2020 Scrum Guide names, with what followed. This guide gives you a full adaptable letter, the openings that work, and what to write instead of velocity.
Scrum Master cover letter examples by experience level
A scrum master cover letter is a one-page letter that places you on four facts, then describes one change you made, in the vocabulary of the framework the job is named after.
The four facts are how many teams, how big, what cadence, and how long you stayed. The change is to an event or artifact the Scrum Guide names: Ken Schwaber and Jeff Sutherland's November 2020 revision at scrumguides.org defines three accountabilities, five events and three artifacts, each with a commitment attached. Almost every letter in the stack describes facilitating ceremonies instead, which says nothing about what you changed.
Guide to a scrum master cover letter
This guide and the corresponding scrum master cover letter example will cover:
- How to structure the letter, paragraph by paragraph
- The four team facts and why they belong in the first sentence
- What to write instead of velocity
- The openings that close a strong file
How to write a scrum master cover letter
| Paragraph | Its job | Length |
|---|---|---|
| Opening | The post and the four team facts | 2 to 3 sentences |
| Evidence | One event or artifact you changed, and what followed | 4 to 5 sentences |
| Fit | Something real about their teams | 3 to 4 sentences |
| Close | Credentials with issuing bodies, availability, thanks | 2 sentences |
Four facts, one sentence, first paragraph
"Scrum master to two teams of eight and nine, two week sprints, both held more than two years." That sentence places you better than a paragraph of description, and it takes eleven seconds to write.
It matters because the job is different at every scale. One team is a coaching job; four teams is a systems job. A reader who cannot tell will assume the smaller one, and the rest of your letter is read against that assumption.
The tenure number is the one candidates leave out and the one experienced readers look for. Improvements claimed over six months are hard to believe; the same claims over two years are evidence.
A scrum master cover letter example you can adapt
Dear Ms. Kalinowska,
I am applying for the Scrum Master post at Catalina Benefits Technology. I currently serve four teams totaling 33 people on a claims adjudication platform, two week sprints, and I have been with the lead team for 26 months. I also coach two newer scrum masters.
The change I would most want to bring is a Definition of Done rewrite. Three increments in a row were declared done and then could not be released, because migration scripts and rollback steps were being treated as release work rather than part of the increment. I took two sprints of evidence to the teams and the product owners, and we rewrote the Definition of Done to include migration scripts, rollback steps and updated runbooks. It slowed the first two sprints visibly and I had to defend it. Releasable increments then went from 6 of 13 sprints to 12 of 13 on the lead team, and sprints ending without a met Sprint Goal fell from 5 in 13 to 1 in 13.
Your posting mentions three teams sharing one release train and a recent move to a shared test environment. Environment contention is the problem I have most recently taken above team level: I brought two sprints of blocked-story data to our platform leadership group, a second environment was funded, and stories blocked in testing went from 31 percent to 9 percent over the following two quarters. That is where I would want to start, because it is usually the impediment no single team can fix and therefore the one nobody escalates.
I hold the Certified ScrumMaster credential from Scrum Alliance, renewed in 2025, and the PMP from the Project Management Institute, and I spent three years in quality assurance on the same product area before moving into this role. I can start on four weeks' notice. Thank you for your time.
Sincerely, Odalys Prieto, CSM, PMP
Openings that work
| Instead of | Use |
|---|---|
| I am a passionate servant leader with a love of agile | Scrum master to four teams totaling 33 people, two week sprints, 26 months with the lead team |
| I facilitate all scrum ceremonies and remove impediments | I rewrote the Definition of Done after three increments could not be released |
| I increased my team's velocity by 40 percent | Releasable increments went from 6 of 13 sprints to 12 of 13 |
The four team facts, in one sentence
| Fact | Why a reader wants it |
|---|---|
| How many teams | Whether this is a coaching job or a systems job |
| How many people on each | Whether your facilitation experience matches their shape |
| Sprint length | Places you in their cadence |
| How long with the team | Makes every improvement you claim believable or not |
Add coaching if you do it. "Coach to two newer scrum masters" costs six words and is a seniority signal.
What to say instead of velocity
Velocity is a planning input for one team. Story points are calibrated locally, so the number does not compare between teams, and a rise can be produced by re-estimating rather than improving. A letter leading with a velocity increase reads as one from someone who has not thought about what the number is for. Four replacements, all of which travel between teams.
| Instead of velocity | Use |
|---|---|
| Velocity rose 40 percent | Releasable increments went from 6 of 13 sprints to 12 of 13 |
| The team became more predictable | Sprints ending without a met Sprint Goal fell from 5 in 13 to 1 in 13 |
| We removed blockers faster | Stories blocked in testing fell from 31 percent to 9 percent over two quarters |
| Quality improved | Post-release change requests fell from 9 a quarter to 2 |
Open with the four team facts. Pick one change to a named event or artifact. Say what it cost before it worked. Give a before and an after over a stated number of sprints. Name the issuing body for each credential.
Do not lead with velocity. Do not list the five events as an accomplishment. Do not call yourself a servant leader without an example. Do not describe a transformation you watched. Do not stack four acronyms in the closing line.
No Handbook profile for the title, and a wide occupation beneath it
The Bureau of Labor Statistics publishes no Handbook profile under the title scrum master. The nearest published occupation is project management specialists, with a median annual wage of $102,320 in May 2025, 1,094,300 jobs in 2025, a projected 7 percent growth and about 76,500 openings a year through 2035 (BLS Occupational Outlook Handbook, May 2025 wage data and 2025-35 projections, published 27 August 2026).
That occupation spans far more than software: professional, scientific and technical services accounted for 28 percent of its 2025 employment and construction for 22 percent, with May 2025 sector medians running from $120,700 in finance and insurance to $98,730 in construction (BLS, 2025 and May 2025). Above it sits computer and information systems managers, with a median annual wage of $175,140 in May 2025 (BLS, May 2025).
A letter showing change above the level of one team argues toward that band; one about ceremonies argues at the bottom of the band below.
Length, format and sending it
One page, four paragraphs, 280 to 400 words. PDF unless the portal says otherwise, named for yourself and the post: odalys-prieto-scrum-master-cover-letter.pdf.
Address a person. Delivery leadership is usually named in the posting or on the company's site, and on a role built around working relationships a generic salutation is a poor first note.
Use the same figures as your resume so the two agree. Our scrum master resume example uses the numbers here.
Key takeaways
- Open with four team facts: how many teams, how big, what cadence, how long.
- Pick one change to an event or artifact the Scrum Guide names.
- Say what the change cost before it worked.
- Give a before and an after over a stated number of sprints.
- Never lead with velocity; use releasable increments or Sprint Goals met.
- Name one real thing about their teams.
- List credentials with their issuing bodies and renewal state.
Write your scrum master cover letter in 10 minutes with our AI cover letter builder.
Scrum master cover letter questions, answered
How long should a scrum master cover letter be?
One page, four paragraphs, 280 to 400 words. The evidence paragraph carries most of it, because a change to an artifact needs its cause, its cost and its result.
What if I have only ever served one team?
Say so in the first sentence and let the tenure work for you. Two years with one team of seven is a stronger claim than six months each across four, because the improvements are attributable.
Should I name the Scrum Guide in the letter?
Naming the artifact or event you changed does the work; a reader who knows the Guide recognizes the vocabulary. Quote the document only if the posting is about establishing Scrum where it does not exist, in which case the accountability it sets out, establishing Scrum as defined in the Scrum Guide, is what the letter can hang on.
Which certifications should I mention?
The ones you hold, with the issuing body and the state of the cycle. Scrum Alliance renews the Certified ScrumMaster every two years using Scrum Education Units (Scrum Alliance, retrieved 16 September 2026), and the Project Management Institute requires 60 professional development units per three-year cycle for the PMP (PMI, retrieved 16 September 2026).
How do I write this letter if my team never really followed Scrum?
Write what happened and where it diverged, in the Guide's terms. "Two week sprints, no separate Product Owner, so backlog decisions sat with a business analyst and I ran a weekly refinement session" is specific, honest, and gives a reader something to ask about.