Scrum Master Exam: Mastering the Scrum Guide 2020 (2026 Edition)

If you're preparing for the PSM I or CSM exam, you've probably already discovered that memorizing definitions won't be enough. Both Scrum.org and Scrum Alliance design their certifications to test your ability to apply Scrum thinking — not just recite it. That's what makes the 2020 Scrum Guide so central to your success. It's short (only 13 pages), but every sentence carries weight, and exam questions are deliberately written to expose shallow understanding.

The 2020 revision was a significant update. Ken Schwaber and Jeff Sutherland stripped out prescriptive language, removed the Development Team as a separate sub-team, and leaned heavily into empiricism, self-management, and the product-focused nature of Scrum. If you studied an older guide or used outdated prep materials, you may actually be learning the wrong answers. This article is built specifically around the 2020 guide and what it means for your exam in 2026.

Think of this as your coaching session — not a dry summary. We'll work through each core concept, flag the traps that catch candidates off guard, and give you the mental models you need to answer scenario-based questions with confidence. Let's get into it.

---

Why the 2020 Scrum Guide is the Foundation of Your Exam

Both Scrum.org (PSM I) and Scrum Alliance (CSM) explicitly base their certification content on the 2020 Scrum Guide. Scrum.org publishes this openly, and Scrum Alliance instructors are required to teach from it. That means every question about roles, events, artifacts, and Scrum theory on your exam traces directly back to that document.

What changed in 2020 matters for your exam. The biggest conceptual shift was the move away from "the Development Team" as a distinct group within the Scrum Team. In the 2020 guide, the Scrum Team consists of one Scrum Master, one Product Owner, and Developers — not three separate tiers. This sounds subtle, but it has real implications for exam questions about accountability and decision-making. Questions that ask "who is responsible for the Sprint Backlog?" now have a cleaner answer: the Developers. No more parsing whether that means "the Development Team" or "the Scrum Team."

The 2020 guide also made self-management non-negotiable. Where previous versions used the term "self-organizing," the 2020 guide says Scrum Teams are "self-managing," meaning they decide internally who does the work, how it's done, and what to work on. Exam writers love testing whether you understand that this doesn't mean chaos — it means the team has the autonomy and accountability to operate without being told how to do their jobs.

---

The 3 Scrum Accountabilities: Roles vs. Responsibilities

The 2020 Scrum Guide deliberately uses the word "accountability" rather than "role." This is intentional and exam-relevant. An accountability implies ownership and answerability — not just a job title. When you see a question asking who is accountable for something, the answer is never vague.

The Scrum Master

The Scrum Master is accountable for the Scrum Team's effectiveness. This is the most misunderstood accountability on the exam. Candidates often think the Scrum Master is accountable for the team's output or delivery — they're not. The Scrum Master's job is to ensure the team understands and enacts Scrum, removes impediments, and operates in an environment where they can do their best work.

The 2020 guide describes the Scrum Master as a servant leader. In practice, this means a Scrum Master isn't a project manager assigning tasks or a meeting scheduler. Imagine a team where Developers feel pressured by a middle manager who keeps "attending" Sprint Planning and suggesting tasks. The Scrum Master's response isn't passive — they actively protect the team's autonomy, coach the organization on Scrum values, and address that dysfunctional dynamic directly.

For the exam, remember that the Scrum Master serves three entities: the Scrum Team, the Product Owner, and the broader organization. Questions often describe scenarios where the Scrum Master must coach stakeholders who are bypassing the Product Owner, or a team that doesn't know how to write a proper Definition of Done. In both cases, the Scrum Master coaches and facilitates — they don't command.

The Product Owner

The Product Owner is accountable for maximizing the value of the product resulting from the Scrum Team's work. They are the sole person responsible for managing the Product Backlog — ordering it, ensuring items are clear, and making sure the team understands the work to be done.

A critical exam point: the Product Owner may delegate Product Backlog management tasks to others, but they remain accountable. If a stakeholder wants to change a Sprint mid-Sprint, the Product Owner is the appropriate person to negotiate scope — not the Scrum Master, not the Developers. Respect that boundary in your answers.

The Developers

Developers are accountable for creating a usable Increment every Sprint. They create the Sprint Backlog, adapt their plan daily (via the Daily Scrum), and are responsible for the Definition of Done. The 2020 guide no longer restricts "Developers" to software engineers — any person on the Scrum Team who works on the product Increment is a Developer.

---

The 5 Scrum Events: Timeboxing and Purpose

Every Scrum event is timeboxed. This is one of the most heavily tested areas on both PSM I and CSM exams, and the questions often try to catch you on the exact timebox or the purpose of an event rather than just its name.

Sprint

The Sprint is the container for all other events — a timebox of one month or less. The 2020 guide is explicit: no changes are made that endanger the Sprint Goal, quality does not decrease, the Product Backlog is refined as needed, and scope may be clarified with the Product Owner. Sprints should never be extended. If something goes wrong mid-Sprint, the Product Owner can cancel the Sprint — but only the Product Owner.

