Glossary

Definition of Done

A definition of done is an agreed, shared checklist of the criteria a piece of work must meet before it counts as finished — not just "code written" but tested, reviewed, documented and shippable. It removes the ambiguity that lets half-finished work get called "done".

A definition of done (DoD) is a shared, explicit agreement about what "finished" means for a piece of work. The term is formalised in the Scrum Guide, which treats it as a commitment to quality for every increment, but the idea applies anywhere: it is the checklist a task must satisfy before anyone is allowed to call it done.

A typical software definition of done might require that work is not just built, but also tested, peer-reviewed, documented, and deployable. The exact list matters less than the fact that everyone agrees on it in advance.

Why it matters

Without a definition of done, "done" means different things to different people — and the gap between them is where rework lives. A developer's "done" and a client's "done" can be weeks apart. A clear DoD closes that gap before the work starts, which is far cheaper than discovering it after.

A close cousin of a clear standard

A definition of done is really a standard made explicit. That's why it pairs so naturally with delegating outcomes: when you hand over a result, the definition of done is how the other person can judge their own work and know when they've actually hit the mark — without coming back to ask.

Frequently asked

Is the definition of done the same as acceptance criteria?

No. Acceptance criteria are specific to one piece of work and describe what that item must do to be accepted. A definition of done is a single shared standard that applies to every item, covering quality steps such as testing, review and documentation. An item is finished only when it meets both.

Who decides the definition of done?

The whole team agrees it together, ideally before work starts. In Scrum the development team owns it, but anyone affected by the standard — testers, reviewers, the customer — should have a say, because a definition of done only works if everyone treats it as binding.

Can a definition of done be used outside software?

Yes. Any work with a fuzzy finish line benefits from one: a report, a hire, a marketing campaign. Write down the criteria that separate "looks finished" from "is finished", agree them in advance, and you close the gap where rework hides.

Term

Critical Path

The critical path is the longest sequence of dependent tasks that determines the shortest possible time to finish a project. A delay to any task on the critical path delays the whole project; tasks off it have slack. Knowing yours tells you where a slip actually costs you time.

Term

After-Action Review (AAR)

An after-action review is a short, structured debrief that asks four questions: what was supposed to happen, what actually happened, why was there a difference, and what will we change? Originally a US Army practice, it turns experience into improvement — and works best when it's blameless but accountable.

Guide

How to Delegate Outcomes, Not Just Tasks

To delegate an outcome rather than a task, hand over four things together: the outcome the person owns, the standard it must meet, the constraints they must respect, and the check-ins you'll use. Task-handing tells people what to do; outcome-handing makes them responsible for whether it actually works.

← Back to the glossary