“"The practice exams helped me understand Product Owner responsibilities much more clearly."”
Eleanor Price
Product Owner
The PSPO I assessment is 80 questions in 60 minutes, taken on your own schedule directly through Scrum.org’s own testing platform — there’s no Pearson VUE or PSI test center involved, no webcam proctor, and no appointment booking. You log in, start the clock, and go. That’s less than 45 seconds per question on average, which is the single biggest reason people run out of time: not because the Scrum concepts are hard, but because the question format eats time you don’t budget for.
Questions come in three formats mixed together: single-answer multiple choice, multiple-answer (select all that apply, with no partial credit), and true/false. The multiple-answer questions are where pacing falls apart — they read like a single question but take two or three times as long to work through carefully, and the exam doesn’t tell you in advance how many options are correct. You need an 85% score to pass, which is 68 of 80 correct. That’s a high bar compared to most IT certification exams sitting in the 65-75% range, and it leaves almost no room for guessing your way through.
Scrum.org doesn’t publish official domain weightings for PSPO I the way providers like AWS or CompTIA do for their exams. What they do publish are three Focus Areas drawn from the Professional Scrum Competencies framework.
Focus Area | What It Covers | Official Weighting |
|---|---|---|
Understanding and Applying the Scrum Framework | Empiricism, the Scrum Team, Scrum Events, Scrum Artifacts, Definition of Done | Not published by Scrum.org |
Developing People and Teams | Self-managing teams and how a Product Owner works within one | Not published by Scrum.org |
Managing Products with Agility | Forecasting & release planning, product vision, product value, Product Backlog management, business strategy, stakeholders & customers | Not published by Scrum.org |
In practice, the third area carries the most exam weight simply because it covers the most ground — it’s six sub-topics bundled into one Focus Area, and Product Backlog management questions alone show up repeatedly throughout a attempt.
The difference between the Product Goal and a vision statement. People memorize “the Product Goal describes a future state of the product” and then get tripped up on scenario questions that ask them to distinguish it from product vision, from a release goal, or from a Sprint Goal. These are four different things in the 2020 Scrum Guide and PSPO I tests whether you actually know the boundaries between them, not just the definitions.
Questions that test what Scrum does not prescribe. A meaningful chunk of PSPO I is written to catch people who’ve absorbed “best practices” from blog posts, previous jobs, or other certifications rather than the Scrum Guide itself. If you’ve worked as a product owner using story points, a product roadmap template, or a specific backlog refinement cadence, PSPO I will present a question where the “common practice” answer is wrong because the Scrum Guide doesn’t mandate it. Candidates who’ve never worked as a PO sometimes do better here than experienced ones, because they haven’t learned habits to unlearn.
Multiple Product Backlogs vs. multiple Scrum Teams. This is a specific, recurring trap: Scrum.org is explicit that a single product has one Product Backlog even when several Scrum Teams work on it together. Candidates regularly answer this wrong because it feels intuitive that more teams means more backlogs.
Scaling and stakeholder questions that aren’t about Scrum rules. A portion of the exam draws on “application of Scrum based on your own experience,” per Scrum.org’s own description of the assessment. These questions don’t have a single Scrum Guide quote to fall back on — they test judgment about stakeholder management and value maximization, and people who’ve only memorized the guide tend to freeze on them.
Don’t treat practice questions as a way to memorize answers — treat them as a way to find out which Scrum Guide concepts you’re fuzzy on, then go re-read those sections. Because PSPO I leans heavily on scenario and judgment-based questions rather than pure recall, question banks that just test “what does the Scrum Guide say about X” in isolation won’t fully prepare you for the thing.
Time yourself in blocks that match the exam’s pace — roughly 45 seconds a question — rather than untimed. The multiple-answer format is the part that catches people off guard on test day, so when you hit one in practice, don’t rush past it; work out why each selected option is correct and each unselected one isn’t. That habit transfers directly.
Scrum.org also offers a free, non-certifying Product Owner Open assessment (15 questions drawn from the same pool concepts). It’s worth running until you’re consistently scoring well above 85% there before you spend the $200 on an actual attempt — it’s built from the same source material and gives you a free signal on readiness.
Answering from job experience instead of the Scrum Guide. -world product ownership often includes practices the Scrum Guide doesn’t define — roadmaps, story points, specific ceremonies. PSPO I grades against the Guide, not against how your last company did Scrum.
Treating the Developing People and Teams focus area as filler. It’s a smaller slice of the exam, but self-managing teams questions catch people who assumed this area was negligible and skipped reviewing it.
Running out of time on multi-select questions. Partial credit doesn’t exist. Spending four minutes perfecting one multiple-answer question at the expense of three later questions is a losing trade.
Confusing Product Owner accountability with Scrum Master accountability. Several questions are written specifically to test whether you understand where the PO’s authority starts and stops relative to the rest of the team — this is a common point of confusion for people transitioning from a Scrum Master or project manager background Need additional preparation? Try our NetApp Certified Data Administrator, ONTAP (NCDA) mock test.
New to Scrum entirely: Plan on 3-4 weeks. Start with the Scrum Guide itself (it’s short — read it more than once), then work through the Professional Scrum Product Owner Fundamentals self-paced course material before touching practice questions, since you need the conceptual foundation first.
Working Product Owner or experienced Agile practitioner: 1-2 weeks is usually enough, but don’t skip the Scrum Guide re-read — this is the group most likely to fail from assuming workplace habits are “correct Scrum.” Spend your prep time specifically hunting for places where your job’s practices diverge from the Guide’s actual text.
Retaking after a failed attempt: Scrum.org gives you a competency-area performance breakdown after a failed attempt (not individual question results) — use it. If you scored weak on Managing Products with Agility, that’s where your remaining study time goes, not a full re-read from scratch. Most retake failures come from repeating the same prep approach rather than targeting the actual gap.
Last updated on Oct, 31 2026