On a county vaccine-registry product, Developers mark items Done when the code is committed, even though clinic staff cannot use the Increment and required privacy checks are skipped. What should the Product Owner insist on?
Select an answer to reveal the explanation.
Short Explanation
Coded is not Done any more than a kitchen cooked a meal it never plated or safety-checked. Clinic staff cannot use a registry they cannot trust. Hold the line: Done means a usable, quality Increment.
Full Explanation
The Definition of Done describes the quality required of the Increment. On a county vaccine-registry product, marking items Done when code is committed—while clinic staff cannot use the Increment and required privacy checks are skipped—hides undone quality work and destroys transparency. The Product Owner should insist on a Definition of Done that produces a usable, quality Increment rather than half-finished code, because coded is not Done for public-health trust.
Keeping coded as Done so velocity stays high for the health board games a measure with unfinished work. Moving privacy checks to a hardening Sprint after several coding Sprints recreates an undone registry and deferred risk. Letting each Developer decide a personal Done so the team stays self-managing misreads self-management as optional quality.
County vaccine registries touch privacy and clinic trust; Done that stops at a commit message is not public-health quality.
Exam caveat: PSPO II Definition of Done must yield a usable Increment; velocity that counts privacy-skipped registry work is misleading.
Operational check: update Done to require clinic-usable registry behavior plus mandatory privacy checks, and recount any 'Done' items that fail that bar as not Done.