Definition of Done

Why It Matters

Without a shared definition of done, "finished" means different things to different people. A developer might consider a feature done when the code is written. A product manager might consider it done when it is tested and documented. A customer success lead might consider it done when the user has been trained on it. These gaps are invisible until they cause problems: rework, missed deadlines, and frustrated stakeholders who expected more than they received.

Where It Comes From

The concept originates in agile and Scrum methodology, where a definition of done is established at the team level and applied to every increment of work. The Scrum Guide defines it as "a formal description of the state of the Increment when it meets the quality measures required for the product." But the principle extends far beyond software development. Any team that produces deliverables benefits from answering the question: how do we know this is complete?

How to Build One

An effective definition of done is specific, observable, and agreed upon before work begins. It should answer: what criteria must be met for this work to be considered complete? This typically includes quality standards (reviewed, tested, documented), communication requirements (stakeholders informed, handoff completed), and readiness criteria (can the next person or team pick this up without coming back to ask questions?).

• Define completion criteria before work starts, not after
• Make criteria observable: anyone should be able to verify whether each condition is met
• Include handoff readiness, not just task completion
• Revisit the definition when patterns of rework or confusion emerge

Common Failure Modes

The most common failure is treating "done" as implicit. Teams assume everyone shares the same understanding until they discover otherwise at the worst possible moment. A second failure is making the definition too vague ("done means high quality") or too rigid (a 20-item checklist for every task regardless of size). The best definitions scale with the complexity of the work and focus on the criteria that have historically caused confusion or rework.