A school-enrollment product team is told to finish a separate 'release planning' phase and lock next year's dates before any Sprint starts. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
A separate release-planning banquet before school enrollment 'starts' is leftover waterfall — the cafeteria is already serving. Forecasts get updated while real Sprints run, not locked in a phase that pretends uncertainty is gone. Keep the outlook inside the same Scrum events that inspect actual Increments.
Full Explanation
Scrum has no pre-Sprint release-planning phase that freezes dates before empiricism begins. The Product Owner keeps an empirical forecast alive through Product Backlog order, Sprint Planning, Sprint Review, and refinement as enrollment demand and technical discoveries change. A locked calendar phase hides uncertainty and delays learning. Continuous forecasting is how release planning actually works on a Scrum product.