A library holds-notification story is marked ‘coded’ mid-Sprint. What success criteria should the adaptive team apply before calling the task done?
Select an answer to reveal the explanation.
Short Explanation
‘Coded’ isn’t the finish line—think of acceptance criteria as the inspection checklist and Definition of Done as the house rules before you hang the ‘Open’ sign. Both need a green light. Otherwise you’re delivering hope, not a finished story.
Full Explanation
When a library holds-notification story is marked "coded" mid-Sprint, adaptive success criteria require that the story meet its acceptance criteria and the team’s Definition of Done before it is considered complete. Coding progress alone is insufficient; Done means the agreed functional checks and quality bar are satisfied so civic patrons are not handed half-finished notifications. Associates should separate "in progress coding" from "successfully complete."
Treating any merged commit as done even if acceptance checks fail fails conceptually because merge status is not acceptance or DoD completion. Claiming only the mayor’s office sign-off matters while team DoD and acceptance criteria are optional fails because political sign-off does not replace the team’s quality agreements and story tests. Claiming done means the designer sketched a wireframe regardless of working software fails because adaptive completion centers on a working increment meeting criteria, not sketches alone.
Exam caveat: Completion equals acceptance criteria plus Definition of Done—not merge flags, political optionalization of DoD, or design sketches alone. Operational check: keep holds-notification stories in progress until acceptance tests and DoD items pass; demonstrate only Done work in the Sprint Review to library stakeholders.