Toolkit/lens
Definition of Done (DoD) Checklist
The exit contract. Ensures work is complete, stable, and aligned.
qualityexit-criteriacompletionchecklist
The Definition of Done (DoD) is the exit contract. It ensures work is complete, stable, and aligned with what was agreed—not just "close enough."
The DoD Wizard Artifacts
To legally transition a phase (e.g., Pilot to MVP) in the Accelerator, the DoD tab must be satisfied and structurally proven.
1. Acceptance Criteria
Binary statements defining the boundaries of completion. If it is not in the Acceptance Criteria, it is Out of Scope.
Example: "Branding materials clearly communicate principles of transparency and clarity."
2. Test Cases
Executable validation paths. Every Acceptance Criterion must be backed by a mapped Test Case containing:
- ☐Description of the test
- ☐Execution Steps
- ☐Expected Result
Evidence References
To declare "Done" in the Governance OS, you must link the physical proof. This could be a link to a passed CI/CD pipeline, a signed-off UAT document, or an operational monitoring dashboard.
The Reality Check
If DoD is not met, delivery is not complete—regardless of sprint demos or stakeholder enthusiasm. You cannot bypass the DoD without triggering a Change Forum.