Ordering is a product decision under uncertainty
The Product Backlog is an emergent ordered list of work needed to improve the product. The Product Owner remains accountable for effective management and maximizing product value. Ordering can consider evidence about benefit, risk, dependencies and learning needs; Scrum does not prescribe one universal scoring formula. A small item can be useful without automatically being first. A large customer can offer important evidence without automatically deciding every priority. Distinguish the basis for a decision from a numerical ranking that the given information cannot support. A careful answer explains which evidence matters and what remains uncertain.
Product Goal and Sprint Goal support different horizons
The Product Goal describes a future state of the product that gives the Scrum Team direction. The team must fulfill or abandon one Product Goal before taking on the next. A change in evidence can justify reconsidering direction; keeping several competing goals nominally active is not a transparent substitute for that decision. The Sprint Goal provides a single objective for a Sprint. The exact work needed to pursue it can become clearer as the team learns. These goals should create focus without pretending that a complex problem will unfold exactly as the original task list predicted.
Worked example: new information during a Sprint
Fictional case: a membership product is working toward a Sprint Goal of making renewal reliable. A newly discovered failure affects the same customer path. First ask whether the Sprint Goal is still valuable and whether the proposed response supports or endangers it. The Product Owner and Developers can discuss and renegotiate scope as more is learned. Developers adapt the plan for the work. Automatically rejecting every new item would prevent learning; automatically inserting every urgent request would hide the impact on the objective. Make the trade-off visible, preserve quality and explain what changes in the plan.
Inspect value with relevant observations
A count of completed tasks describes output, not necessarily customer value. If a Product Goal concerns successful booking, observed completion behavior and feedback about obstacles may be more relevant evidence than meeting counts or task splitting. Interpret such observations carefully. Context, incomplete data and competing explanations can limit a conclusion; a changed number alone is not proof of causation. These suggested measures are original applications of empiricism to a fictional product, not mandatory Scrum metrics. At Sprint Review, stakeholders and the Scrum Team can inspect outcomes and changes in the environment to inform further adaptations.
Transfer check: keep requests distinct from commitments
At Review, two stakeholders request different improvements. Does collaboration mean both requests are automatically committed for the next Sprint? No. The input can inform backlog adaptation, while Product Owner accountability remains clear and planning still considers what is appropriate. Now suppose the Product Goal itself appears obsolete. Describe an explicit decision to fulfill or abandon it before taking on a new goal rather than quietly layering contradictory directions together. Use the linked practice to compare ordering evidence, goal focus, stakeholder input and outcome observations. Write what the available evidence supports and what it does not establish; uncertainty is part of a defensible product decision.
A Product Backlog contains a low-effort cosmetic change, a risk-reduction investigation and a feature with uncertain customer benefit. What is the best basis for the Product Owner’s ordering decision?
- The Product Owner is accountable for product value and effective backlog management. Ordering can consider several factors in the context of the Product Goal, including risk, dependencies and what the team needs to learn. Scrum does not prescribe one universal scoring formula. The available information is insufficient to rank these three items numerically; the question asks for a defensible basis for the decision, with uncertainty left visible.
Compare the other answer choices
Low effort can matter, but by itself it does not establish which item best advances product value or learning.
An unchanging formula that ignores evidence conflicts with an empirical approach to complex product decisions.
Stakeholder influence supplies input but does not automatically determine value or transfer Product Owner accountability.
Try it, then explain it.
Complete a short set without looking at the example. After each answer, explain which evidence or rule supports your decision and why the alternatives do not fit.
Sources & authorship
Original OpenExam explanations and examples. References support the concepts; they are not the source of copied questions. Independent educator review is pending.
The Scrum Guide — November 2020