During a public-health clinic portal review, a council aide asks why a major backlog theme exists. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
When someone asks "why this?", the honest answer is a line back to the vision, not a pile of story points. If the clinic portal exists so residents can book shots without a two-week phone wait, every big theme should point at that change. No trail back to the vision usually means the theme is inventory, not strategy.
Full Explanation
When a council aide asks why a major backlog theme exists on a public-health clinic portal, the Product Owner should trace the theme to a specific element of the Product Vision and the citizen outcome it is meant to move. That traceability is how vision earns its keep in stakeholder conversations. Reciting the last three Sprint velocities only shows busyness, not purpose. Handing the aide the full unrefined Product Backlog to vote items up or down outsources ordering without shared direction. Replacing the vision with the aide's preferred feature list so why-this questions stop converts political preference into strategy. Exam caveat: backlog themes should be explainable from vision and outcomes, not from activity metrics. Operational check: for each major theme, write one sentence linking it to a vision element and a measurable clinic or resident outcome, and use that sentence in Review and budget briefings when challenged. Clinic portal backlog themes should trace to Product Vision elements and citizen outcomes when council aides ask why; velocity is not an answer. Keep a one-sentence vision-to-outcome link for each major theme in Review and budget briefings. Keep a living map from each major clinic-portal theme to a vision clause and a citizen or clinician outcome measure, and bring that map when aides challenge backlog composition.