This has been quite some time in the making.
After reattempting the assessment in December 2025, I can finally, finally say it:
I’m a certified Professional Scrum Master III (PSM III)!
And I’m not exaggerating when I say this was one of the hardest exams I’ve ever taken.
PSM III is a stress test of how you think, how you write, and whether you can stay true to Scrum when the scenario gets messy.
This blog post is how I approached it. This post is not intended to be a definitive guide. Just as the approach that worked for me.
TL;DR: here is what made the difference for me
- Treat every question as a Scrum Master scenario, not an academic prompt
- Anchor answers in empiricism + Scrum Values + Done
- Practice timed writing more than reading
- Use a repeatable answer structure to prevent rambling
- Keep moving: a “good enough” answer beats a perfect answer you never finish
Empiricism, applied
My first attempt was in 2023. I didn’t pass.
That initial disappointment quickly turned into something more useful: the feedback I received exposed gaps I didn’t know I had. It reframed the exam from “a certification I wanted” into “a mirror I needed”.
The most important lesson was simple:
No amount of reading beats lived experience and ongoing reflection.
Since that first attempt, in terms of knowledge, I went wider (agile leadership, evidence-based management, scaling) and deeper (the Product Owner perspective, the Developer perspective, and the realities of product thinking, DevOps, and quality). Those perspectives force you to understand Scrum as a system, not a checklist.
And honestly, my workplace mattered a lot in that journey. A heartfelt thanks to the team at railcube. Their curiosity, willingness to experiment, and trust turned our environment into a real learning lab. The feedback loops were relentless in the best way.
That is empiricism at play: you learn Scrum by doing Scrum, seeing what happens, and adapting. Over and over.
It took me two more attempts to get here. I’m grateful for the extra mileage, as it contributed to my performance in the final run.
What the assessment feels like
Imagine writing 24 mini-essays while the room slowly fills with hungry wolves.
Time limit: 150 minutes
Questions: 24
Format: essay (no multiple choice!)
You’re thinking while typing, editing while the clock keeps moving, and trying to be both accurate and clear in a small text box. The pressure is real and time flies.
Grading takes up to four weeks. In my case, the grading came back in six days.
The result email breaks down any feedback the examiner had based on your answers, plus how many answers did not meet expectations, met expectations, and exceeded expectations.
My outcome:
- 21 answers met expectations
- 3 answers did not meet expectations
- 0 answers exceeded expectations (a little painful, not gonna lie)
But as I say with boss fights in video games: a clear is a clear. A pass is a pass.
The mindset that made the difference
If I had to reduce PSM III to one sentence:
Answer like a Scrum Master, not like a student.
Here’s what that means in practice:
1️⃣ Stay true to Scrum, especially when it’s tempting not to
Many questions are designed to lure you into: “Well, at my company we…”
That’s dangerous.
You can use real experience, but your solution still needs to align with:
- Scrum accountabilities
- Scrum events
- Scrum artifacts and commitments
- Empiricism: Transparency, Inspection, Adaptation
- Scrum values
If your answer quietly bends Scrum and justifies it with “pragmatism”, graders will see it.
2️⃣ Think in empiricism, not in “best practices”
When a scenario goes wrong, I trained myself to ask:
- What isn’t transparent?
- What aren’t we inspecting?
- What do we need to adapt?
That kept my answers grounded and consistent.
3️⃣ Lead like a servant leader, not a project manager
PSM III often tests whether you “solve” problems by controlling people.
I aimed to show:
- facilitation
- coaching
- restoring healthy boundaries
- building shared understanding
- enabling self-management
Sometimes you need to be firm. But it’s rarely about “telling the team what to do”.
4️⃣ Protect professionalism and ethics
Some questions have an ethical edge: cutting corners, hiding work, faking progress, and bypassing quality.
My rule: never trade short-term comfort for long-term damage.
A Scrum Master is a guardian of transparency and integrity.
How I prepared (what actually mattered)
1️⃣ Have real mileage
PSM III assumes you’ve been in the arena.
I actively reflected on situations like conflict, stakeholder pressure, technical debt, self-management, and “Done” being under threat. Then I compared my instincts to the Scrum Guide: where was I aligned, and where was I rationalizing shortcuts?
That reflection is both uncomfortable and extremely useful.
2️⃣ Internalize the Scrum Guide
It’s not just about memorizing the words, but also understanding the reasoning behind them.
For PSM III, you need to answer quickly, “Why does Scrum work this way?” If you are only familiar with what Scrum states, you might find yourself at a standstill. If you understand why, you can navigate almost any scenario.
3️⃣ Master the Scrum values
The values are not window dressing. They are often the hidden key in the situation.
If a team avoids hard truths, you’re likely looking at Openness and Courage. If stakeholders keep thrashing priorities, Focus and Respect are usually in play.
4️⃣ Get into the mindset with some great resources
A few that helped me:
- Scrum – A Pocket Guide (Gunther Verheyen), great to reinforce the “why” of Scrum
- Scrum Mastery (Geoff Watts), great insights into the servant-leader mindset
- Scrum Insights for Practitioners (Hiren Doshi), summaries and tips aligned with the Scrum Guide
- Scrum.org learning paths and trainer blogs, these highlight common misunderstandings and advanced topics.
Furthermore, if you have the time, I can always heartily recommend books in the Professional Scrum series. Great reads that support the various Scrum.org courses.
5️⃣ Train the muscle: timed writing
This was the biggest one. If you only do one thing: do this.
The knowledge isn’t the bottleneck. Typing coherent answers under time pressure is.
I practiced with PSM III-style questions (TheScrumMaster.co.uk has some great free and paid practice scenarios) and forced myself to write full answers with a strict timer.
How I structured my answers (fast, not shallow)
As time is the true challenge in the assessment, there is a big risk you may spiral into large essays. I used a repeatable pattern for my answers, which also made it it easier for a grader to scan.
1️⃣ One-sentence stance
Start with the core move you’d make.
2️⃣ Why (tied to Scrum)
Link to empiricism, values, accountabilities, or “Done”.
3️⃣ Concrete actions
Bullet points. Numbered steps. Short sentences.
Optional: a brief experience line
Only if it strengthens the answer and you still have time.
Let’s practice. This is a practice scenario:
You are the Scrum Master of a product team delivering a customer-facing feature. The Developers say the work is “basically done” and want to present it in the Sprint Review to show progress.
However, you discover the following:
Several automated tests are failing and were temporarily disabled “to keep momentum.”
The feature works in a developer environment but has not been validated in an environment that resembles production.
The team has open bugs they describe as “minor” and “we’ll fix them next Sprint.”
The Product Owner is under pressure from management to demonstrate delivery, and suggests calling it “Done enough” for the Review.
The team’s current Definition of Done exists, but it is vague and inconsistently applied. Stakeholders are expecting to see usable value.
Question:
As Scrum Master, what would you do in this situation? Explain your reasoning and include concrete steps you would take in the next 24–48 hours and how you would prevent this pattern from repeating.
1️⃣ One-sentence stance
I wouldn’t support presenting this work as “Done” in the Sprint Review.
2️⃣ Why (tied to Scrum)
The Scrum Guide states that only completed Increments that meet the Definition of Done can be released. In the Sprint Review, you can show progress, but you must be transparent about what is and is not Done. Disabled tests, untested environments, and known bugs mean we don’t have a Done Increment. Showing work that is “Done enough” creates false transparency and damages stakeholder trust.
3️⃣ Concrete actions
– Within the next 24-48 hours:
I’d bring the Developers and the PO together for an urgent inspection. I’d ask the Developers to re-enable the failing tests but also ensure they’re visible in the build pipeline. I’d also ask them to validate the feature in a production-like environment. We’d decide what truly meets the DoD and can be presented as usable value. Items with open bugs that break the DoD must return to the Product Backlog.
Before Sprint Review, I’d help the PO prepare an honest message for stakeholders. We’d show what is truly “Done” and openly explain what is not releasable and why. This turns a difficult moment into an opportunity for real inspection or adaptation.
– To prevent this pattern from repeating:
I’d use the Sprint Retrospective to focus on why it happened. I’d help the team rewrite the DoD to be specific and binary (i.e., “All automated tests pass” and “Validated in staging environment”). I’d also coach management that cutting quality to meet deadlines usually slows delivery later. A clear, shared DoD protects the team, the product, and stakeholder trust.
4️⃣ Optional: brief experience line
In my experience, the moment “Done enough” becomes acceptable, technical debt compounds and trust erodes quickly.
Exam day checklist
✅ Set an alarm for 5 minutes per question. And then move on. So, don’t get stuck. Write a solid baseline answer and move on.
✅ Answer what’s asked. If there are two separate questions, deliver two, clearly labeled separate answers.
✅ Use bullet points. Clarity beats prose.
✅ Use correct Scrum terminology. “Developers”, not “dev team”. “Sprint Review”, not “demo”.
✅ Define a good set of abbreviations. I.e. I consistently used SM for Scrum Master. Saves typing.
✅ Open book feels like a blessing, but it’s not feasible. Quick keyword checks are fine. Researching is not: you simply do not have the time!
✅ Control your environment. No notifications, no interruptions, have some water nearby.
Closing thoughts
Getting PSM III feels like the apex of a long personal arc: effort, ambition, commitment, and overcoming a lot of self-doubt.
It also reaffirmed something I deeply believe:
Experience shapes the Scrum Master.
If you’re considering PSM III, treat it as more than an exam. Treat it as a forcing function for growth.
Inspect and adapt. Empiricism rocks!