Overview¶

A focused, exam-oriented crash course for Scrum.org's Professional Scrum Master II (PSM II) certification — the intermediate-to-advanced tier that follows PSM I. PSM II tests applied judgment: given a scenario, what should the Scrum Master do, consistent with the Scrum Guide?

Who it's for: Practicing Scrum Masters who have already passed (or are very comfortable with) PSM I-level content and want a concentrated prep track for PSM II.

Core Topics Breakdown¶

1. The Scrum Guide, Cover to Cover¶

• PSM II questions are written to align tightly with the current Scrum Guide's exact language. Know the accountabilities (Product Owner, Scrum Master, Developers), the definition of each event's purpose and timebox, and the three artifacts plus their commitments (Product Goal, Sprint Goal, Definition of Done).
• Pay close attention to timebox maximums: Sprint Planning (8 hrs for a one-month Sprint), Daily Scrum (15 min), Sprint Review (4 hrs for a one-month Sprint), Retrospective (3 hrs for a one-month Sprint) — scaled proportionally for shorter Sprints.

2. The Scrum Master as a True Servant Leader¶

• PSM II heavily tests the Scrum Master's service to three groups: the Developers, the Product Owner, and the wider Organization. Expect scenario questions asking which of these the Scrum Master is serving in a given action.
• Recognize when a described action (e.g., "assigns tasks to team members") violates Scrum's self-management principle — a very common trap in exam questions.

3. Facilitation and Coaching Judgment¶

• Distinguishing facilitation (helping a group reach its own decision) from directing (telling the group the decision) — PSM II favors facilitation-oriented correct answers.
• Recognizing coaching opportunities embedded in scenario descriptions — e.g., a team asking the Scrum Master to solve a technical disagreement should usually be redirected to solve it themselves.

4. Common Scenario Themes¶

• A stakeholder demands a mid-sprint scope change — what does the Scrum Master do? (Protect the Sprint Goal; facilitate a conversation with the Product Owner about trade-offs, don't unilaterally block or allow it.)
• A team consistently fails to meet its Sprint Goal — what diagnostic questions should the Scrum Master ask first? (Backlog readiness, capacity assumptions, external interruptions.)
• Multiple teams sharing a Product Backlog experience conflicting priorities — what governance structure resolves this? (Points toward Nexus-style coordination.)

5. Test-Taking Strategy¶

• Eliminate answers that describe the Scrum Master taking unilateral authority over people or tasks — Scrum explicitly reserves this for the team's self-management.
• When two answers both sound plausible, prefer the one that facilitates a conversation over the one that makes a decision on someone else's behalf.
• Watch for absolute language ("always," "never") in answer options — these are often distractors unless they match the Scrum Guide's actual absolute statements (e.g., the Daily Scrum is always 15 minutes or less).

Study Tips¶

• Take multiple timed mock exams under real exam conditions (no notes, timed) to build stamina for the scenario-heavy question style.
• After each mock exam, don't just note which answers were wrong — write out why the correct answer aligns with a specific Scrum Guide principle.
• Form or join a study group to debate ambiguous scenario questions; talking through the reasoning surfaces gaps in understanding faster than solo review.

Common Pitfalls¶

• Studying secondary blog interpretations of Scrum instead of the actual Scrum Guide text — PSM II is written directly against the Guide.
• Choosing answers based on "what a good manager would do" instead of "what a servant-leader Scrum Master would do" — these frequently diverge.
• Rushing through scenario questions without identifying which of the three groups (Developers, PO, Organization) the question is really about.

Quick Reference Cheat Sheet¶

Further Practice¶

Write three original scenario questions (with four answer options each) testing the difference between facilitation and direction. Trade with a study partner if possible.