PSPO I · Scrum.org · Product Backlog Management · Bank updated 2026-07-03
PSPO I practice questions: Product Backlog Management
5 free questions from 72 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Product Backlog Management section of our PSPO I bank (72 questions on this area). Every question is original, with the correct answer explained and linked to the source it is drawn from.
1/5 · Product Backlog Management
During refinement, the Product Owner tells the Developers, "This item is only 2 story points, so let's plan for it that way." A Developer disagrees and sizes it much higher. According to the Scrum Guide, who has the final say on the size of a Product Backlog item?
AThe Product Owner, because ordering and sizing are combined under Product Backlog management.
BWhichever party most recently refined that item gets to set its final size.
CThe Scrum Master, who mediates estimate disagreements between the Product Owner and Developers.
DThe Developers, because the people who will perform the work make the final estimate.
Show answer & explanation
D is correct. The Guide states the Developers who will be doing the work are responsible for the sizing. The Product Owner may influence the Developers by helping them understand and select trade-offs, but the people who will perform the work make the final estimate.
↗ The Scrum Guide (2020) — Product Backlog Management
2/5 · Product Backlog Management
Which statement about changing the Sprint Backlog during an active Sprint is correct per the Scrum Guide?
AAny Scrum Team member may add items directly to the Sprint Backlog without discussing it with the Developers.
BThe Scrum Master updates the Sprint Backlog whenever the Daily Scrum reveals a change in plan.
CThe Product Owner can reorder or swap Sprint Backlog items at any time to reflect new stakeholder requests.
DOnly the Developers can change their plan during the Sprint, since the Sprint Backlog belongs solely to them.
Show answer & explanation
D is correct. The Scrum Guide is explicit: 'Only the Developers can change their plan during the Sprint,' reinforcing that the Sprint Backlog is a plan by and for the Developers, even though the Product Owner can influence future scope through negotiation.
↗ The Scrum Guide (2020) — Product Backlog Management
3/5 · Product Backlog Management · easy
A Scrum Team needs to track upcoming work to reduce technical debt and shore up infrastructure that isn't a customer-facing feature. According to the Scrum Guide, where does this kind of work belong?
AIn a separate technical-debt register maintained solely by the Developers, kept invisible to the Product Owner.
BOn the engineering roadmap, outside of Scrum artifacts entirely.
CIn the Product Backlog, since it is the single source of work needed to improve the product.
DIn the Sprint Backlog only, added directly by Developers without ever appearing in the Product Backlog.
Show answer & explanation
C is correct. The Scrum Guide defines the Product Backlog as the single source of work undertaken by the Scrum Team, covering all changes needed to improve the product — including technical debt, infrastructure, and other non-feature work, not solely visible features.
↗ The Scrum Guide (2020) — Product Backlog Management
4/5 · Product Backlog Management · hard
A Scrum Team is discussing how the concept of 'commitment' applies to each of the three Scrum artifacts. Which pairing is correct per the Scrum Guide (2020)?
AProduct Backlog → Sprint Goal; Sprint Backlog → Product Goal; Increment → Definition of Done.
BProduct Backlog → Product Goal; Sprint Backlog → Sprint Goal; Increment → Definition of Done.
CProduct Backlog → Definition of Done; Sprint Backlog → Product Goal; Increment → Sprint Goal.
DAll three artifacts share a single commitment — the Product Goal — since it is described as the overarching objective for the Scrum Team.
Show answer & explanation
B is correct. The Scrum Guide (2020) introduced explicit commitments for each artifact to reinforce transparency and focus: the Product Goal for the Product Backlog, the Sprint Goal for the Sprint Backlog, and the Definition of Done for the Increment.
↗ The Scrum Guide (2020) — Product Backlog Management
5/5 · Product Backlog Management
A stakeholder asks to see exactly what the Developers plan to build this Sprint and how they intend to do it, without changing anything themselves. Is this consistent with the Scrum Guide?
ANo — only the Product Owner may view the Sprint Backlog on stakeholders' behalf and report progress separately.
BYes — the Sprint Backlog is described as a highly visible, real-time picture of the Developers' plan; belonging solely to the Developers concerns who changes it, not who may view it.
CYes, but only during the Sprint Review, since that is the only point at which the Sprint Backlog is made transparent.
DNo — the Sprint Backlog is private to the Developers and may not be viewed by anyone outside the Scrum Team.
Show answer & explanation
B is correct. The Scrum Guide (2020) calls the Sprint Backlog 'a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint.' 'Belongs solely to the Developers' governs who may change the plan, not who may observe it — consistent with transparency as a Scrum pillar.
↗ The Scrum Guide (2020) — Product Backlog Management
Other PSPO I areas
The same kind of free sample for every other section of the PSPO I bank:
Study Product Backlog Management with instant feedback
6 free questions · filter study mode by area and difficulty · error log with spaced repetition · no card, no dumps, no ads.
Create your free account →
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by Scrum.org. PSPO I and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official Scrum.org materials (as of August 2026); always confirm current details with the vendor before booking.