Parks recreation booking missed the published late-summer release forecast after a spike in failures on a risky integration. Stakeholders have not heard yet. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Bad news is like a leaky roof: waiting never makes the attic drier. Tell people the forecast slipped, and tell them what you learned. Hidden misses just turn into louder surprises.
Full Explanation
Openness is a Scrum Value and a practical stakeholder skill for civic Product Owners. When parks recreation booking misses a published late-summer release forecast after risky integration failures, concealing the miss destroys trust and delays adaptation of the Product Backlog and release outlook. The Product Owner should communicate the forecast miss promptly and openly, including what was learned from the failure spike so stakeholders can help adapt priorities. Relabeling work, shifting blame, or decorating charts substitutes theater for inspection and leaves parks users surprised later.
Keeping the old forecast slide in circulation fails because it knowingly misleads stakeholders and postpones reordering. Blaming the Scrum Master in a council packet fails by politicizing accountability instead of sharing product evidence. Inflating remaining story points so the burn chart looks on track fails because metric theater hides empiricism and invites worse surprises.
Exam caveat: Forecasts are empirical and will miss; prompt, open communication with learning attached is the professional response. Operational check: Within one business day of confirming the miss, send stakeholders a short note with the old forecast, the new outlook, the integration learning, and the backlog adaptations under consideration.