Scrum Master Exam: Top 20 Situational Questions & Answers (2026)

If you've been studying for your PSM I or CSM certification, you've probably noticed something: memorizing the Scrum Guide isn't enough. The questions that trip up even well-prepared candidates aren't the definitional ones ("How long is a Sprint Review?") — they're the situational ones. The ones where two answers both sound reasonable, but only one reflects genuine Scrum thinking.

That's what this guide is about. We're going to walk through 20 of the toughest situational question types you'll encounter, explain the reasoning behind the correct answers, and help you build the kind of Scrum judgment that makes these questions feel obvious rather than agonizing.

The key insight most candidates miss is this: the exam isn't just testing what you know about Scrum — it's testing how you think like a Scrum Master. And that's a different skill entirely. So let's build it.

---

Why Situational Questions are the Hardest Part of the PSM I & CSM

Situational questions are designed to probe something deeper than recall. They put you in the middle of a messy, real-world scenario — a stakeholder barging into a Sprint, a Developer who refuses to collaborate, a Product Owner who keeps changing requirements mid-Sprint — and ask you to choose the most appropriate response.

The difficulty isn't ambiguity about Scrum rules. It's that the wrong answers are usually things that a reasonable manager or team lead might do in real life. Escalating to HR when there's team conflict? Reasonable. Letting the Product Owner adjust the Sprint Backlog mid-Sprint if the team agrees? Sounds flexible and collaborative. But neither of these reflects Scrum Guide 2020 principles, and both will cost you points.

The PSM I exam (from Scrum.org) is particularly rigorous in this regard. With an 85% passing threshold and questions that frequently involve multi-select scenarios, there's no room for fuzzy thinking. The CSM exam (from Scrum Alliance) is slightly more forgiving, but situational questions still form the backbone of where candidates lose marks. Understanding why the Scrum framework is designed the way it is — not just what it says — is your real edge here.

---

The Scrum Master Mindset: How to Approach Any Exam Scenario

Before diving into specific scenarios, let's establish a mental framework. When you read a situational question, you should be filtering your answer through three lenses simultaneously.

Lens 1: Is this servant leadership in action? The Scrum Guide 2020 defines the Scrum Master as a "true leader who serves the Scrum Team and the larger organization." This is not a passive role. Servant leadership means actively removing impediments, coaching, facilitating — but never commanding, directing, or taking ownership away from the people doing the work.

Lens 2: Does this protect self-management? The 2020 Scrum Guide made a significant shift — it replaced "self-organizing" with "self-managing." This is subtle but important. Self-managing teams decide who does the work, how it gets done, and what gets done within the Sprint Backlog. Any answer that has the Scrum Master assigning tasks, deciding technical approaches, or making commitments on the team's behalf is almost certainly wrong.

Lens 3: Does this uphold Scrum values? Courage, Focus, Commitment, Respect, and Openness aren't decorative additions to the Scrum Guide. They're the behavioral foundation. When you see a scenario about a team member who's underperforming or a Scrum Master who needs to push back against a VP, the right answer usually involves one of these values in action.

A Practical Tip for Exam Day

When you're stuck between two answers, ask yourself: Which answer treats the Developers, Product Owner, or organization as capable adults who need facilitation and transparency — not supervision and control? The answer that respects autonomy while enabling accountability is almost always right.

---

Handling Stakeholder Interference: Exam Scenarios and Correct Actions

This is one of the most commonly tested scenario categories, and it maps directly to one of the Scrum Master's core responsibilities: protecting the Scrum Team from external interference during the Sprint.

Scenario Type 1: A Manager Assigns Work Directly to Developers

"During Sprint 3, the head of marketing approaches two Developers directly and asks them to complete a data report by end of week. The Developers agree. What should the Scrum Master do?"

The wrong answers usually involve the Scrum Master reporting this to HR, telling the Developers they were wrong, or simply documenting the incident. The correct action is for the Scrum Master to coach the Developers on directing external requests through the Product Owner, and to educate the marketing manager on how Scrum works — specifically, that all work requests go through the Product Backlog.

The principle at play: the Sprint Backlog is owned by the Developers. New work mid-Sprint that isn't aligned with the Sprint Goal is an impediment. The Scrum Master doesn't punish anyone — they use this as a coaching and transparency opportunity.

Scenario Type 2: Stakeholders Attend the Daily Scrum

"A senior stakeholder starts attending the Daily Scrum regularly and begins asking questions during the event. What should the Scrum Master do?"

Many candidates choose "ask the stakeholder to observe silently" — which sounds like a reasonable compromise. But the Scrum Guide is clear: the Daily Scrum is for the Developers. The Scrum Master's job is to ensure this event happens and that its purpose is protected. The correct answer involves the Scrum Master facilitating a conversation about the event's purpose and, if the presence is disruptive, respectfully redirecting the stakeholder to other forums like the Sprint Review.

