PSPO I Quick Reference: Every Number You Need to Memorise

PSPO I Exam Overview: Know the Numbers

The Professional Scrum Product Owner (PSPO I) certification from Scrum.org tests your understanding of Scrum, the Product Owner role, and how to maximize product value. The exam consists of 80 multiple-choice questions to be answered in 60 minutes, with a passing score of 85%. That means you can only miss 12 questions. Every point counts, so memorizing the key numbers and concepts is crucial.

In this quick-reference cheat sheet, we distill the essential facts you need to memorize for the PSPO I exam. We'll cover the exam structure, domain weightings, Scrum framework fundamentals, and common traps to avoid. We recommend pairing this with What Is a Passing Score on PMP? The Number Nobody Publishes Clearly.

Exam Structure and Domain Weights

The PSPO I exam covers five domains, each with a specific percentage of questions. Knowing these weights helps you prioritize your study time. Here are the domains and their approximate weights (based on Scrum.org's public guidelines):

• Product Owner Responsibilities (30%): This is the largest domain. Focus on the Product Owner's accountabilities, stakeholder management, and value maximization.
• Scrum Framework (20%): Understand the Scrum pillars, values, events, and artifacts.
• Product Backlog Management (20%): Learn how to create, order, and refine the Product Backlog, and how to define 'Done'.
• Release Management (15%): Covers forecasting, release planning, and tracking progress toward goals.
• Business Strategy (15%): Includes product vision, value measurement, and evidence-based management.

While the exact percentages may vary slightly, the Product Owner Responsibilities domain is clearly the most heavily weighted. Spend extra time on that area.

A free Professional Scrum Product Owner I study plan gives you a week-by-week schedule that puts more time into the Product Owner Responsibilities domain and fits your available study hours.

Scrum Framework: Core Numbers to Remember

Scrum is defined by the Scrum Guide. You must know the key timeboxes and roles precisely. Here are the numbers you absolutely need to memorize:

Timeboxes

• Sprint: One month or less. The length is consistent throughout the development.
• Sprint Planning: A maximum of 8 hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
• Daily Scrum: 15 minutes. It is held at the same time and place each day.
• Sprint Review: A maximum of 4 hours for a one-month Sprint.
• Sprint Retrospective: A maximum of 3 hours for a one-month Sprint.

Roles

There are three accountabilities in Scrum: the Product Owner, the Scrum Master, and the Developers. The Product Owner is accountable for maximizing the value of the product and managing the Product Backlog. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. The Developers are accountable for creating a usable Increment each Sprint.

Note that the Scrum Guide uses the term 'accountability' rather than 'role' to emphasize that these are not just job titles but responsibilities. In the PSPO I exam, you'll be asked about the Product Owner's specific accountabilities, such as: This topic pairs well with PSPO I Difficulty: What Actually Makes People Fail.

• Developing and explicitly communicating the Product Goal.
• Creating and clearly communicating Product Backlog items.
• Ordering Product Backlog items.
• Ensuring that the Product Backlog is transparent, visible, and understood.

Product Backlog and Definition of Done

The Product Backlog is an emergent, ordered list of what is needed to improve the product. Key facts:

• The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
• Product Backlog items (PBIs) can be decomposed into smaller, more precise items. This is an ongoing process called refinement.
• Refinement typically consumes no more than 10% of the capacity of the Developers.
• The Definition of Done (DoD) is a formal description of the state of the Increment when it meets the quality measures required for the product. If there are multiple Scrum Teams working on the same product, they must mutually define and comply with the same DoD.

Release Management and Forecasting

Release management is about deciding when and what to release. Important concepts:

• Release planning is based on the Product Backlog and its progress, not on a fixed upfront plan.
• Forecasting is based on empirical data from past Sprints, such as velocity (the amount of Product Backlog items completed per Sprint).
• The Product Owner is responsible for deciding whether to release the Increment, but the Developers must first ensure it meets the Definition of Done.
• Value can be measured using various metrics, such as customer satisfaction, revenue, or usage. The Product Owner should choose metrics that reflect the product's goals.

Common Traps and How to Avoid Them

The PSPO I exam is known for its tricky questions. Here are common traps to watch out for:

1. Confusing the Product Owner with a Project Manager

The Product Owner is not a project manager. The Product Owner is accountable for the product's value, not for managing the team or the project timeline. Avoid answers that suggest the Product Owner directs the Developers or manages the budget (though the Product Owner may have budget authority in some contexts, the exam focuses on Scrum accountabilities).

2. Assuming the Product Owner Works Alone

The Product Owner is one person, not a committee. However, the Product Owner may delegate tasks to others, but the accountability remains with the Product Owner. The exam often tests whether you know that the Product Owner can delegate but not abdicate.

3. Mixing Up Sprint Review and Sprint Retrospective

The Sprint Review is for inspecting the Increment and adapting the Product Backlog. The Sprint Retrospective is for the Scrum Team to inspect itself and create a plan for improvements. Many questions ask which event is for what purpose. If you're preparing for this exam, 10 PSPO I Questions Most Candidates Get Wrong is essential reading.

4. Overemphasizing Tools and Processes

Scrum is a framework, not a methodology. Questions may try to lure you into thinking that a specific tool (like a burndown chart) is mandatory. In Scrum, the only artifacts are the Product Backlog, Sprint Backlog, and Increment. Tools are not prescribed.

5. Misunderstanding the Sprint Goal

The Sprint Goal is a commitment for the Sprint. It provides flexibility regarding the functionality implemented, but it is a clear, measurable objective. The Sprint Goal is created during Sprint Planning and is not changed during the Sprint.

Key Takeaways for Your PSPO I Prep

To pass the PSPO I exam, you need to internalize the Scrum Guide, not just memorize facts. Understand the 'why' behind each rule. Use the domain weights to allocate your study time, but also take practice exams to get familiar with the question style.

When you are ready to test yourself, a free Professional Scrum Product Owner I readiness check lets you answer a short set of practice questions and shows which topic area needs review.

Remember to review the Scrum Guide regularly, as it is the definitive source. The exam is based on the latest version of the Scrum Guide (as of 2020, with the updated terminology).

Finally, don't forget the numbers: 80 questions, 60 minutes, 85% passing score, one-month Sprint maximum, 8/4/3-hour timeboxes, 15-minute Daily Scrum, and 10% refinement capacity. These will help you quickly eliminate wrong answers.

Want to know if you are actually ready? full-length Professional Scrum Product Owner I (PSPO I) mock tests give you a straight answer.