PSPO II · Scrum.org · Product Value and Backlog Management at Scale · Bank updated 2026-09-12
PSPO II practice questions: Product Value and Backlog Management at Scale
5 free questions from 16 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Product Value and Backlog Management at Scale section of our PSPO II bank (16 questions on this area, which carries 15% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.
1/5 · Product Value and Backlog Management at Scale · easy
In the Evidence-Based Management Guide, the Key Value Area 'Unrealized Value' is best described as measuring:
AThe organization's capacity to deliver new capabilities that support learning and adapting based on market feedback
BThe value already delivered to customers by the product as it exists today
CThe speed at which a single idea moves from being conceived to being delivered to customers
DThe potential future value that could be captured if the organization better met the needs of current and future customers, relative to an ideal or total addressable market
Show answer & explanation
2/5 · Product Value and Backlog Management at Scale
A Product Owner for a complex product notices velocity declining across three releases even though no new scope has been added; investigation shows rising defect rates and lengthening regression cycles caused by accumulated technical debt. Stakeholders pressure the Product Owner to keep adding new features, arguing 'customers don't pay for debt work.' Which response best aligns with EBM and Scrum guidance on maximizing value?
AContinue prioritizing only customer-facing features since Ability to Innovate is an internal engineering concern outside the EBM value areas and irrelevant to backlog ordering
BEscalate the decision to the Scrum Master, since the Scrum Master is accountable for technical debt trade-offs on behalf of the Product Owner
CInstruct the Developers to address the technical debt entirely outside of Sprints, on their own time, since the Product Backlog should contain only customer-value items
DMake the impact of technical debt visible using evidence such as declining delivery capability and rising unplanned work, then negotiate backlog capacity for debt reduction alongside features, since eroding Ability to Innovate threatens future value delivery
Show answer & explanation
3/5 · Product Value and Backlog Management at Scale
In a complex product built by three Scrum Teams, a 'PO Proxy' assigned to each team logs every stakeholder request directly into the shared Product Backlog and orders items strictly by the date the request was received, without evaluating value or consulting the accountable Product Owner. What anti-pattern does this describe?
AThis is a distributed-Product-Owner model explicitly recommended by the Scrum Guide for products built by more than one team
BThe 'backlog secretary' anti-pattern; the Product Owner remains accountable for developing and communicating the Product Goal and ordering the Product Backlog to maximize value, even if refinement tasks are delegated
CThis is acceptable because the Scrum Guide allows any stakeholder to directly reorder the Product Backlog according to the urgency of their own request
DThis is correct practice, since Product Backlog ordering should always follow first-in-first-out sequencing to ensure fairness to stakeholders
Show answer & explanation
4/5 · Product Value and Backlog Management at Scale
A Product Owner for a complex product must choose between two roughly equal-effort items competing for the same two teams' capacity next Sprint. Item X unlocks a regulatory requirement carrying a financial penalty that escalates weekly if delayed, but has modest ongoing customer value. Item Y offers high ongoing customer value with no external deadline. What is the most defensible ordering decision?
AOrder by whichever item the majority of Developers find more technically interesting, since motivation drives better quality regardless of order
BSplit both teams so each item receives half capacity in parallel to hedge against both risks equally
COrder Item Y first since the Product Backlog should always be ordered strictly by long-term customer value, and regulatory penalties are a legal matter separate from Product Backlog ordering
DOrder Item X first: although Item Y offers higher steady-state value, Item X's cost of delay accelerates sharply over time, and containing that escalating risk protects the organization's ability to capture Item Y's value later without penalty
Show answer & explanation
5/5 · Product Value and Backlog Management at Scale · hard
A very complex product is built by six Scrum Teams. Leadership proposes giving each team its own independent Product Backlog and its own Product Owner, each free to define value and order work purely for their own component, in order to 'move faster.' Which risk is most significant here from the Scrum Guide's perspective on Scrum applied across multiple teams?
AThe main risk is that six Product Owners increases payroll cost, which is a budgeting concern unrelated to Scrum
BWithout a shared Product Goal and coordinated ordering across the component backlogs, teams may locally optimize their own component's value while the overall product's value, which depends on integrated increments, is not maximized or may not even be usable
CThere is no risk as long as each team still holds its own Sprint Review, since Sprint Reviews alone guarantee integration across independently ordered component backlogs
DNone; the Scrum Guide explicitly requires exactly this structure of one independent Product Backlog and one Product Owner per team for any product built by more than one team
Show answer & explanation
Other PSPO II areas
The same kind of free sample for every other section of the PSPO II bank:
Study Product Value and Backlog Management at Scale 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 II 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.