210- Definition of Done

Definition of Done (DoD)

• Explicit, shared vision of what “finished” means.
• Must be agreed on by all stakeholders; prevents misinterpretation and scope drift.
• Needs continuous refinement because requirements and perceptions change.

Why It Matters

• Aligns expectations; avoids surprises at delivery.
• Ensures final product matches stakeholder requirements.
• Lack of clear DoD ⇒ shock, disappointment, rework.

Common Pitfalls

• Stakeholder describes one thing but imagines another.
• Developer’s interpretation differs from stakeholder intent.
• Misalignment can occur in both directions (stakeholder → team, team → stakeholder).

Application Areas

• User stories: every story requires its own DoD.
• Releases: define DoD so delivered package meets expectations.
• Overall project deliverables: each major output needs a documented DoD.

Best Practices

• Revisit and confirm DoD frequently (“all the time”).
• Use concrete, testable criteria (e.g., \text{all acceptance tests pass} \Rightarrow \text{done}).
• Conduct regular validation reviews with stakeholders to maintain shared understanding.