PSM II — Scrum.org Professional Scrum Master II Study Plan
A practical 7-, 14-, 30-, and 60/90-day study plan for the Scrum.org Professional Scrum Master II (PSM II) exam.
How to use this Study Plan
This Study Plan is for candidates preparing for the real Scrum.org Professional Scrum Master II (PSM II) exam. It assumes you are not just memorizing Scrum terms; you are preparing to answer scenario-based questions about how a Professional Scrum Master should act in complex team, product, stakeholder, and organizational situations.
Use the current Scrum.org exam page for the latest exam format, timing, rules, and policies. Use this plan to organize your study time, decide when to take timed practice, and turn missed questions into targeted review.
PSM II preparation should move through three levels:
| Level | What you must be able to do |
|---|---|
| Framework precision | Recall Scrum accountabilities, events, artifacts, commitments, and the purpose behind each one. |
| Scenario judgment | Choose actions that support empiricism, self-management, transparency, inspection, and adaptation. |
| Scrum Master maturity | Recognize when to teach, coach, facilitate, mentor, remove impediments, or help the organization change. |
Which plan should you use?
| Your situation | Use this plan | Main goal | Minimum daily time |
|---|---|---|---|
| Exam is in one week and you already know Scrum basics | 7-day final review | Identify weak spots, practice scenarios, avoid new-topic overload | 90-150 minutes |
| Exam is in two weeks and you need focused conditioning | 14-day focused plan | Convert Scrum knowledge into PSM II judgment | 60-120 minutes |
| You want a balanced schedule while working full time | 30-day balanced plan | Build stable understanding, then timed performance | 45-90 minutes |
| You are new to advanced Scrum Master scenarios or coming from project management, delivery, or hybrid governance roles | 60/90-day full path | Rebuild habits around Scrum accountabilities and empirical delivery | 30-75 minutes |
| Your practice results are inconsistent | Extend the plan | Review missed-question patterns before scheduling the exam | Varies |
If you have limited time, do not try to read every article, forum post, or book. For PSM II, the highest-value work is:
- Know the Scrum Guide precisely.
- Practice scenario questions under realistic timing.
- Review every missed, guessed, and “lucky” answer.
- Learn to explain why the best answer supports Scrum.
PSM II study targets
Use these targets to organize your review. They are not official domain weights; they are practical study areas for the Scrum.org PSM II exam.
| Study target | What mastery looks like | Practice action |
|---|---|---|
| Scrum theory and empiricism | You can explain why transparency, inspection, and adaptation matter in a scenario. | For each question, identify what is unclear, what should be inspected, and what adaptation is appropriate. |
| Scrum accountabilities | You do not confuse Scrum Master, Product Owner, Developers, stakeholders, managers, or customers. | Create an accountability map and review it after missed role-based questions. |
| Events | You know the purpose of each Scrum event and avoid turning events into status meetings or approval gates. | For event questions, write the event purpose before reviewing answer choices. |
| Artifacts and commitments | You understand Product Goal, Sprint Goal, Definition of Done, Product Backlog, Sprint Backlog, and Increment. | Drill questions about goals, transparency, quality, and unfinished work. |
| Scrum Master service | You choose coaching, facilitation, teaching, mentoring, and impediment removal over command-and-control. | After each scenario, ask: “Is the Scrum Master enabling Scrum or making decisions for others?” |
| Self-management | You protect Developers’ accountability for planning and managing their own work. | Flag answers where someone assigns tasks, controls estimates, or bypasses the Developers. |
| Product and value | You understand how Scrum supports value, benefits, feedback, and product decisions without making the Scrum Master the product manager. | Practice stakeholder, Product Owner, ordering, and Sprint Review scenarios. |
| Risk and uncertainty | You see risk as something exposed and managed through empiricism, Done Increments, and frequent inspection. | Rewrite risk-heavy scenarios in terms of transparency, inspection, adaptation, and quality. |
| Organizational impediments | You recognize when the Scrum Master should help the organization change rather than work around broken systems. | Practice manager, governance, reporting, dependency, and impediment questions. |
| Agile, predictive, and hybrid habits | You can separate Scrum from traditional project management assumptions. | Identify where a scenario tempts you to use status reporting, phase gates, approvals, resource assignment, or scope control as the main solution. |
Daily practice rhythm
Use one of these routines depending on your available time. The review step matters more than the number of questions completed.
| Time available | Session rhythm |
|---|---|
| 45 minutes | 10 min concept review, 20 min scenario practice, 15 min missed-question review |
| 60 minutes | 15 min Scrum Guide or topic review, 30 min practice, 15 min error log |
| 90 minutes | 20 min targeted review, 45 min mixed questions, 25 min explanation review |
| 2-3 hours | 30 min topic review, 60-90 min timed practice, 45-60 min deep review |
A strong daily PSM II session should follow this sequence:
- Pick one target. Example: Scrum Master stance, Product Owner collaboration, Sprint Goal, Definition of Done, stakeholder feedback, or organizational impediments.
- Answer closed book. Do not check notes while answering scenario questions.
- Review all missed and guessed items. A guessed correct answer still belongs in your error log.
- Explain the Scrum reason. Write why the best answer supports Scrum, not just why it “sounds right.”
- Extract one rule. End each session with one sentence you can apply later.
- Retest later. Revisit the same topic after at least one sleep cycle.
Scenario answer checklist
Before choosing an answer on PSM II scenario practice, ask:
| Question | Why it matters |
|---|---|
| Who is accountable here? | Many wrong answers give the Scrum Master, manager, or stakeholder someone else’s accountability. |
| What is not transparent? | Scrum solutions often begin by making work, goals, quality, risk, or progress visible. |
| What should be inspected? | Look for the right event, artifact, or conversation that enables inspection. |
| What adaptation is needed? | The best answer usually enables the Scrum Team to adapt, not simply comply. |
| Does this protect self-management? | Avoid answers that assign work, dictate estimates, or make the Scrum Master a task manager. |
| Does this improve Done, value, or feedback? | Quality, value, and usable Increments are frequent clues. |
| Is this a short-term workaround or a Scrum-consistent improvement? | PSM II often rewards fixing the system over hiding the problem. |
| Is more than one answer true? | Choose the best next action, not merely a statement that is technically correct. |
Missed-question review method
Do not only mark questions right or wrong. Build a review log that explains the pattern behind each miss.
| Log field | What to write |
|---|---|
| Topic | Example: Sprint Goal, stakeholder management, Done, Product Owner, Scrum Master stance |
| Scenario clue | The phrase that should have changed your answer |
| Your mistaken assumption | Example: “Scrum Master should assign a fix,” “Manager should decide,” “Sprint scope is fixed” |
| Scrum principle | The rule, purpose, or accountability involved |
| Better action | What a Professional Scrum Master should do instead |
| Retest date | When you will revisit the topic |
Missed-answer decision table
| If you missed because… | Your likely issue | What to do next |
|---|---|---|
| You forgot a Scrum rule | Framework precision gap | Reread the relevant Scrum Guide section and answer 10 targeted questions. |
| You confused accountabilities | Role/accountability gap | Build a table for Product Owner, Scrum Master, Developers, and stakeholders. |
| You picked the most forceful answer | Command-and-control habit | Review coaching, facilitation, self-management, and servant leadership scenarios. |
| You picked the most passive answer | Misunderstood Scrum Master service | Practice impediment removal and organizational change scenarios. |
| You treated Sprint planning as fixed scope control | Predictive project habit | Review Sprint Goal, Sprint Backlog adaptation, and empirical planning. |
| You ignored quality or Done | Delivery professionalism gap | Drill Definition of Done, Increment, technical quality, and undone work scenarios. |
| You treated Sprint Review as sign-off | Stakeholder feedback gap | Review Sprint Review purpose, product feedback, and Product Backlog adaptation. |
| You chose based on workplace custom | Experience bias | Re-answer using only Scrum accountabilities and principles, not your company process. |
| You changed a correct answer late | Confidence/timing issue | Practice timed sets and write answer-change rules. |
What to practice next
Use your error log to choose the next study block. Do not move randomly from topic to topic.
| Current evidence | Next practice block |
|---|---|
| You miss basic framework questions | Scrum Guide precision before more mock exams |
| You know the rule but miss the scenario | Mixed scenario sets with written explanations |
| You miss Product Owner or value questions | Product Goal, Product Backlog, stakeholder feedback, value evidence |
| You miss team behavior questions | Self-management, Developers’ accountability, coaching, facilitation |
| You miss quality questions | Definition of Done, Increment, undone work, technical excellence |
| You miss organizational questions | Impediments, management support, transparency, organizational change |
| You miss hybrid-governance scenarios | Separate Scrum accountabilities from reporting, funding, and governance constraints |
| You run out of time | Short timed sets, then exam-length timed practice |
| Your score swings widely | Stop taking mocks; review error patterns for two sessions |
When to use timed mock exams
Timed mocks are useful only when you review them deeply. Taking many mocks without review trains speed, not judgment.
| Timing | Use a timed mock for… | What to do afterward |
|---|---|---|
| Start of plan | Diagnostic baseline | Identify top 3 weaknesses; do not worry about score yet. |
| After framework review | Check whether you can apply concepts under pressure | Review all missed and guessed questions. |
| Midpoint of 30-, 60-, or 90-day plan | Measure progress and adjust topics | Rebuild the next week around weak patterns. |
| 7-10 days before exam | Readiness check | Decide whether final week is review or reschedule/extend. |
| 2-4 days before exam | Final timing and confidence check | Review explanations; stop adding major new material. |
Timed mock rules:
- Match the current Scrum.org exam format as closely as your practice source allows.
- Take the mock in one sitting.
- Do not pause, research, or check notes.
- Review the same day if possible.
- Log guessed correct answers.
- Do not retake the same mock repeatedly until you have memorized it.
- Stop full mocks if you are not reviewing explanations carefully.
7-day final review plan
Use this if your PSM II exam is in one week. This is a review plan, not a full learning path. Focus on Scrum judgment, not collecting new resources.
| Day | Focus | Actions | Done when… |
|---|---|---|---|
| 1 | Diagnostic and plan | Take a mixed timed practice set. Build your error log. Review the current exam rules on Scrum.org. | You know your top 3 weak areas. |
| 2 | Scrum framework precision | Review accountabilities, events, artifacts, commitments, Sprint Goal, Product Goal, and Definition of Done. | You can explain each element’s purpose without notes. |
| 3 | Scrum Master stance | Practice scenarios on coaching, facilitation, teaching, mentoring, impediment removal, and self-management. | You stop choosing answers where the Scrum Master controls the team. |
| 4 | Product, value, and stakeholders | Drill Product Owner collaboration, Product Backlog ordering, Sprint Review, stakeholder feedback, and value evidence. | You can distinguish feedback from approval/sign-off. |
| 5 | Quality, risk, and organizational impediments | Review Done, usable Increments, technical quality, transparency, management issues, dependencies, and systemic impediments. | You can explain how Scrum exposes and reduces risk. |
| 6 | Timed mock and explanation review | Take one exam-style timed mock. Spend at least as much time reviewing as answering. | Your remaining misses are narrow and explainable. |
| 7 | Light final review | Review your error log, Scrum Guide notes, and scenario checklist. Stop heavy practice early. | You feel clear, rested, and are not adding new topics. |
If you are behind with 7 days left
Prioritize in this order:
- Scrum Guide precision.
- Scrum Master stance scenarios.
- Missed-question review.
- One timed mock.
- Final explanation review.
Avoid:
- Reading large amounts of new material in the last 48 hours.
- Taking multiple full mocks without review.
- Memorizing answer patterns from repeated tests.
- Replacing Scrum principles with workplace habits.
14-day focused plan
Use this if you have two weeks and can study most days. The goal is to convert basic Scrum knowledge into PSM II-level judgment.
| Day | Focus | Main work |
|---|---|---|
| 1 | Diagnostic | Take a mixed practice set and create your error log. |
| 2 | Scrum Guide precision | Review Scrum theory, accountabilities, events, artifacts, and commitments. |
| 3 | Framework application | Practice questions that require choosing the right event, artifact, or accountability. |
| 4 | Scrum Master service | Drill coaching, facilitation, teaching, mentoring, servant leadership, and impediment removal. |
| 5 | Self-management and team effectiveness | Practice Developers’ accountability, collaboration, estimation, planning, and conflict scenarios. |
| 6 | Product Owner support | Review Product Goal, Product Backlog, ordering, value, stakeholder input, and Sprint Review. |
| 7 | Timed mixed set | Take a timed set and review every explanation. Re-rank weak topics. |
| 8 | Definition of Done and quality | Drill usable Increments, Done, undone work, transparency, and delivery professionalism. |
| 9 | Risk, change, and uncertainty | Practice empirical planning, changing conditions, Sprint Goal, adaptation, and risk visibility. |
| 10 | Organization and managers | Review organizational impediments, management expectations, reporting, dependencies, and change. |
| 11 | Predictive/hybrid traps | Compare Scrum responses with traditional project control responses. Practice scenario judgment. |
| 12 | Full timed mock | Take an exam-style timed mock. Do not study during the mock. |
| 13 | Deep explanation review | Rework missed and guessed questions. Write final rules for recurring traps. |
| 14 | Final light review | Review error log, Scrum Guide notes, and scenario checklist. Stop adding new material. |
14-day weekly rhythm
| Week | Goal | Practice mix |
|---|---|---|
| Week 1 | Build accurate Scrum reasoning | 60% topic review, 40% targeted practice |
| Week 2 | Perform under exam conditions | 30% review, 50% scenario practice, 20% timed mocks |
30-day balanced plan
Use this if you want a realistic preparation plan while working full time. The 30-day path gives enough time to review, practice, correct patterns, and build timing confidence.
30-day overview
| Days | Focus | Outcomes |
|---|---|---|
| 1-3 | Baseline and exam map | Diagnostic complete; error log started; study targets selected |
| 4-7 | Scrum Guide precision | Accountabilities, events, artifacts, commitments, and empiricism are clear |
| 8-12 | Scrum Master stance | Coaching, facilitation, teaching, mentoring, impediment removal practiced |
| 13-16 | Team, quality, and Done | Self-management, Definition of Done, Increment, and delivery quality reviewed |
| 17-20 | Product, value, and stakeholders | Product Owner support, stakeholder feedback, Sprint Review, and value scenarios practiced |
| 21-23 | Organization, risk, and change | Governance, managers, dependencies, systemic impediments, and transparency reviewed |
| 24 | Timed mock | First serious readiness check |
| 25-27 | Weak-area repair | Rebuild study around error log patterns |
| 28 | Final timed mock | Confirm timing and decision quality |
| 29 | Explanation review | Review misses, guessed answers, and final rules |
| 30 | Light review or exam day | No major new material |
30-day weekly schedule
| Week | Monday-Friday | Weekend |
|---|---|---|
| Week 1 | Read and map Scrum Guide concepts; short targeted question sets | Diagnostic review and accountabilities drill |
| Week 2 | Scrum Master stance and team scenarios | Mixed timed set plus deep review |
| Week 3 | Product, value, stakeholders, quality, risk, and organization | Scenario workshop: rewrite missed questions into Scrum principles |
| Week 4 | Timed mocks, weak-area repair, final explanation review | Light final review and exam readiness check |
30-day practice allocation
| Activity | Approximate share |
|---|---|
| Scrum Guide and concept review | 25% |
| Targeted scenario practice | 35% |
| Mixed timed practice | 20% |
| Missed-question review | 20% |
If your missed-question review takes longer than planned, reduce new questions. For PSM II, explanation quality is more valuable than question volume.
60/90-day full preparation path
Use this if you are starting early, returning to Scrum after a break, or coming from project management, delivery management, governance, or hybrid environments where Scrum accountabilities may have been blended with traditional roles.
60/90-day phase plan
| Phase | 60-day timing | 90-day timing | Focus | Deliverables |
|---|---|---|---|---|
| 1. Orientation | Days 1-5 | Days 1-7 | Exam identity, current Scrum.org rules, diagnostic, study setup | Error log, topic map, weekly calendar |
| 2. Framework mastery | Days 6-15 | Days 8-24 | Scrum Guide precision, empiricism, accountabilities, events, artifacts, commitments | Framework notes and targeted practice |
| 3. Scrum Master service | Days 16-28 | Days 25-42 | Coaching, facilitation, teaching, mentoring, impediment removal, self-management | Scenario explanations by Scrum Master stance |
| 4. Product and delivery | Days 29-38 | Days 43-60 | Product Goal, value, stakeholders, Sprint Review, Done, Increment, quality | Product/value and Done practice sets |
| 5. Organization and complexity | Days 39-48 | Days 61-72 | Managers, governance, dependencies, risk, change, organizational impediments | Organizational scenario log |
| 6. Timed integration | Days 49-55 | Days 73-83 | Mixed timed sets and exam-style mocks | Timing data and weak-area repair plan |
| 7. Final review | Days 56-60 | Days 84-90 | Final mock, explanation review, light review | Readiness decision |
Weekly cadence for long plans
| Day type | Work |
|---|---|
| Concept day | Review one topic and write a short summary from memory. |
| Targeted practice day | Answer questions only from that topic. |
| Mixed practice day | Use mixed scenarios to prevent topic cueing. |
| Review day | Rework missed and guessed questions; update error log. |
| Timed day | Take a timed set or mock when scheduled. |
| Light day | Read notes, review Scrum Guide excerpts, or rest. |
A sustainable weekly pattern:
| Day | Example activity |
|---|---|
| Day 1 | Scrum Guide or topic review |
| Day 2 | Targeted practice |
| Day 3 | Scenario explanation writing |
| Day 4 | Mixed practice |
| Day 5 | Weak-area repair |
| Day 6 | Longer timed set or mock, if scheduled |
| Day 7 | Light review or rest |
Agile, predictive, and hybrid habit reset
Many PSM II candidates understand Scrum vocabulary but still answer from a project manager or delivery manager mindset. Use this table to reset your instincts.
| Scenario temptation | Predictive or hybrid habit | Scrum-consistent response |
|---|---|---|
| Manager wants the Scrum Master to assign tasks | Centralized work control | Developers manage their own work; Scrum Master coaches and helps remove impediments. |
| Stakeholder wants Sprint Review to approve completed work | Sign-off gate | Sprint Review is for inspection, feedback, and adaptation of the Product Backlog. |
| Scope changes during the Sprint | Change-control reflex | Protect the Sprint Goal; Developers adapt the Sprint Backlog as they learn. |
| Team has quality problems | Add inspection at the end | Improve Definition of Done, transparency, engineering practices, and Done Increments. |
| Leadership wants progress certainty | Status reporting habit | Increase transparency with real evidence, usable Increments, goals, and inspection. |
| Product Owner is unavailable | Scrum Master becomes proxy PO | Scrum Master helps address the impediment; Product Owner accountability remains with the Product Owner. |
| Multiple teams have dependencies | Add a coordinator who directs teams | Make dependencies transparent and help teams improve collaboration and self-management. |
| Risk is high | Create a plan that hides uncertainty | Use empiricism, short feedback loops, Done work, and adaptation to expose and manage risk. |
Final-week rules
During the final week, your job is to stabilize judgment.
| Rule | Why |
|---|---|
| Stop adding major new resources 48 hours before the exam. | New material can create confusion without enough practice time. |
| Review explanations more than scores. | PSM II rewards reasoning, not recognition of repeated answers. |
| Do not take a full mock the night before if you cannot review it. | Unreviewed mocks create anxiety and little learning. |
| Keep the Scrum Guide close. | Most scenario judgment still depends on precise Scrum understanding. |
| Sleep and timing matter. | Fatigue increases second-guessing and role-confusion errors. |
| Review guessed correct answers. | Lucky answers hide weak reasoning. |
| Use your own error log. | Your mistakes are more useful than generic topic lists. |
Exam-readiness checks
You are likely ready to sit for the Scrum.org Professional Scrum Master II (PSM II) exam when most of these are true:
| Readiness check | Yes/No |
|---|---|
| You can explain Scrum accountabilities without turning the Scrum Master into a project manager. | |
| You can identify the purpose of each Scrum event in a scenario. | |
| You can explain how Product Goal, Sprint Goal, Definition of Done, and Increment affect decisions. | |
| You consistently review missed and guessed questions before taking more practice. | |
| Your recent mixed timed practice is stable, not swinging widely. | |
| You finish timed practice with enough time to review uncertain items. | |
| You can choose the best answer when several answers seem partly correct. | |
| You can separate Scrum principles from your workplace’s custom process. | |
| Your remaining weak areas are narrow and known. | |
| You are no longer adding major new study resources. |
If you track practice percentages, compare your results with the current score requirement and exam details published by Scrum.org. Build a safety margin in practice rather than aiming to barely clear the line.
Practical next step
Choose the plan that matches your exam date, take a mixed diagnostic practice set, and start an error log today. For every missed or guessed question, write the Scrum principle behind the correct answer. Then use your error patterns to decide tomorrow’s practice topic.