PSPO I — Scrum.org Professional Scrum Product Owner I Study Plan
A practical study schedule for Scrum.org Professional Scrum Product Owner I (PSPO I), with 7-day, 14-day, 30-day, and 60/90-day preparation paths.
How to use this Study Plan
This plan is for candidates preparing for the Scrum.org Professional Scrum Product Owner I (PSPO I) exam from Scrum.org. It is designed to help you turn your available study time into a realistic preparation schedule.
The PSPO I exam rewards precise understanding of Scrum and Product Ownership. Your preparation should move quickly from reading definitions to applying them in scenario questions: who is accountable, what happens during Scrum events, how Product Backlog decisions are made, how value is maximized, and how stakeholders interact with the Scrum Team.
Use this page to choose a study path, set a daily rhythm, review missed questions, and decide when you are ready to sit for the real exam.
Which plan should you use?
| Time available | Best for | Main goal | Practice intensity |
|---|---|---|---|
| 7 days | You already know Scrum and need final review | Tighten definitions, remove weak spots, build exam speed | Daily timed sets and explanation review |
| 14 days | You have some Scrum exposure but need structure | Cover all core PSPO I areas and practice scenarios | Practice most days; 2 timed mocks |
| 30 days | You want balanced preparation | Build Scrum and Product Owner understanding before heavy practice | Regular topic review, then timed practice |
| 60/90 days | You are new to Scrum, Product Ownership, or professional product work | Learn deliberately, then shift into scenario judgment | Gradual build, weekly practice, final mock cycle |
If you are unsure, choose the shorter plan only if you can already explain Scrum accountabilities, events, artifacts, commitments, the Product Goal, the Product Backlog, and Product Owner accountability without notes.
What to prioritize for PSPO I
The exam is not a generic project-management test. Anchor your study to the Scrum framework and the Product Owner accountability.
| Study area | What you must be able to do |
|---|---|
| Scrum fundamentals | Explain empiricism, transparency, inspection, adaptation, self-management, and why Scrum events exist |
| Accountabilities | Distinguish Product Owner, Scrum Master, and Developers without assigning traditional project roles incorrectly |
| Product Owner accountability | Understand value maximization, Product Backlog ordering, Product Goal ownership, stakeholder engagement, and decision authority |
| Scrum events | Know the purpose of Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and the Sprint itself |
| Scrum artifacts and commitments | Connect Product Backlog to Product Goal, Sprint Backlog to Sprint Goal, and Increment to Definition of Done |
| Product Backlog management | Practice ordering, refinement, transparency, stakeholder input, and adapting based on learning |
| Value and product thinking | Reason about outcomes, benefits, risk, feedback, releases, and maximizing value over output volume |
| Agile versus predictive habits | Avoid answers that rely on command-and-control project management when Scrum requires empiricism and self-management |
| Scenario judgment | Choose the Scrum-consistent answer, not the answer that sounds administratively convenient |
Daily practice rhythm
Use the same basic rhythm regardless of your schedule. The difference is the number of questions and depth of review.
| Available time today | Study rhythm |
|---|---|
| 30 minutes | 10 minutes concept review, 15 minutes practice questions, 5 minutes missed-question notes |
| 60 minutes | 20 minutes targeted reading, 25 minutes practice, 15 minutes explanation review |
| 90 minutes | 25 minutes topic review, 35 minutes mixed practice, 20 minutes error log, 10 minutes flash review |
| 2+ hours | 40 minutes review, 45 minutes practice, 30 minutes missed-question analysis, 15 minutes retest weak area |
A strong PSPO I study session should produce one of these outputs:
- A cleaner understanding of a Scrum rule, accountability, event, artifact, or commitment.
- A written reason why a missed answer was wrong.
- A shorter list of weak areas.
- Better speed on scenario questions.
- A clearer distinction between Product Owner decisions, Scrum Master coaching, and Developers’ self-management.
7-day final review plan
Use this if your exam is in one week or less. Do not try to read every possible product-management source. Focus on Scrum precision, Product Owner accountability, and practice explanations.
| Day | Focus | Study actions | Output |
|---|---|---|---|
| 1 | Diagnostic | Take a timed mixed practice set. Review every miss and every guess. | Error log with top 3 weak areas |
| 2 | Scrum framework reset | Review accountabilities, events, artifacts, commitments, Definition of Done, Increment, Sprint Goal, Product Goal. | One-page Scrum map |
| 3 | Product Owner accountability | Review value maximization, Product Backlog ordering, stakeholder input, Product Goal, refinement, release decisions. | PO decision checklist |
| 4 | Scenario practice | Complete a timed set focused on Product Owner, stakeholder, backlog, and value scenarios. | Updated error log |
| 5 | Full timed mock | Take a full timed mock under exam-like conditions. Do not pause. | Score trend and weak-topic list |
| 6 | Explanation review | Rework missed and flagged questions. Review why wrong answers are attractive but incorrect. | Final correction notes |
| 7 | Light final review | Review Scrum Guide-level fundamentals, your error log, and key distinctions. Stop heavy new study. | Calm readiness check |
7-day rules
- Stop adding new study sources after Day 5 unless you discover a major Scrum framework gap.
- On Days 6 and 7, prioritize explanation review over new question volume.
- Do not memorize isolated wording without understanding the scenario logic.
- If you repeatedly miss questions about the same accountability or event, return to the Scrum framework before doing more practice.
14-day focused plan
Use this if you have two weeks and can study most days. The goal is to complete a fast content pass, then spend the second week on timed application.
| Day | Focus | Practice target |
|---|---|---|
| 1 | Baseline diagnostic and exam format check | Timed mixed set |
| 2 | Scrum theory: empiricism, values, self-management | Short concept quiz |
| 3 | Accountabilities: Product Owner, Scrum Master, Developers | Role/accountability scenarios |
| 4 | Events: purpose, participants, outcomes | Event sequence questions |
| 5 | Artifacts and commitments | Artifact/commitment questions |
| 6 | Product Backlog and refinement | Backlog ordering scenarios |
| 7 | Weekly review | Retake missed questions from Days 1-6 |
| 8 | Product value and stakeholder engagement | Value/stakeholder scenarios |
| 9 | Product Goal, Sprint Goal, Definition of Done | Goal and commitment scenarios |
| 10 | Agile versus predictive decision traps | Scenario judgment set |
| 11 | Timed mock 1 | Full timed practice |
| 12 | Mock review | Deep explanation review, no rushing |
| 13 | Timed mock 2 or large mixed set | Exam-like pacing |
| 14 | Final review | Error log, Scrum map, light recall |
14-day checkpoints
| Checkpoint | If true | Action |
|---|---|---|
| You miss mostly definition questions | Framework knowledge is not stable | Re-read core Scrum rules before more mocks |
| You miss mostly scenario questions | Concepts are known but judgment is weak | Review why each wrong option violates Scrum |
| You run out of time | Pacing needs work | Use shorter timed sets before another full mock |
| You change correct answers often | Confidence is unstable | Mark uncertain questions, but change only with a clear reason |
| You miss PO versus Scrum Master accountability | Role clarity is weak | Build a comparison chart and drill role scenarios |
30-day balanced plan
Use this if you want a structured month. This is the best path for many candidates because it gives enough time to understand Scrum before relying on practice questions.
| Week | Main objective | Study actions | End-of-week check |
|---|---|---|---|
| Week 1 | Build Scrum foundation | Study Scrum theory, accountabilities, events, artifacts, commitments. Create a one-page Scrum framework map. | Explain Scrum without notes |
| Week 2 | Build Product Owner understanding | Study Product Goal, Product Backlog, value, ordering, refinement, stakeholder collaboration, release thinking. | Explain how the PO maximizes value |
| Week 3 | Convert knowledge into scenario judgment | Practice mixed scenario sets. Review missed answers deeply. Separate Scrum answers from traditional project-management habits. | Weak areas are specific, not broad |
| Week 4 | Timed mock and final correction cycle | Take timed mocks, review explanations, retest weak areas, stop adding new material near the end. | Consistent readiness on timed practice |
30-day schedule by phase
| Days | Focus | What to do |
|---|---|---|
| 1-3 | Diagnostic and Scrum overview | Take a baseline set. Review Scrum theory, values, accountabilities, and core terms. |
| 4-7 | Events, artifacts, commitments | Drill each event’s purpose and connect artifacts to their commitments. |
| 8-11 | Product Owner accountability | Study value maximization, Product Goal, Product Backlog ordering, stakeholder engagement. |
| 12-15 | Product Backlog management | Practice refinement, transparency, ordering, risk, dependencies, and feedback scenarios. |
| 16-20 | Mixed scenario practice | Use timed sets. Review all misses. Track patterns. |
| 21-24 | Weak-area repair | Revisit only the topics your error log identifies. |
| 25 | Timed mock 1 | Simulate exam conditions. |
| 26-27 | Mock review | Explain each miss and guess. Retest weak topics. |
| 28 | Timed mock 2 or large mixed set | Confirm pacing and consistency. |
| 29 | Final review | Review notes, Scrum map, error log, and key distinctions. |
| 30 | Light study only | Stop heavy practice. Prepare logistics and rest. |
60/90-day full preparation path
Use this if you are new to Scrum, new to Product Ownership, or returning after a long gap. You do not need to study heavily for months, but you should use the extra time to build durable understanding before timed practice.
| Phase | 60-day path | 90-day path | Objective |
|---|---|---|---|
| Foundation | Days 1-14 | Days 1-21 | Learn Scrum theory, accountabilities, events, artifacts, commitments |
| Product Ownership | Days 15-28 | Days 22-42 | Study Product Goal, Product Backlog, value, stakeholders, ordering, refinement |
| Applied scenarios | Days 29-42 | Days 43-63 | Practice decision-making in PO scenarios |
| Timed practice | Days 43-52 | Days 64-78 | Build speed and exam endurance |
| Final correction | Days 53-60 | Days 79-90 | Review mocks, repair weak areas, stop adding new material |
Weekly rhythm for longer plans
| Day type | Activity |
|---|---|
| 2 days per week | Core reading and note-making |
| 2 days per week | Topic-specific practice |
| 1 day per week | Mixed practice set |
| 1 day per week | Missed-question review |
| 1 day per week | Rest or light flash review |
How to avoid overstudying on a longer path
- Keep notes short. One-page summaries are better than long copied notes.
- Start practice by the end of Week 2 or Week 3.
- Do not wait until the final week to see scenario questions.
- Revisit the Scrum framework repeatedly instead of collecting too many outside interpretations.
- Schedule the exam when your timed practice is consistent, not when you have read “one more” source.
Core PSPO I study sequence
Follow this order if you are building your own schedule.
| Sequence | Topic | Why it comes here |
|---|---|---|
| 1 | Scrum theory and values | Everything else depends on empiricism, transparency, inspection, adaptation, and self-management |
| 2 | Scrum accountabilities | Many questions test who is accountable for what |
| 3 | Events | Events create inspection and adaptation points |
| 4 | Artifacts and commitments | These define transparency and focus |
| 5 | Product Owner accountability | PSPO I depends heavily on value, backlog, and stakeholder judgment |
| 6 | Product Backlog and Product Goal | These are central to product direction and value decisions |
| 7 | Stakeholders, feedback, and value | Scenarios often test how the PO uses input without giving away accountability |
| 8 | Mixed scenario practice | This turns definitions into exam-ready judgment |
| 9 | Timed mocks | This confirms pacing and readiness |
| 10 | Final explanation review | This removes recurring traps before exam day |
Agile, predictive, and hybrid decision traps
PSPO I scenarios may include language that sounds like traditional project management, stakeholder control, phase-gate approval, task assignment, or fixed-scope delivery. Your job is to answer from the Scrum framework and Product Owner accountability.
| Scenario pattern | Common trap | Scrum-consistent thinking |
|---|---|---|
| A manager wants to assign tasks to Developers | Treat the manager as directing team execution | Developers self-manage their work |
| Stakeholders want to control Product Backlog order directly | Let stakeholder priority override the PO | Stakeholders provide input; the Product Owner is accountable for ordering |
| A project plan conflicts with learning from the Sprint Review | Preserve the original plan | Use empiricism; adapt based on inspection |
| The PO wants more work added during the Sprint | Treat the Sprint Backlog as a PO-controlled task list | Developers manage the Sprint Backlog; changes should not endanger the Sprint Goal |
| A Scrum Master makes product value decisions | Confuse facilitation with product accountability | Product value decisions belong to the Product Owner |
| The team completes work that does not meet the Definition of Done | Count it as mostly complete | Only work meeting the Definition of Done is part of the Increment |
| A hybrid organization demands reports and milestones | Abandon Scrum accountabilities | Work within organizational context while preserving Scrum rules |
Diagnostic practice: what to do first
Take a diagnostic set before you feel fully ready. The point is not to prove readiness; it is to identify your first study priorities.
After the diagnostic, classify every missed or guessed question.
| Miss type | What it means | Next action |
|---|---|---|
| Definition miss | You did not know a Scrum term or rule | Re-read the relevant framework section and make a flash note |
| Accountability miss | You confused PO, Scrum Master, or Developers | Create a role comparison note and drill similar questions |
| Event miss | You misunderstood purpose, timing, or outcome of an event | Review the event’s purpose and participants |
| Artifact/commitment miss | You confused Product Backlog, Sprint Backlog, Increment, Product Goal, Sprint Goal, or Definition of Done | Draw the artifact-to-commitment map |
| Product value miss | You chose output, utilization, or stakeholder pressure over value | Review Product Owner accountability and value maximization |
| Scenario trap | You knew the rule but chose a tempting answer | Write why the tempting option violates Scrum |
| Speed miss | You rushed or ran out of time | Use timed sets and practice flagging uncertain questions |
Missed-question review method
Do not only record the correct answer. Record why your thinking failed.
Use this structure:
| Field | What to write |
|---|---|
| Question topic | Example: Product Backlog ordering, Sprint Review, Definition of Done |
| My answer | The option you chose |
| Correct answer | The option supported by Scrum |
| Why I missed it | Knowledge gap, role confusion, overthinking, predictive-project habit, speed issue |
| Rule or principle | The Scrum rule or Product Owner principle involved |
| Trap answer | Why the wrong option looked attractive |
| Retest date | When you will retry a similar question |
Missed-question review steps
- Read the explanation before retaking the question.
- Identify the Scrum rule, not just the correct letter.
- Write one sentence beginning with: “The Scrum-consistent answer is…”
- Add the topic to your weak-area list.
- Retest that topic within 48 hours.
- If you miss the same topic again, stop mixed practice and review the source concept.
What to practice next
Use your error log to choose the next practice block.
| If your last practice set showed… | Practice next |
|---|---|
| Many misses on who decides what | Accountabilities and Product Owner authority |
| Many misses on Sprint Planning, Daily Scrum, Sprint Review, or Retrospective | Scrum events and their purposes |
| Many misses on Product Goal, Sprint Goal, or Definition of Done | Artifacts and commitments |
| Many misses on Product Backlog ordering | Value, risk, dependencies, stakeholder input, and PO accountability |
| Many misses on stakeholder scenarios | Stakeholder engagement without surrendering PO accountability |
| Many misses from traditional project thinking | Agile versus predictive trap review |
| Good accuracy but slow pace | Timed mixed sets |
| Strong topic sets but weak mixed sets | Full scenario practice and mock exams |
| Repeated mistakes after review | Return to core Scrum definitions before more questions |
When to use timed mock exams
Timed mocks are most useful after you have completed one full pass of the core topics. Taking too many full mocks too early can waste time because you will repeatedly miss questions for the same basic reasons.
| Plan | First timed mock | Second timed mock | Final mock use |
|---|---|---|---|
| 7-day plan | Day 1 or Day 2 diagnostic | Day 5 | Use Day 6 for review, not another heavy mock unless needed |
| 14-day plan | Day 11 | Day 13 | Review explanations on Day 14 |
| 30-day plan | Around Day 25 | Around Day 28 | Stop heavy mocks after final review begins |
| 60/90-day plan | After applied scenario phase | During timed practice phase | Final week only if review time remains |
Timed mock rules
- Match the current exam format shown by Scrum.org when you schedule or purchase the exam.
- Use exam-like conditions: no notes, no pausing, no interruptions.
- Mark uncertain questions and move on.
- Review both missed questions and correct guesses.
- Do not take back-to-back mocks without explanation review between them.
- Treat a mock as a diagnostic tool, not just a score.
Product Owner scenario checklist
For PSPO I scenario questions, ask these questions before choosing an answer.
| Question | Why it matters |
|---|---|
| Who is accountable here? | Many wrong answers shift accountability to the wrong role |
| What is being inspected? | Scrum uses events for inspection and adaptation |
| What creates transparency? | Artifacts, commitments, Definition of Done, and clear backlog ordering matter |
| Does the answer maximize value? | Product Owner decisions should support value, not just output |
| Does it preserve self-management? | Developers decide how to turn selected work into a Done Increment |
| Is stakeholder input being used correctly? | Stakeholders inform decisions but do not replace PO accountability |
| Is the answer empirical? | Scrum adapts based on evidence and learning |
| Is the answer adding unnecessary command-and-control process? | PSPO I often penalizes non-Scrum project-management assumptions |
Final-week rules
Use the final week to stabilize performance, not to collect new material.
Stop adding new material when:
- You are within 48 hours of the exam.
- Your misses are mostly from rushing, second-guessing, or misreading.
- You have already completed your core Scrum and Product Owner review.
- New sources are creating conflicting wording rather than clearer understanding.
Keep reviewing:
- Scrum accountabilities.
- Scrum events and their purpose.
- Artifacts and commitments.
- Product Owner accountability for value and Product Backlog ordering.
- Definition of Done and Increment.
- Product Goal and Sprint Goal.
- Stakeholder engagement and feedback.
- Your own missed-question log.
Exam-readiness checks
You are closer to ready when you can do the following without notes.
| Readiness check | Yes/No |
|---|---|
| I can explain the Product Owner accountability clearly. | |
| I can distinguish Product Owner, Scrum Master, and Developers in scenarios. | |
| I know the purpose of every Scrum event. | |
| I can connect each Scrum artifact to its commitment. | |
| I understand how Product Backlog ordering supports value. | |
| I can explain how stakeholder input is used without replacing PO accountability. | |
| I can identify predictive project-management traps in Scrum scenarios. | |
| I review explanations for missed and guessed questions. | |
| I can complete timed practice without rushing at the end. | |
| My weak areas are narrow and known, not broad and vague. |
Last 24 hours
Keep the final day simple.
| Do | Avoid |
|---|---|
| Review your error log | Starting a new long study source |
| Re-read your Scrum framework map | Taking multiple full mocks |
| Review Product Owner accountability | Memorizing without understanding |
| Do a short warm-up set if it calms you | Chasing obscure edge cases |
| Confirm exam logistics | Studying late into the night |
Practical next step
Choose the plan that matches your remaining time. Then take a diagnostic practice set, build an error log, and spend your next study session on the highest-frequency weakness it reveals. For PSPO I, the fastest improvement usually comes from tightening Scrum accountabilities, Product Owner decision-making, and scenario explanation review.