A parks recreation booking product shows volatile throughput this quarter. Council wants a likely window for the next public release. What should the Product Owner use to brief them?
Select an answer to reveal the explanation.
Short Explanation
Last year's parks plan is a souvenir, not a weather report. Council needs what the booking product is actually finishing now, warts and all. Brief the recent throughput, say the range is still jumpy, and leave the stretch-velocity pep talk at the door.
Full Explanation
Empirical release planning for a parks recreation booking product uses what has already happened—recent Sprint outcomes, observed throughput, and visible variation—to brief council on a likely public-release window. Calling uncertainty out is part of transparency with elected officials, not a failure of Product Ownership. Last year's approved parks plan names an original target month that no longer reflects current capacity or volatility, so it is a souvenir rather than a forecast input. A stretch velocity agreed in a motivational kickoff encodes optimism bias and systematically overstates what the Developers can sustainably finish. Dividing remaining story points by the single highest Sprint ever recorded likewise cherry-picks peak performance and ignores the volatility council is asking about. Exam caveat: PSPO II distinguishes evidence-based forecasts from plan documents and motivational metrics; the Product Owner's brief must survive inspection at the next Sprint Review. Operational check: present median recent throughput, the spread across the last several Sprints, and an explicit statement of what would move the release window earlier or later before council treats any month as locked.