Interactive graph
Definition of Done
Table of Contents
Done means shared proof - not dev says finished while QA, docs, and deploy still wait.
Key Concept
- Definition of done is the checklist everyone agrees means finished - code merged is rarely the whole list.
- Complete the Cycle closes owners and dates; done is the proof bar at the end of the cycle.
- Without a shared done, status theater hides half-finished work behind green tickets.
Level 1 - Recognize
Definition of done is the shared checklist that proves work is finished - not one person's opinion.
Level 2 - Explain
Like a move-out inspection list - keys, clean fridge, paid utilities - not only empty boxes by the door.
Level 3 - Use
Write done for the next epic: tested, documented, deployed, stakeholder notified - post in the channel before sprint start.
Level 4 - Connect
Status Without Theater needs honest done; Let the Team Own How still requires clear what done means.
Level 5 - Create
Review done at retro when status drifted mid-sprint - update the checklist, not blame individuals.
Examples
- Glad done included client training video - merged PR looked green; stakeholder still could not run reports.
- Team marked tickets done at code review - production flag and support handoff were missing; shared list fixed the gap.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| extends | PM Mindset | Execution bar inside the hub |
| extends | Complete the Cycle | Done closes the loop |
| extends | Status Without Theater | Honest status needs honest done |
| extends | Execution | Finished work, not discussed work |
