The business-license renewal product is always green on server uptime, yet residents still abandon renewals. How should the Product Owner measure Current Value?
Select an answer to reveal the explanation.
Short Explanation
A server that is up while nobody finishes a renewal is a well-lit empty counter. Current Value is whether residents get the license done and how they felt doing it. Uptime matters, but it is not the whole scoreboard.
Full Explanation
Server uptime that is always green while residents abandon business-license renewals shows that availability is necessary but not sufficient Current Value. The Product Owner should measure citizen satisfaction and renewal task-completion rate, not uptime alone. Treating uptime as the sole Current Value measure celebrates infrastructure while the citizen job fails. Replacing outcome metrics with a velocity chart shows delivery activity, not renewal success. Counting renewal screens shipped this year again confuses output with Current Value. Exam caveat: Current Value for civic products centers on successful citizen outcomes and satisfaction. Operational check: instrument renewal completion and abandonment reasons, review them alongside uptime in Sprint Review, and order backlog work that removes abandonment drivers even when servers already look healthy. Business-license Current Value lives in renewal completion and satisfaction; green uptime with abandonment is incomplete measurement. Instrument abandonment reasons and order backlog work against those drivers even when infrastructure looks healthy. Pair uptime SLOs with renewal completion and satisfaction on the same Review slide so green infrastructure cannot mask abandoned license renewals.