After three Sprints of discovery on a building-permit workflow, several core assumptions failed. The original release narrative is now wrong. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Discovery that proves the permit idea is wrong is not a wasted three Sprints — it is the city dodging a bad build. Change the story and the forecast. Sunk cost is how offices ship the workflow nobody should use.
Full Explanation
Failed assumptions are evidence; they must change the release narrative and the forecast. Protecting the original story to justify sunk discovery cost, reinstating failed spikes as mandatory scope, or implementing the disproven design all convert learning into waste. The Product Owner's accountability is maximizing value going forward, which includes killing or reshaping a permit bet when inspection says it will not work. Council is better served by an adapted outlook than by a defended fiction.