A county public-health clinic portal receives a federal grant earmarked for a wellness-points gamification module. Clinic staff and residents never asked for it; intake interviews show missed appointment reminders and language access as the real immunization-completion blockers. Grant language still allows digital engagement that improves immunization completion. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
A pile of grant cash is not the same as a citizen needing the thing. It is like a coupon for a flavor nobody ordered—you can still ask whether the rules let you spend it on flavors people actually want. The Product Owner steers inside the constraint toward validated need instead of treating unused money as value.
Full Explanation
Funding availability is not validated product value. On a county public-health clinic portal, advanced Product Ownership means maximizing immunization-completion outcomes for residents and the organization within real constraints, including grant language. When a federal award pays for a class of digital engagement that improves completion rather than mandating one unused gamification module, the Product Owner should negotiate to apply that money to evidenced needs—appointment reminders and language access—that still satisfy the grant. Building the unused wellness-points module because leftover money is expiring maximizes output and burn-down of a budget, not citizen outcomes. Rejecting the grant outright and freezing the Product Backlog until another funding source appears discards a usable constraint instead of steering inside it. Splitting the Scrum Team so Developers write grant paperwork while a vendor ships the module off the Product Backlog destroys transparency, dual-tracks accountability, and bypasses empiricism on the civic Increment. Exam caveat: grant earmarks constrain spend categories; they do not automatically define value or Product Backlog order—value still rests on evidence of outcomes for clinic staff and residents. Operational check: map grant-eligible outcomes to the top validated blockers, document the negotiated redirect with funder language, order reminder and language-access items on the Product Backlog, and inspect completion and equity measures after the next releasable Increment rather than celebrating grant burn rate.