Short answer: PSPO I proves you know what the Scrum Guide says about the Product Owner; PSPO II proves you can make a Product Owner's decisions when the Guide gives no direct answer. PSPO I is 80 questions in 60 minutes for $200; PSPO II is 40 questions in 60 minutes for $250. Both need 85% to pass, both are taken online, and neither requires a course or expires. Move up to PSPO II when you have real Product Owner experience to draw on - Scrum.org's own PSPO-Advanced class page asks for at least a year of it. All facts below were checked at scrum.org on 3 October 2026.
PSPO I vs PSPO II at a glance
| PSPO I | PSPO II | |
|---|---|---|
| Publisher | Scrum.org | Scrum.org |
| Questions | 80 | 40 |
| Time | 60 minutes (45 seconds per question) | 60 minutes (90 seconds per question) |
| Question types | Multiple choice, multiple answer, true/false | Multiple choice, multiple answer; partial credit on some |
| Pass mark | 85% | 85% |
| Fee | $200 per attempt | $250 per attempt |
| Course required | No | No - PSPO-Advanced recommended |
| Prerequisite | None | None formally; PSPO I recommended |
| Languages | English, Japanese, Simplified Chinese | English |
| Renewal | None - lifetime | None - lifetime |
| Source | scrum.org PSPO I | scrum.org PSPO II |
Our PSPO I exam format page and PSPO II exam format page mirror these numbers, and the timed mode of our simulator uses the same question counts and time limits.
The table hides the one number that matters most: time per question doubles. PSPO I is a speed-and-precision test - 80 questions in an hour leaves no room for deliberation. PSPO II halves the count and keeps the hour, because each question takes longer to read and longer to decide. If you passed PSPO I by recognising the Guide's wording quickly, that skill alone will not carry you through PSPO II.
What PSPO I tests
Scrum.org lists three focus areas for PSPO I: Understanding and Applying the Scrum Framework (empiricism, the Scrum Team, events, artifacts, Done), Developing People and Teams (self-managing teams), and Managing Products with Agility (forecasting and release planning, product vision, product value, Product Backlog management, business strategy, stakeholders and customers). The source material is the Scrum Guide, read from the Product Owner's side.
A typical PSPO I question has one right answer that you can point to in the Guide: who is accountable for ordering the Product Backlog, whether the Product Owner can be a committee, what happens to the Sprint Goal when scope changes. The traps are workplace habits the Guide does not support - a Product Owner who assigns tasks to Developers, a "Sprint 0", a backlog that only the Product Owner may touch.
Our PSPO I practice bank has 282 questions in four areas, with the largest share in Maximizing Value and Product Backlog Management.
What PSPO II tests
Scrum.org describes PSPO II as advanced Product Ownership: product vision, Product Backlog management, release and portfolio planning, business strategy and working with stakeholders. Its questions come from three focus areas - Understanding and Applying the Scrum Framework, Managing Products with Agility, and Evolving the Agile Organization - with the greatest emphasis on Managing Products with Agility. Scrum.org publishes no numeric weights for any of them.
The other source you need is the Evidence-Based Management guide. Its four Key Value Areas - Current Value, Unrealized Value, Time to Market and Ability to Innovate - are how a Product Owner argues about value with evidence instead of opinion, and PSPO II scenarios lean on that vocabulary.
A typical PSPO II question describes a product in trouble: a stakeholder who wants a fixed release date for a fixed scope, a portfolio of three products competing for one team, a product with rising revenue and collapsing customer satisfaction. Four or five responses all sound like something a sensible manager might do. The right one is the response most consistent with a single accountable Product Owner maximising value through empiricism - usually the one that makes the trade-off transparent and decides on evidence, rather than the one that promises everyone what they asked for.
Our PSPO II practice bank has 106 questions grouped into seven topics taken from Scrum.org's own description - for example Evidence-Based Management and Forecasting and Release Strategy. The topic split is our grouping, not an official weighting, and the exam format page labels it as an estimate.
Cost: self-study vs the official classes
| Route | PSPO I | PSPO II |
|---|---|---|
| Self-study, pass first time | $200 | $250 |
| Self-study, one retake | $400 | $500 |
| Official class | Free attempt included | Free attempt included |
| Second attempt via class | Free if taken within 14 days and score below 85% | Free if taken within 14 days and score below 85% |
Both official classes - Professional Scrum Product Owner and PSPO-Advanced - include a password for the matching assessment. If you sit it within 14 days of receiving the password and score below 85%, Scrum.org grants a second attempt at no extra cost. Course fees are set by each trainer, so there is no single price to compare against; we do not quote one.
On the self-study route, both levels together cost $450 if you pass first time. Passwords do not expire, so there is no reason to buy before you are ready, and Scrum.org certifications do not require renewal.
When to move up from PSPO I to PSPO II
Three signals say you are ready:
- You make product decisions, not just backlog edits. If someone else sets the product goal and you translate it into items, PSPO II scenarios will feel abstract. Scrum.org's PSPO-Advanced class asks for at least one year of Product Owner experience, and the assessment is written for that audience.
- You can explain value without output metrics. If your instinct is to defend a product with velocity or number of features delivered, spend a week on the EBM guide first. PSPO II rewards answers about outcomes for customers and the organisation.
- PSPO I feels easy now. Take the free Product Owner Open assessment and our PSPO II diagnostic. If Product Owner Open is not comfortably above 90%, go back to the Scrum Guide - PSPO II will not be kind to gaps at that level.
If none of the three is true yet, PSPO I on its own is a legitimate stopping point. It is the more widely recognised of the two, and for a business analyst or Scrum Master moving towards product ownership it is the cheaper first signal.
A three-week bridge from PSPO I to PSPO II
This plan assumes you hold PSPO I, work as a Product Owner or alongside one, and can spend about an hour a day. Scrum.org publishes no study-hours figure for either level.
| Week | Focus | Checkpoint |
|---|---|---|
| 1 | Scrum Guide re-read for the "why"; EBM guide end to end; free PSPO II diagnostic | You can name one measure for each Key Value Area of your own product |
| 2 | Scenario practice by topic: vision and strategy, stakeholders, forecasting, portfolio | 80%+ on each topic set |
| 3 | Timed mocks: 40 questions, 60 minutes; error log; book the attempt | 90%+ held on fresh mocks |
In week 2, read every rationale, including on questions you answered correctly. The useful pattern in PSPO II mistakes is rarely a missing fact; it is a habit - promising scope, deferring to the loudest stakeholder, or solving a value problem with a process change. One line per mistake in an error log makes the habit visible after two or three mocks.
After PSPO II
The next step is PSPO III: 24 essay questions in 150 minutes, graded by Scrum.org experts, $500 per attempt, with PSPO I and PSPO II strongly recommended but not required. It is a different kind of assessment entirely, and few roles ask for it.
If you are weighing the Scrum Master path as well, our PSM II study plan covers the equivalent step on that side, and the PSM I vs CSM guide compares the entry-level options. For a wider view, start at which certification.
Fees, formats, languages, course terms, prerequisites and renewal rules verified on scrum.org on 3 October 2026. Scrum.org publishes no pass rate and no focus-area weights for PSPO I or PSPO II, so we give neither.