A county public-health clinic portal is behind on a flu-shot booking Increment. The health director wants to cancel this Sprint Review so Developers get two more hours of coding. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Skipping the Review to save time is like never tasting the soup so the cook can stir faster. That event is the regular chance to see whether clinic staff and residents can actually book shots. Empiricism on the product dies the moment inspection is postponed.
Full Explanation
The Sprint Review is the formal opportunity to inspect the Increment and adapt the Product Backlog with stakeholders. Canceling it to recover coding hours trades transparency and adaptation for output, which does not maximize product value. A written status deck or a quarterly steering review cannot replace inspecting a usable Increment against the Product Goal. The Product Owner should protect the event so empiricism on the clinic product continues.