Done

[duhn]

Definition of Done

A piece of work is “Done” when it satisfies the (pre-existing) agreement between Stakeholders and Developers about what it takes for the work to be complete;

“Done” for a Story usually consists of Acceptance Criteria (which could be a TimeBox), a Standard of Care, and General Agreements;

A Software Increment is “Done” when “the increment consists of thoroughly tested, well-structured, and well-written code that has been built into an executable and that the user operation of the functionality is documented… This is the definition of a ”Done” increment.” (per Ken Schwaber, Agile Project Management with Scrum, Microsoft Press, 2004, pg. 12). The concept of “Done” has often been extended to Epics, Sprints, Releases, and so on…(Compare to UnDone)

Examples

The Story’s Agreement can be quite specific about what "Done" means; but it should be silent on how it should be done. The Team owns its work – Team Members should not be micromanaged – but the Agreements can constrain the work in order to maintain quality. In other words, one shouldn’t micromanage the People, but it’s ok to micromanage the Product.

Professionals use a Standard of Care (SoC) + Professionals clarify Acceptance Criteria (AC) + Professionals make General Agreements (GA) + Professionals do their Due Diligence (DD) + Professionals work well with others’ Team Norms (TN) = Professionals meet a Definition of Done (DoD). DoD = (SoC + GA + TN + AC) + DD

The Team agreed that the Story would be time-boxed; that that they will be "Done" when a certain amount of time has passed - no matter what the actual result is at that time.

Cite This Term

"Done" ScrumDictionary.com. Accessed Jun 28, 2022. https://scrumdictionary.com/term/done/.