Stakeholders for a municipal transit app demand a Gantt chart of every feature for the next twelve months. How should the Product Owner respond?
Select an answer to reveal the explanation.
Short Explanation
A year-long feature Gantt is a frozen menu, and rider needs will not sit still that long. Keep the Product Goal as the destination and a near-term forecast as the next few stops. Far-out bars dressed up as commitments just pretend the city already knows next winter's surprises.
Full Explanation
Scrum forecasting for a Product Owner is a Product Goal plus an empirical near-term outlook, not a contractual schedule of every transit feature. Long-range Gantt bars treated as Sprint commitments replace inspection with fake precision and make adaptation politically expensive. Stakeholders still deserve a transparent outlook; the Product Owner simply refuses to freeze unvalidated features a year out. Facilitation of the chart is not a Scrum Master substitute for Product Owner accountability on order and forecast.