A transit real-time arrival feature meets the Definition of Done but sits undeployed behind a quarterly release freeze. What should the Product Owner argue about value?
Select an answer to reveal the explanation.
Short Explanation
Done in a drawer is a wrapped gift still in the closet. Riders do not get value from code they cannot see. Until the arrival board is live, that work is potential — not realized — value.
Full Explanation
A transit real-time arrival feature that meets the Definition of Done but sits undeployed behind a quarterly release freeze has not yet delivered value to riders. The work remains Unrealized Value until riders can actually benefit from the Increment. Claiming value the moment Developers marked it Done confuses internal completeness with citizen benefit. Claiming value at Sprint Planning when the item was selected is even earlier and emptier. Counting story points as Current Value until release day treats output metrics as outcomes. Exam caveat: value is realized when users can use the Increment, not when internal states change. Operational check: challenge the release freeze for Done, releasable rider-facing work, track time from Done to production, and report undeployed Done items as Unrealized Value in stakeholder briefings. Undeployed Done transit arrival work remains Unrealized Value until riders benefit; release freezes that warehouse Done Increments delay civic outcomes. Track Done-to-production time and challenge freezes for releasable rider-facing Increments. Escalate release-freeze policies that warehouse Done rider-facing Increments; report the count and age of undeployed Done items as Unrealized Value until riders can use them.