Sprint Planning

Sprint Planning is timeboxed to 8 hours for a one-month Sprint (shorter for shorter Sprints). The 2020 guide says Sprint Planning addresses three topics: why is this Sprint valuable (the Sprint Goal), what can be done (selecting Product Backlog items), and how the chosen work will get done. Notice that the Scrum Master facilitates this event — they don't decide the Sprint Goal, and neither does the Product Owner alone. The Sprint Goal is a collaborative commitment.

Daily Scrum

The Daily Scrum is 15 minutes, held every day of the Sprint, for the Developers. Not the Scrum Master. Not the Product Owner (unless they're also a Developer). The 2020 guide removed the three prescribed questions ("What did I do yesterday...") to give teams more flexibility in how they structure it. The purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.

Sprint Review

The Sprint Review is timeboxed to 4 hours for a one-month Sprint. It's a working session — not a demo or a status meeting. The Scrum Team and stakeholders collaborate on what was accomplished and what comes next. The output is a revised Product Backlog reflecting new information and priorities.

Sprint Retrospective

The Sprint Retrospective is 3 hours for a one-month Sprint and it comes after the Sprint Review and before the next Sprint Planning. It's the team's opportunity to inspect itself — how they work, their relationships, tools, and processes — and create actionable improvements. The 2020 guide says the Scrum Master participates as a fellow team member, while also ensuring the event is productive and positive.

---

The 3 Scrum Artifacts and Their Commitments

The 2020 Scrum Guide introduced a powerful structural change: each artifact now has an associated commitment. This ties the artifacts to empiricism and ensures transparency. Exam questions frequently test whether you know which commitment belongs to which artifact.

Artifact	Commitment
Product Backlog	Product Goal
Sprint Backlog	Sprint Goal
Increment	Definition of Done

Product Backlog and the Product Goal

The Product Backlog is an ordered, emergent list of everything needed to improve the product. It's never complete — it evolves. The Product Goal describes the future state of the product and serves as the long-term objective for the Scrum Team. Only one Product Goal is pursued at a time.

Sprint Backlog and the Sprint Goal

The Sprint Backlog is composed of the Sprint Goal (the why), the set of Product Backlog items selected for the Sprint (the what), and an actionable plan for delivering the Increment (the how). It's owned by the Developers and updated throughout the Sprint. If the Developers discover the selected work is more than expected, they negotiate scope with the Product Owner — but the Sprint Goal remains fixed.

Increment and the Definition of Done

An Increment is a concrete stepping stone toward the Product Goal. Multiple Increments can be created during a Sprint. The Definition of Done is a formal description of the state required for the Increment to be considered complete. If an item doesn't meet the Definition of Done, it cannot be included in the Increment. This is non-negotiable in Scrum.

---

Empiricism: The Heart of Scrum Theory

Scrum is founded on empiricism — the idea that knowledge comes from experience and that decisions should be based on observation. The 2020 guide identifies three pillars of empiricism: transparency, inspection, and adaptation.

In real-world terms: if a team's burndown chart shows they're behind on Sprint Goal delivery but nobody talks about it, transparency is failing. If the Scrum Master doesn't facilitate honest retrospectives, adaptation suffers. Each Scrum event is essentially an opportunity to inspect and adapt — Sprint Planning inspects the Product Backlog and adapts the plan; the Daily Scrum inspects daily progress and adapts the day's work.

The 2020 guide also added lean thinking as a second pillar of Scrum's foundation alongside empiricism. Lean thinking focuses on reducing waste and focusing on essentials. For exam purposes, understand that this reinforces the "enough, not excessive" principle in Scrum — just enough planning, just enough documentation, just enough process to deliver value.

---

Scrum Values: How They Influence Situational Questions

The five Scrum values — Commitment, Focus, Openness, Respect, and Courage — appear directly in situational exam questions more than most candidates expect. You won't just be asked to list them. You'll be asked what a Scrum Master should do when they're being violated.

Consider this scenario: a Developer tells the Scrum Master privately that the Sprint Goal is unrealistic but doesn't raise it in the Sprint Review. Which value is being compromised? Openness and Courage. What should the Scrum Master do? Coach that Developer to raise their concern directly, and create a safe environment where honest feedback is welcome.

Respect shows up when Developers are dismissed by a Product Owner who sets unrealistic deadlines without consulting the team. Commitment shows up when the team agrees to a Sprint Goal and then gets distracted by unrelated requests. Focus reminds us that the Sprint Goal is what the team concentrates on — not every stakeholder request that comes through Slack.

These values aren't decorative. When you see a scenario question that seems to have two reasonable answers, check which one better upholds the Scrum values and the principle of servant leadership. That's often your tiebreaker.

---

Common Exam Traps: What to Avoid in 2026

After studying hundreds of exam questions, there are patterns in how both PSM I and CSM exams mislead candidates. Here's what to watch for:

• "The Scrum Master should assign tasks" — Wrong. Developers decide how they do their own work. Self-management means nobody tells Developers what to do.
• "The Product Owner can change the Sprint Goal mid-Sprint" — Wrong. The Sprint Goal is fixed. Scope can be negotiated, but the goal is a commitment.
• "The Daily Scrum is for the whole Scrum Team" — Wrong. It's for the Developers. The Scrum Master attends only if needed as a facilitator or if they're also a Developer.
• "Scrum requires story points" — Wrong. The 2020 guide doesn't mention story points, velocity, or burndown charts. These are common practices but not Scrum.
• "The Scrum Master is the team leader" — Wrong. The Scrum Master is a servant leader — they lead through influence, coaching, and removing impediments, not authority.
• "Sprints can be extended if needed" — Never. A Sprint is never extended. Start a new Sprint after the previous one ends at its timebox.

Also beware of questions where the "right" answer feels counterintuitive. For example: a stakeholder insists on attending Daily Scrum and asking questions. The Scrum Master's job is to protect the event's purpose, not to be polite and let dysfunction continue. The Scrum Master would address this — probably by explaining to the stakeholder that Daily Scrum is for Developers to sync, and offering an alternative touchpoint.

---

Final Study Tips for Exam Day Success

• Read the 2020 Scrum Guide at least three times. The first time for context, the second time to highlight commitments, timeboxes, and accountabilities, and the third time to challenge yourself on "why" questions.
• Don't just know the rules — understand the reasoning. Exam questions rarely test rote recall. They test your judgment in complex situations.
• For PSM I: Scrum.org's Open Assessments are free and genuinely close to real exam difficulty. Use them regularly.
• For CSM: Your training course is required, but don't assume passing the class is enough preparation. Supplement with scenario practice.
• Time yourself. PSM I gives you 60 minutes for 80 questions — that's 45 seconds per question. Practice under pressure.
• Flag and return. Don't let one hard question derail your rhythm. Flag it and come back.
• Know the purpose of every event. If you can articulate why each event exists in one sentence, you'll handle most scenario questions.

---

Key Takeaways

• The 2020 Scrum Guide replaced "Development Team" with "Developers" and "self-organizing" with "self-managing" — both are exam-relevant changes.
• Each accountability (Scrum Master, Product Owner, Developers) has a specific, non-overlapping area of ownership.
• Each artifact has a commitment: Product Goal, Sprint Goal, and Definition of Done.
• Every Scrum event is timeboxed — know the exact timeboxes for a one-month Sprint.
• Scrum is grounded in empiricism: transparency, inspection, and adaptation are not optional.
• Scrum values inform situational questions — especially Courage, Openness, and Respect.
• The Scrum Master never assigns work, never extends Sprints, and always serves rather than commands.

---

Conclusion

Passing the PSM I or CSM isn't about grinding through flashcards — it's about building a genuine understanding of how and why Scrum works. When you internalize the principles behind the 2020 Scrum Guide, the right answer to even the trickiest exam question becomes clearer because you're thinking like a Scrum practitioner, not a test-taker.

The best way to seal that understanding is by practicing with scenario-based Scrum Master questions that mirror the real exam format. Working through situations where the Scrum Master has to navigate stakeholder pressure, team dysfunction, or organizational resistance trains your judgment in a way that reading alone can't. Build that practice into your preparation from day one — it's what separates candidates who pass confidently from those who just barely scrape through.

---

Frequently Asked Questions

Q: What is the difference between PSM I and CSM in terms of exam content?

Both certifications are based on the 2020 Scrum Guide, but the path differs. PSM I (Scrum.org) is a rigorous 80-question online assessment with no mandatory training — it's self-paced and available anytime. The CSM (Scrum Alliance) requires completing a two-day course from a Certified Scrum Trainer before you can take a shorter online exam. PSM I is generally considered more challenging in terms of exam difficulty, while CSM emphasizes the training experience itself.

Q: Can the Product Owner cancel a Sprint, and under what circumstances?

Yes — and only the Product Owner can cancel a Sprint. According to the 2020 Scrum Guide, a Sprint can be cancelled if the Sprint Goal becomes obsolete. This might happen if the company changes strategic direction, a competitor releases a product that makes the current work irrelevant, or external circumstances make the Sprint Goal unachievable. Cancellations are rare and disruptive, which is why the Product Owner — not the Scrum Master or Developers — holds this decision.

Q: Does the 2020 Scrum Guide require specific engineering practices like TDD or CI/CD?

No. The 2020 Scrum Guide intentionally removed prescriptive technical practices to make Scrum applicable across industries and contexts — not just software development. Practices like Test-Driven Development, Continuous Integration, or pair programming are valuable complementary techniques (often associated with Extreme Programming), but they are not part of Scrum itself. For your exam, if a question implies that a specific engineering practice is required by Scrum, that's a red flag — Scrum does not mandate technical practices.