A quick-win one-off report on the public-health inspection app would need weekly babysitting and would crowd out later experiments. What should the Product Owner weigh before saying yes?
Select an answer to reveal the explanation.
Short Explanation
A quick win that leaves a baby on the team's doorstep is not a win. If inspectors need a weekly hand-held report, tomorrow's experiments die in the support queue. Weigh the whole bill — including future capacity — before celebrating.
Full Explanation
Before saying yes to a quick-win one-off report on the public-health inspection app that needs weekly babysitting and would crowd out later experiments, the Product Owner should weigh total value, including the later hit to Ability to Innovate if support burden consumes team capacity. Ceremony dates for inspection-week announcements alone understate the cost. Finishing inside the current Sprint regardless of future cost ignores the ongoing tax. Adding story points to this quarter's dashboard measures output, not whether the report is worth the innovation drag. Exam caveat: total cost of ownership and Ability to Innovate are part of value economics, not afterthoughts. Operational check: estimate ongoing support hours, opportunity cost to planned experiments, and expected inspection outcome benefit; approve only if net value remains positive after those costs, otherwise decline or automate fully before committing. One-off public-health reports that need weekly babysitting tax Ability to Innovate; total value includes that future capacity hit. Estimate support burden and opportunity cost before approving ceremony-driven quick wins. If the inspection-week report cannot be automated, price the weekly support hours against planned experiments for the next quarter and decline when Ability to Innovate would take the larger hit.