1.2 How to Study for PSPO I

1.2 How to Study for PSPO I

Quick Answer: Master the Scrum Guide 2020, drill the free Scrum Open and Product Owner Open until you hit 100% consistently, then reinforce traps (ordering vs prioritization, who cancels a Sprint, Daily Scrum ownership, pillars vs values, artifact commitments, and Sprint timeboxes). Sit the paid exam only when timed practice is stable above the 85% bar.

PSPO I rewards precision. Many questions are not “what would your company do?” but “what does the Scrum Guide say?” Candidates who rely only on workplace habits—or on outdated Scrum 2017 language—lose points on wording that looks minor until it appears as a True/False or multi-select item.

Primary Source: The Scrum Guide 2020

The Scrum Guide is short—roughly 13 pages in English—but every sentence can be tested. Treat it as the constitution of the exam.

How to read it for PSPO I

1. First pass (overview): Read end-to-end without notes. Capture the purpose of Scrum, the three accountabilities, five events, three artifacts, and the idea of empiricism.
2. Second pass (structure): Build a one-page map: pillars → values → team → events → artifacts → Done. Note every must, only, and accountable statement.
3. Third pass (Product Owner lens): Re-read with a highlighter only for Product Owner accountabilities: maximizing value, Product Backlog management, Product Goal, stakeholder collaboration, ordering, and Sprint cancellation authority.
4. Maintenance reads: Re-read the full Guide weekly until exam day. Short documents fade unless revisited.

Do not substitute blog posts, slide decks, or AI summaries for the Guide. Secondary materials (including this study guide) explain and drill; the Guide is the grading key.

Free Open Assessments: Your Fitness Test

Scrum.org provides two free practice assessments that map directly to PSPO I preparation:

Performance standard before you pay $200

• Aim for 100% on both Opens, repeatedly, not a single lucky 90%.
• Retake after rest days so you are not memorizing question order.
• When you miss an item, write the Guide rule in your own words, then find the exact sentence in the Guide.
• Only schedule the paid PSPO I when Open scores are boringly perfect and you can explain why each distractor is wrong.

The Opens are shorter and easier than the real assessment. Consistent 100%s are a minimum gate, not a guarantee. Still use additional practice questions (including this guide’s quizzes and any broader bank you trust) under a 45-seconds-per-question pace.

Common Traps (Memorize These)

These mistakes appear constantly on Product Owner assessments. Drill them until the correct phrasing is automatic.

1. Ordered vs prioritized Product Backlog

The Scrum Guide says the Product Backlog is an ordered list. “Prioritized” is informal language that can imply a simple high/medium/low scheme or that someone other than the Product Owner sets sequence. On the exam, prefer ordered—the Product Owner is accountable for ordering so the most valuable work is clear.

2. Who cancels the Sprint

Only the Product Owner has the authority to cancel the Sprint. Stakeholders, managers, Developers, or the Scrum Master may influence the decision, but cancellation authority is the Product Owner’s. Cancelling is rare and typically follows a Sprint Goal becoming obsolete; the completed Done items are still reviewed.

3. Daily Scrum is for the Developers

The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. The Product Owner and Scrum Master attend only if they are actively working on Sprint Backlog items as Developers—or if the Developers invite them. It is not a status meeting for the Product Owner to collect reports.

4. Transparency is a pillar, not a Scrum Value

Empirical pillars: Transparency, Inspection, Adaptation.
Scrum Values: Commitment, Focus, Openness, Respect, Courage.

“Transparency” and “Openness” sound similar; the exam will punish mixing pillars with values. Commit this table:

5. Artifact–commitment pairs

Every Scrum artifact has a commitment that enhances transparency and focus:

Mix-ups (for example, saying the Sprint Goal commits the Product Backlog) are easy multi-select traps.

6. Sprint timeboxes for a one-month Sprint

For a one-month Sprint, maximum timeboxes are:

For shorter Sprints, events are usually shorter. The Sprint itself is one month or less. If the Sprint Goal becomes obsolete, the Product Owner may cancel—not the Scrum Master alone.

Additional high-yield reminders

• There is one Product Owner per product; the role may be held by one person who may represent stakeholder desires, but accountable decisions rest with that person.
• Developers forecast work for the Sprint; the Product Owner does not push a fixed scope into the Sprint against their capacity.
• Definition of Done creates transparency about quality; the Product Owner cannot “accept” undone work as a Done Increment.
• Stakeholders collaborate through the Product Owner and at Sprint Review—they do not re-order the Product Backlog unilaterally mid-Sprint.

Phased Study Path and Hours

Adjust hours to your background. A candidate who already works as a Product Owner may finish faster; someone new to Scrum should budget more Guide and Open time.

Total for many candidates: about 20–40 hours. Spread study over 2–4 weeks rather than one weekend so wording sticks.

How to use this study guide with the Opens

• After each chapter, answer its quizzes before peeking at explanations.
• When a quiz exposes a Guide gap, re-read that Guide section immediately.
• Keep a running trap list (ordered vs prioritized, cancel authority, Daily Scrum ownership, pillars vs values, commitments, timeboxes).
• In the week before the exam, do timed practice only—no open-book browsing during the set.

Mindset for scenario questions

PSPO I often presents a workplace scenario and asks what the Product Owner should do under Scrum. Prefer the answer that:

1. Protects empiricism and a usable Done Increment,
2. Respects self-managing Developers,
3. Keeps ordering and value decisions with the Product Owner, and
4. Uses events and artifacts for collaboration instead of inventing new command-and-control meetings.

If two options both “sound agile,” choose the one aligned with Guide accountabilities, not corporate title politics.

Exam-Day Checklist

• Quiet room, charged device, stable connection, water, and a clock you can see
• No reliance on notes (integrity / Standard of Conduct)
• Flag hard multi-selects and return if time remains; do not leave blanks if the interface allows review
• After the result, save your competency breakdown for any retake plan

Summary of the Strategy

Read the Guide like law. Drill the Opens until perfect. Memorize the trap list. Practice under the 60-minute clock. Pay $200 only when evidence says you are ready. The chapters that follow turn each focus-area sub-topic into teaching you can quote on exam day—start with empiricism and the Scrum Team, then events, artifacts, self-management, and product agility.