Key exam insight: Stakeholder engagement is important in Scrum — but it belongs in the Sprint Review, not the Daily Scrum. Questions that conflate these will catch you if you're not careful.

---

Managing Team Conflict and Self-Management Challenges

Team dynamics questions are tricky because they tempt you into management-style answers. If two Developers are in conflict, shouldn't the Scrum Master step in and resolve it? Not exactly.

Scenario Type 3: Developers Can't Agree on a Technical Approach

"Two senior Developers disagree on the architecture approach for a key feature. The argument is slowing down the Sprint. What should the Scrum Master do?"

The wrong answer: the Scrum Master researches the options and makes a recommendation. That's a technical decision, and the Scrum Master has no authority there (and may not have the expertise either). The correct approach is to facilitate a structured conversation where the team can surface the tradeoffs, make a decision together, and move forward. The Scrum Master might use techniques like dot voting or simply timeboxing the discussion — but the decision belongs to the Developers.

Scenario Type 4: One Developer Is Not Collaborating

"A Developer consistently works in isolation, doesn't share progress at the Daily Scrum, and rarely helps teammates. Sprint velocity is declining. What should the Scrum Master do?"

This scenario tests whether you'll reach for a management lever (performance review, escalation to HR) or a Scrum Master lever (coaching, transparency, fostering values). The right answer involves the Scrum Master having a direct, respectful conversation with the Developer — not on their performance, but on how their behavior affects the team's ability to self-manage and achieve the Sprint Goal. The Scrum values of Respect and Openness are directly relevant here.

Important nuance: If the behavior persists and genuinely becomes an impediment to the team, the Scrum Guide does allow the Scrum Master to remove impediments — which in extreme cases might involve escalating to HR or management. But that's a last resort, not a first response. Exam questions almost never make that the correct first answer.

---

What to Do When the Product Owner or Developers Struggle

These scenarios test your understanding of the Scrum Master's coaching role toward each Scrum Team member — not just the team as a whole.

Scenario Type 5: The Product Owner Keeps Changing Sprint Backlog Items Mid-Sprint

"The Product Owner frequently asks Developers to swap Sprint Backlog items for 'more urgent' ones. Developers are frustrated but comply. What should the Scrum Master do?"

This is a classic misunderstanding of Product Owner authority. The Product Owner owns the Product Backlog — not the Sprint Backlog. Once Sprint Planning is done, the Sprint Backlog belongs to the Developers. The Scrum Master should coach the Product Owner on this boundary and facilitate a conversation about the impact this pattern has on the Sprint Goal and team morale.

The Scrum Guide 2020 is explicit: during the Sprint, the Sprint Goal is fixed, and the scope can be renegotiated in collaboration with the Product Owner — but only the Developers can adjust their Sprint Backlog.

Scenario Type 6: The Product Owner Is Unavailable

"The Developers have questions about acceptance criteria that only the Product Owner can answer. The PO is unreachable for three days. Work is stalling. What should the Scrum Master do?"

The wrong answer: the Scrum Master answers the questions on behalf of the Product Owner. Never. The Scrum Master is not a proxy for the Product Owner. The correct answer is to remove the impediment by escalating the PO's unavailability — to the organization if necessary — while coaching the Developers to make reasonable assumptions where possible and flag these clearly. Transparency is the value at stake here.

Scenario Type 7: Developers Don't Have the Skills for Sprint Backlog Items

"Halfway through the Sprint, the team realizes they lack expertise in a required technology. They can't complete three key items. What should the Scrum Master do?"

The Scrum Master facilitates the conversation, but the solution is the team's to find. They might pair with an external expert, reduce scope, or renegotiate with the Product Owner. The Scrum Master shouldn't independently source contractors or solve the problem unilaterally. This scenario also tests whether you'd cancel the Sprint (wrong — only the Product Owner can cancel a Sprint, and this isn't an appropriate reason).

---

Dealing with Unfinished Work and Sprint Goal Failures

This category generates some of the most contested exam answers. Let's cut through the confusion.

Scenario Type 8: Unfinished Items at Sprint End

"Three Product Backlog items were not completed during the Sprint. What happens to them?"

Incomplete items are returned to the Product Backlog, where the Product Owner re-prioritizes them. They do NOT automatically carry over to the next Sprint. This is a critical point — automatic carryover violates the principle of Sprint Planning being a fresh commitment by the Developers. Exam distractors often suggest the team should "commit to finishing them in Sprint n+1" during the next Sprint Planning — which sounds responsible but bypasses the PO's right to reprioritize.

Scenario Type 9: The Sprint Goal Is at Risk Early

"By Day 5 of a two-week Sprint, the team realizes their initial estimates were significantly off. They will almost certainly fail to meet the Sprint Goal. What should the Scrum Master do?"

