At Sprint Review for the city parks pass, evidence shows residents abandon the mayor’s favorite gated “VIP picnic locker” flow. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
When the video of residents bouncing off the VIP lockers is sitting right there, doubling down is just stubbornness in a nicer suit. Courage is changing the backlog when the evidence punches a favorite idea. Parks visitors already voted with the back button.
Full Explanation
Empiricism requires adaptation when inspection contradicts a hypothesis, including a politically favored one. At Sprint Review for a city parks pass, evidence that residents abandon the mayor's favorite gated VIP picnic-locker flow is a signal to change Product Backlog order. Courage is the Scrum Value that lets the Product Owner adapt despite executive attachment, protecting resident value and public trust over face-saving persistence.
Protecting the favorite initiative by discounting Sprint Review evidence as unrepresentative refuses inspection. Asking Developers to keep building lockers in secret so the next Review looks more successful destroys transparency and doubles down on a falsified idea. Converting the locker flow into a fixed-scope project so empiricism no longer applies walls the bad bet off from adaptation entirely.
Exam caveat: PSPO II courage items commonly pair political favorites with contradictory evidence; adaptation of the backlog is the expected move, not narrative management.
Operational check: after Review, reorder or remove the picnic-locker initiative based on abandonment evidence, document the decision against the Product Goal, and brief the mayor's office on the evidence rather than on loyalty to the original idea.