At Sprint Review, residents show that the parking-permit product's renewal reminder is the only thing they actually use—and it fails often. The Product Owner usually waits for the quarterly roadmap workshop to change order. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Feedback that sits until next quarter is leftovers in the fridge. Residents just told you the renewal reminder is the meal—and it is burnt. Move it up the parking backlog today so the next Sprint can cook from evidence, not from last season's menu.
Full Explanation
Empiricism requires timely adaptation of the Product Backlog when evidence arrives. When Sprint Review shows residents rely on the parking-permit renewal reminder—and it fails often—while the Product Owner usually waits for the quarterly roadmap workshop to change order, the Product Owner should reorder within hours so the next Sprint can act on that evidence. Capturing feedback in minutes and waiting for the next quarterly workshop delays adaptation. Freezing the backlog until Marketing rewrites the annual campaign elevates a plan document over resident outcomes. Instructing Developers to insert reminder work into the current Sprint Backlog without discussing Product Backlog order and the Sprint Goal bypasses collaboration and transparency. Exam caveat: mid-Sprint changes still need Product Owner–Developer agreement against the Sprint Goal; immediate Product Backlog reorder for the next Sprint is the default response to strong Review evidence. Operational check: raise reminder reliability on the Product Backlog immediately after Review, align the next Sprint Goal if warranted, measure reminder success and renewal completion, and stop treating the quarterly workshop as the only change window for the civic parking product.