A city product roadmap slide lists months of committed features. What should the Product Owner change?
Select an answer to reveal the explanation.
Short Explanation
Far-out roadmap boxes look like reservations, but they are really guesses in a nice font. Turn the distant stuff into themes and hypotheses, and keep crisp order only on what is actually next. A slide is a forecast, not a lease on next autumn's features.
Full Explanation
A roadmap that presents far-horizon features as commitments confuses directional intent with Product Backlog order. The Product Owner keeps near-term items detailed and ordered for value, while later work stays in themes or hypotheses until evidence justifies refinement. Removing all outlook beyond the current Sprint is unnecessary secrecy; copying the slide into months of Sprint Goals hardens the contract. Forecasting stays honest when only the near term carries commitment-like detail.