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 uses what has already happened — recent Increments, observed throughput, and visible variation — to inform the next window. Historical plan documents, kickoff stretch goals, and best-ever Sprint math all ignore current capacity and volatility. Calling out uncertainty is part of transparency with council, not a failure of Product Ownership. The Product Owner's job is a honest outlook from evidence, not a defense of last year's calendar.