PSM I — Scrum.org Professional Scrum Master I Study Plan
Practical 7-, 14-, 30-, and 60/90-day study plan for Scrum.org Professional Scrum Master I (PSM I), with daily practice, mock exams, and review.
How to use this PSM I Study Plan
This Study Plan is for candidates preparing for the real Scrum.org Professional Scrum Master I (PSM I) exam from Scrum.org. It is designed to turn your available study time into a practical schedule for learning Scrum, practicing scenario judgment, and reviewing missed questions.
The PSM I exam rewards precise understanding of Scrum. Your preparation should focus on:
- The Scrum Guide and the meaning of each rule, event, artifact, commitment, and accountability
- Empiricism, self-management, transparency, inspection, and adaptation
- How a Scrum Master serves the Scrum Team, Product Owner, Developers, and organization
- Scenario judgment when stakeholders, managers, deadlines, quality issues, or change requests create pressure
- Avoiding traditional project-management assumptions that conflict with Scrum
Use the current Scrum.org exam page and candidate instructions for official exam format, policies, and current requirements.
Which plan should you use?
| Time available | Best for | Main goal | Study style |
|---|---|---|---|
| 7 days | You have already read the Scrum Guide or worked with Scrum | Final review and exam readiness | Daily focused review, timed practice, missed-question repair |
| 14 days | You know agile basics but need structure | Build exam-level Scrum accuracy quickly | One topic per day plus scenario practice |
| 30 days | You are newer to Scrum or want a balanced pace | Learn, practice, and stabilize performance | Weekly cycles of study, practice, and mock review |
| 60 days | You are new to Scrum, busy, or rebuilding fundamentals | Full preparation with spaced repetition | Slow concept build, repeated review, timed mocks near the end |
| 90 days | You need a low-hour weekly schedule or extra language support | Same as 60 days, spread out | Add more teach-back, flashcards, and scenario discussion |
Start with a diagnostic
Before choosing your path, take a short timed diagnostic set or a representative practice session.
| Diagnostic result | What it means | Use this plan |
|---|---|---|
| You miss mostly wording details | You know Scrum but need precision | 7-day or 14-day plan |
| You miss event, artifact, or accountability questions | You need structured review | 14-day or 30-day plan |
| You answer from traditional PM habits | You need Scrum-first scenario training | 30-day or 60-day plan |
| You cannot explain why correct answers are correct | You need concept rebuilding | 30-day or 60/90-day plan |
| Timing causes careless errors | You need timed sets and pacing practice | Any plan, but add timed drills early |
PSM I knowledge map
Use this map to organize study sessions. Do not treat topics as isolated definitions. PSM I questions often test how the parts of Scrum work together.
| Area | What to master | Common traps |
|---|---|---|
| Scrum theory | Empiricism, lean thinking, transparency, inspection, adaptation | Treating Scrum as a task-tracking method only |
| Scrum values | Commitment, focus, openness, respect, courage | Picking an answer that is mechanically correct but undermines openness or self-management |
| Accountabilities | Scrum Master, Product Owner, Developers | Adding roles such as project manager, team lead, tester role, or proxy Product Owner |
| Scrum events | Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective | Confusing status reporting with inspection and adaptation |
| Scrum artifacts | Product Backlog, Sprint Backlog, Increment | Treating artifacts as static documents instead of transparent sources of inspection |
| Commitments | Product Goal, Sprint Goal, Definition of Done | Missing how commitments improve transparency and focus |
| Definition of Done | Quality, transparency, usable Increment | Accepting undone work as a normal outcome |
| Product Backlog management | Ordering, refinement, stakeholder input, Product Owner accountability | Turning ordering decisions into committee decisions |
| Sprint behavior | Forecasting, scope negotiation, Sprint Goal, Sprint cancellation | Assuming Sprint scope is frozen like a contract |
| Scrum Master service | Coaching, facilitation, impediment removal, organizational change | Making the Scrum Master the boss of the team |
| Stakeholders | Collaboration, Sprint Review, feedback, value | Allowing stakeholders to bypass the Product Owner or disrupt the Sprint |
| Metrics and forecasting | Transparency, evidence, empiricism | Using metrics to control individuals instead of improving decisions |
Daily practice rhythm
Use the same rhythm almost every study day. Short, consistent review is more useful than passive rereading.
60-minute day
| Minutes | Activity | Output |
|---|---|---|
| 0-10 | Review yesterday’s missed-question log | Pick 1-2 weak themes |
| 10-25 | Read or reread the relevant Scrum Guide section | Mark exact terms and responsibilities |
| 25-45 | Do targeted practice questions | Answer without notes |
| 45-55 | Review every missed or guessed answer | Write the rule and the reasoning |
| 55-60 | Active recall | Explain the topic out loud in plain language |
90-minute day
| Minutes | Activity | Output |
|---|---|---|
| 0-10 | Warm-up recall | List key rules from memory |
| 10-30 | Concept review | Focus on one Scrum area |
| 30-60 | Practice set | Mix direct and scenario questions |
| 60-80 | Missed-question review | Classify each miss |
| 80-90 | Teach-back | Explain the Scrum answer and why alternatives fail |
2-hour day
| Minutes | Activity | Output |
|---|---|---|
| 0-15 | Review log and flashcards | Revisit recurring weak points |
| 15-45 | Deep topic study | Guide, notes, examples |
| 45-85 | Timed practice | Simulate exam pressure |
| 85-110 | Review explanations | Repair reasoning, not just facts |
| 110-120 | Plan tomorrow | Choose the next weakest topic |
7-day final review plan
Use this plan if your exam is one week away. It assumes you have already read the Scrum Guide at least once. If you have not, make Day 1 a full Scrum Guide pass before doing practice.
| Day | Focus | Study actions |
|---|---|---|
| 1 | Baseline and Scrum Guide reset | Take a timed diagnostic set. Read the Scrum Guide carefully. Create a list of weak areas: accountabilities, events, artifacts, commitments, Scrum Master service, or scenario judgment. |
| 2 | Accountabilities and self-management | Review Scrum Master, Product Owner, and Developers. Practice questions about ownership, decision rights, collaboration, and who is accountable for what. |
| 3 | Events and inspection/adaptation | Review every Scrum event: purpose, participants, outputs, and inspection point. Practice event scenario questions, especially Daily Scrum, Sprint Review, and Retrospective. |
| 4 | Artifacts, commitments, and Done | Review Product Backlog/Product Goal, Sprint Backlog/Sprint Goal, Increment/Definition of Done. Practice quality, transparency, and unfinished work scenarios. |
| 5 | Scrum Master service and difficult scenarios | Practice stakeholder pressure, management intervention, team conflict, impediments, change during a Sprint, quality shortcuts, and organizational coaching. |
| 6 | Timed mock and deep review | Take a full timed mock or the closest available timed practice set. Spend at least as much time reviewing as you spent answering. Re-read Scrum Guide sections connected to misses. |
| 7 | Light final review | No new sources. Review your missed-question log, Scrum values, accountabilities, events, artifacts, and commitments. Do a short confidence set only if it calms you. Stop heavy study early. |
7-day rule
For the final week, prioritize correction over volume.
- Do not collect new study sources in the last 48 hours.
- Do not repeat practice questions until you only memorize answer positions.
- Do not ignore guessed-correct answers. Review them as if they were wrong.
- Keep a short list of “exam traps I still fall for.”
- Sleep and pacing matter more than another late-night question set.
14-day focused plan
Use this plan if you understand agile at a high level but need exam-ready Scrum precision.
| Day | Main focus | Practice target |
|---|---|---|
| 1 | Diagnostic and plan setup | Timed baseline, missed-question log, topic ranking |
| 2 | Scrum theory and values | Empiricism, transparency, inspection, adaptation, Scrum values |
| 3 | Scrum Team and accountabilities | Scrum Master, Product Owner, Developers, self-management |
| 4 | Sprint and Sprint Planning | Sprint Goal, forecast, collaboration, Product Backlog selection |
| 5 | Daily Scrum and Sprint execution | Inspection toward the Sprint Goal, Developer ownership, impediments |
| 6 | Sprint Review and Retrospective | Stakeholder feedback, product adaptation, process improvement |
| 7 | Artifacts and commitments | Product Backlog, Sprint Backlog, Increment, Product Goal, Sprint Goal, Definition of Done |
| 8 | Timed set and review day | Mixed timed practice, explanation review, weak-area repair |
| 9 | Product Owner and value | Ordering, stakeholder input, product decisions, Product Goal |
| 10 | Scrum Master service | Coaching, facilitation, impediments, organizational change |
| 11 | Quality and Done scenarios | Undone work, multiple teams, transparency, release decisions |
| 12 | Change, risk, and stakeholder pressure | Mid-Sprint change, deadlines, compliance, management requests |
| 13 | Full timed mock | Simulate exam conditions. Review all misses and guesses. |
| 14 | Final review | No new material. Review rules, traps, and explanations. Light practice only. |
14-day checkpoint
By the end of Day 8, you should be able to explain:
- Why Scrum has exactly the accountabilities it has
- How each event supports inspection and adaptation
- Why the Definition of Done is central to transparency
- How the Product Owner uses stakeholder input without becoming a committee
- How a Scrum Master acts without becoming a command-and-control manager
If you cannot explain these clearly, reduce practice volume and reread the Scrum Guide more actively.
30-day balanced plan
Use this plan if you want enough time to learn, practice, review, and stabilize before the exam.
Week 1: Build the Scrum foundation
| Day | Focus | Actions |
|---|---|---|
| 1 | Baseline | Take a diagnostic set. List weak topics. Set up a missed-question log. |
| 2 | Scrum theory | Study empiricism, lean thinking, Scrum values. Write short definitions from memory. |
| 3 | Scrum Team | Study accountabilities. Practice “who decides?” and “who is accountable?” questions. |
| 4 | Scrum Master | Review service to the Scrum Team, Product Owner, and organization. |
| 5 | Product Owner | Review value, ordering, Product Goal, stakeholder collaboration. |
| 6 | Developers | Review self-management, quality, Sprint Backlog, Daily Scrum. |
| 7 | Weekly review | Mixed practice set. Repair weak spots before moving on. |
Week 2: Master events, artifacts, and commitments
| Day | Focus | Actions |
|---|---|---|
| 8 | Sprint | Purpose, Sprint Goal, change, cancellation, usable Increment. |
| 9 | Sprint Planning | Inputs, collaboration, forecast, Sprint Goal, Sprint Backlog. |
| 10 | Daily Scrum | Developer inspection, adaptation, progress toward Sprint Goal. |
| 11 | Sprint Review | Product inspection, stakeholder feedback, Product Backlog adaptation. |
| 12 | Retrospective | Process improvement, quality, team adaptation. |
| 13 | Artifacts | Product Backlog, Sprint Backlog, Increment. |
| 14 | Commitments and Done | Product Goal, Sprint Goal, Definition of Done, transparency. |
Week 3: Convert knowledge into scenario judgment
| Day | Focus | Actions |
|---|---|---|
| 15 | Stakeholder pressure | Practice requests that bypass the Product Owner or disrupt the Sprint. |
| 16 | Management intervention | Practice command-and-control traps and Scrum Master coaching responses. |
| 17 | Change during a Sprint | Distinguish useful negotiation from abandoning the Sprint Goal. |
| 18 | Quality shortcuts | Practice Done, technical debt, incomplete work, and transparency. |
| 19 | Forecasting and progress | Review empirical planning and evidence-based discussion. |
| 20 | Mixed scenario set | Timed practice focused on judgment, not definitions. |
| 21 | Mock and retrospective | Take a longer timed mock. Analyze patterns. Update your final-week plan. |
Week 4: Timed performance and final review
| Day | Focus | Actions |
|---|---|---|
| 22 | Repair weakest domain | Reread guide sections and redo targeted questions. |
| 23 | Accountabilities refresh | Practice role boundaries and ownership decisions. |
| 24 | Events refresh | Practice purpose, participants, outputs, and anti-patterns. |
| 25 | Artifacts/commitments refresh | Practice transparency, Done, goals, and increments. |
| 26 | Full timed mock | Simulate exam conditions. Review thoroughly. |
| 27 | Explanation day | For every miss, write why the correct answer fits Scrum. |
| 28 | Final mixed practice | Short timed sets only. Avoid new sources. |
| 29 | Final mock or confidence set | Use only if it will produce useful review, not anxiety. |
| 30 | Light review | Review missed-question log, Scrum Guide highlights, and final checklist. |
60/90-day full preparation path
Use this path if you are new to Scrum, have limited weekly study time, or want a slower preparation cycle. A 60-day path works well with regular study blocks. A 90-day path spreads the same work out and adds more repetition.
| Phase | 60-day timing | 90-day timing | Goal |
|---|---|---|---|
| Orientation | Days 1-5 | Days 1-10 | Understand exam identity, read the Scrum Guide, take a light diagnostic |
| Scrum foundations | Days 6-15 | Days 11-25 | Learn empiricism, values, accountabilities, and basic Scrum structure |
| Events and artifacts | Days 16-30 | Days 26-45 | Master events, artifacts, commitments, and Definition of Done |
| Scenario judgment | Days 31-42 | Days 46-65 | Practice stakeholder, risk, quality, change, and organizational scenarios |
| Timed practice | Days 43-52 | Days 66-80 | Build pacing and reduce careless errors |
| Final review | Days 53-60 | Days 81-90 | Stop adding sources, review misses, confirm readiness |
60-day weekly schedule
| Week | Focus | Deliverable |
|---|---|---|
| 1 | Read the Scrum Guide and take a diagnostic | Topic gap list |
| 2 | Scrum theory, values, and accountabilities | One-page accountability map |
| 3 | Scrum events | Event purpose and outcome chart |
| 4 | Artifacts and commitments | Artifact/commitment comparison table |
| 5 | Scrum Master service | Scenario notes for coaching, facilitation, impediments |
| 6 | Stakeholders, change, quality, risk | Missed-question patterns and anti-pattern list |
| 7 | Timed mock practice | Mock review notes and weak-topic repair |
| 8 | Final review | Exam-readiness checklist and light practice |
90-day adjustment
If you use 90 days, do not simply stretch passive reading. Add spaced repetition:
- Review your missed-question log twice per week.
- Teach one Scrum topic out loud each week.
- Re-answer old missed questions after 7-10 days.
- Keep scenario notes: “What would Scrum make transparent here?”
- Begin timed sets by the final third of the plan, not only in the final week.
What to practice next
Use this table after each study session.
| If your misses are mostly… | Practice next | Review source |
|---|---|---|
| Accountabilities | “Who owns this?” questions | Scrum Team section and accountability notes |
| Events | Purpose, participants, inspection point, adaptation | Event-by-event chart |
| Artifacts | Transparency and what each artifact represents | Artifact and commitment comparison |
| Definition of Done | Quality, usable Increment, unfinished work | Definition of Done notes and scenarios |
| Product Owner decisions | Ordering, value, stakeholder input | Product Owner service and Product Goal |
| Scrum Master decisions | Coaching, facilitation, impediments | Scrum Master service scenarios |
| Stakeholder pressure | Product Backlog, Sprint Review, transparency | Scenario practice |
| Traditional PM instincts | Self-management and empiricism | Scrum vs predictive comparison |
| Careless reading | Slow timed sets | Question stem review habit |
| Timing pressure | Short timed drills | Pacing practice |
Scrum vs traditional project-management instincts
Many PSM I misses come from applying predictive or hybrid project-management habits to Scrum questions. For this exam, answer from Scrum as defined by Scrum.org and the Scrum Guide.
| Traditional instinct | Scrum exam lens |
|---|---|
| The project manager assigns tasks | Developers self-manage and decide how to do the work |
| The Scrum Master directs the team | The Scrum Master serves, coaches, facilitates, and helps remove impediments |
| Stakeholders change the team’s work directly | Stakeholder input is valuable, but Product Backlog ordering is the Product Owner’s accountability |
| Scope is locked for the Sprint like a contract | The Sprint Goal provides focus; scope may be clarified and negotiated without undermining the goal |
| Status meetings are for reporting to management | Scrum events exist for inspection, adaptation, transparency, and collaboration |
| Quality can be deferred to meet a deadline | The Definition of Done supports transparency and a usable Increment |
| More roles create more control | Scrum has defined accountabilities; adding control roles can reduce transparency and self-management |
| Metrics are used to judge individuals | Empirical evidence should support better decisions and improvement |
Missed-question review method
Do not only mark answers right or wrong. The main improvement comes from reviewing why you missed them.
The 5-step review
- Re-read the question stem slowly. Identify whether it asks for the best action, first action, accountability, purpose, or Scrum rule.
- Name the Scrum topic. Example: Sprint Goal, Definition of Done, Product Owner accountability, Scrum Master service.
- Write the rule in your own words. Keep it short and precise.
- Explain why the correct answer fits Scrum. Focus on transparency, inspection, adaptation, self-management, and accountability.
- Explain why your answer was tempting but wrong. This prevents the same trap from repeating.
Missed-question log
| Column | What to write |
|---|---|
| Date | When you missed it |
| Topic | Event, artifact, accountability, value, Done, stakeholder scenario, etc. |
| Miss type | Knowledge gap, wording trap, PM instinct, rushed reading, guessed |
| Correct Scrum principle | The rule or concept you should have used |
| Why I missed it | One sentence |
| Fix | Reread section, create flashcard, do 10 targeted questions, teach back |
| Recheck date | When you will test it again |
Miss types and fixes
| Miss type | Signal | Fix |
|---|---|---|
| Knowledge gap | You did not know the rule | Reread the relevant Scrum Guide section and write a short note |
| Role confusion | You assigned responsibility to the wrong accountability | Build a “who is accountable?” table |
| Event confusion | You mixed up purpose or outcome | Create an event chart and drill scenarios |
| Artifact confusion | You treated an artifact like a document only | Review transparency and commitments |
| Traditional PM bias | You chose command, approval, or phase-gate logic | Rewrite the answer using Scrum principles |
| Wording trap | You missed “best,” “first,” “most likely,” or “not” | Slow down and underline the question task |
| Memorization trap | You remembered an answer but not the reason | Explain the reasoning without looking |
| Timing error | You changed a correct answer or rushed | Practice smaller timed sets with review |
When to use timed mock exams
Timed mocks are useful only after you have enough foundation to learn from them. Taking many mocks too early can train guessing.
| Plan | First timed diagnostic | Main mock window | Final mock use |
|---|---|---|---|
| 7-day | Day 1 | Day 6 | Day 7 only as a light confidence set |
| 14-day | Day 1 | Days 8 and 13 | Avoid heavy mocks on Day 14 |
| 30-day | Day 1 | Days 21, 26, and 29 | Use Day 29 only if review time remains |
| 60-day | Week 1 light diagnostic | Weeks 7-8 | Final week: review over volume |
| 90-day | First 10 days light diagnostic | Final 3-4 weeks | Final week: light timed sets only |
How to review a mock
| Step | Action |
|---|---|
| 1 | Mark wrong answers and guessed-correct answers |
| 2 | Group misses by topic, not by question number |
| 3 | Identify your top 3 recurring traps |
| 4 | Reread only the relevant Scrum Guide sections |
| 5 | Re-answer similar targeted questions |
| 6 | Wait before retaking the same mock so you do not memorize it |
A good mock review session should take at least as long as the mock itself.
Final-week rules
Use the final week to stabilize, not to rebuild from scratch.
| Rule | Why it matters |
|---|---|
| Stop adding new sources 2-3 days before the exam | New wording can create confusion without enough time to integrate it |
| Review misses before new questions | Your own mistakes are the highest-value study material |
| Keep practice timed but not frantic | You need accuracy under pressure, not speed alone |
| Revisit Scrum values daily | Scenario answers often depend on openness, respect, courage, focus, and commitment |
| Do not ignore guessed-correct answers | A guess can hide a weak concept |
| Use the current Scrum.org instructions | Exam format and policies should be checked from the official provider |
Exam-readiness checks
You are ready when your reasoning is stable, not when you have merely completed a certain number of questions.
| Readiness area | Green signal | Yellow signal | Red signal |
|---|---|---|---|
| Scrum Guide knowledge | You can explain major sections without notes | You remember terms but hesitate on meaning | You rely mostly on memorized question answers |
| Accountabilities | You know who is accountable for what | You confuse Product Owner and Scrum Master decisions | You add roles or approval layers not in Scrum |
| Events | You know purpose and inspection point | You know names but confuse outcomes | You treat events as status meetings |
| Artifacts and commitments | You connect artifacts to transparency | You memorize definitions only | You cannot explain Definition of Done or goals |
| Scenario judgment | You choose Scrum-consistent actions | You often choose command-and-control options | You answer from traditional PM habits |
| Timed practice | You finish with enough time to review flagged items | Timing feels tight but manageable | You rush and miss wording |
| Review quality | You can explain every miss | You review only wrong answers | You skip explanations |
Final review checklist
Before exam day, confirm that you can explain each item clearly.
Scrum foundations
- Empiricism
- Transparency, inspection, adaptation
- Lean thinking
- Scrum values
- Why Scrum is a framework, not a complete methodology
Accountabilities
- Scrum Master
- Product Owner
- Developers
- Scrum Team as a whole
- Self-management
- Cross-functionality
Events
- Sprint
- Sprint Planning
- Daily Scrum
- Sprint Review
- Sprint Retrospective
- How each event supports inspection and adaptation
Artifacts and commitments
- Product Backlog and Product Goal
- Sprint Backlog and Sprint Goal
- Increment and Definition of Done
- Transparency of work and progress
- Usable Increment
Scenario themes
- Stakeholders want direct control of team work
- Management wants status, deadlines, or assignments
- Product Owner is unavailable or overruled
- Developers want to skip Done
- Sprint Goal is threatened
- Work is unfinished
- Impediments are blocking progress
- Multiple opinions exist about value or ordering
- The team is not collaborating or self-managing
Practical next step
Choose the plan that matches your time remaining. Then do three things today:
- Take a short diagnostic practice set.
- Create a missed-question log.
- Reread the Scrum Guide section connected to your largest gap.
After that, follow the daily rhythm: review, practice, explain, and repair. For PSM I, the goal is not just recognizing Scrum terms. The goal is choosing the Scrum-consistent response under exam pressure.