Don't cancel the Sprint (again, only the PO can do that, and only under specific conditions). The correct approach is transparency: the team raises this in the Daily Scrum, the Scrum Master facilitates a conversation, and the team collaborates with the Product Owner to renegotiate scope while protecting the Sprint Goal as much as possible. If the Sprint Goal itself becomes obsolete — not just difficult — cancellation becomes a legitimate conversation, but it's the PO's call.

---

Common Distractor Answers to Avoid in Situational Questions

Exam writers are skilled at crafting answers that feel right but violate core Scrum principles. Here are the most reliable patterns to watch for:

• "The Scrum Master should escalate to management immediately." Almost always wrong as a first response. Escalation may be appropriate eventually, but the Scrum Master coaches first.
• "The team votes and the majority decides." Scrum prefers consensus and self-management over majority-rules voting in most cases.
• "Add the urgent work to the Sprint Backlog with the PO's approval." The Sprint Backlog is owned by Developers. PO approval isn't sufficient — the Developers must agree, and the Sprint Goal must remain intact.
• "The Scrum Master should assign tasks to ensure balanced workload." Task assignment is never the Scrum Master's role. Ever.
• "Cancel the Sprint." This is almost never the right answer and can only be done by the Product Owner.
• "Schedule a separate meeting to address this." Scrum already has prescribed events. Adding ad-hoc meetings is often a sign of process inefficiency rather than a solution.

---

Summary: 5 Rules for Solving Any Scrum Master Exam Scenario

When you're sitting in the exam and time pressure kicks in, these five rules will anchor your thinking:

1. The Scrum Master never commands — they coach, facilitate, and remove impediments. If an answer has you making decisions that belong to the team or the PO, it's wrong.
2. Protect self-management relentlessly. Developers decide who does what and how. Any answer that takes that away is almost certainly incorrect.
3. Transparency first. When in doubt, the Scrum Master's job is to make problems visible — not to solve them unilaterally.
4. Events exist for reasons — protect them. The Daily Scrum is for Developers. Sprint Reviews are for stakeholder feedback. Sprint Retrospectives are for internal improvement. Don't let these collapse into each other.
5. Values are not decoration. When a question involves interpersonal difficulty, look for the answer that embodies Courage, Openness, or Respect — not the answer that avoids the conflict.

---

Key Takeaways

• Situational questions test Scrum judgment, not just Scrum knowledge — and they require a different preparation approach.
• The Scrum Master is a servant leader who protects self-management, enables transparency, and coaches — not a manager who controls outcomes.
• The Scrum Guide 2020's shift to "self-managing" teams is a meaningful signal: Developers own how they work, who does what, and what gets done within the Sprint.
• Sprint cancellation, task assignment, and immediate escalation to management are almost always wrong answers on the exam.
• Incomplete Sprint Backlog items return to the Product Backlog — they don't auto-roll over to the next Sprint.
• The Product Owner owns the Product Backlog; Developers own the Sprint Backlog. This boundary generates more exam questions than almost any other Scrum principle.

---

Conclusion

The best way to lock in everything covered here is to practice — not with flashcard-style questions, but with scenario-based Scrum Master questions that mirror the complexity of the actual PSM I and CSM exams. Reading about these principles is helpful, but putting yourself in the scenario, making a judgment call, and then seeing the reasoning explained is what builds genuine Scrum fluency.

As you practice, pay attention not just to whether you got the answer right, but to why each distractor was tempting. That's where the real learning happens. Every time you catch yourself almost choosing the "escalate to management" option or the "majority vote" option, you're identifying a gap in your Scrum intuition — and filling it.

The candidates who pass these exams aren't the ones who memorized the most. They're the ones who genuinely internalized why Scrum works the way it does — and that understanding shows up most clearly in how they handle the hard situational questions.

---

Frequently Asked Questions

Q: How many situational questions should I expect on the PSM I exam?

The PSM I exam contains 80 questions, and while Scrum.org doesn't publish a breakdown, most candidates report that 50–60% of questions are scenario-based or require applied judgment rather than simple recall. This is why understanding the reasoning behind the Scrum Guide matters more than memorizing it verbatim.

Q: Is the reasoning behind the CSM and PSM I situational questions the same?

Largely yes — both exams are grounded in the Scrum Guide 2020. The CSM exam (Scrum Alliance) requires completion of a two-day course and tends to test foundational application, while the PSM I (Scrum.org) is open-enrollment and generally considered more rigorous in how it probes edge cases and nuanced scenarios. The core Scrum principles driving correct answers are identical.

Q: What's the most common mistake candidates make on situational questions?

Choosing answers based on what they'd actually do in their current job — rather than what the Scrum Guide says to do. Many candidates come from management or project management backgrounds where assigning tasks, escalating conflicts, and controlling Sprint scope are normal behaviors. The exam requires you to put that instinct aside and think through the lens of servant leadership and Scrum values. Recognizing that gap is the first step to closing it.