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. Forecasts are empirical and will sometimes miss; concealing that destroys trust and delays adaptation of the Product Backlog and release outlook. The Product Owner should report the miss promptly, share evidence, and invite a value-based response. Relabeling work, shifting blame, or decorating charts substitutes theater for inspection.