Definition of done

Also called: DoD, done criteria

The definition of done is the team’s shared list of what must be true before any piece of work counts as finished.

The definition of done applies to every story: reviewed, tested, documented where needed, deployable. Acceptance criteria are specific to one story. The definition of done is the standing bar they all have to clear.

Trouble starts when done means different things to different people. Engineering means merged, QA means tested on a build, Product means usable by a customer. UAT arguments are very often this disagreement arriving late.

I ask teams to say explicitly whether done includes evidence: on which environment it was verified, on which surfaces and by whom. A definition that ends at code complete moves the real work into release week.

Notes on this

More on this subject: Product validation and acceptance criteria. Written by Marius Ene, senior QA consultant. See how I work with teams or browse all terms.