Definition of Done

The Definition of Done is used for creating a shared understanding of when a Product Backlog item can be considered done.
Read more

Definition of Done

The aim of agile iteration is to provide potentially releasable increment at the end of an iteration. To create such an increment the development team needs to have a shared understanding of how a Product Backlog item can be considered done. For this purpose the Definition of Done is used. DoD is the set of conditions that need to be fulfilled before the item is considered done and it can become a part of the increment. It also increases the transparency by providing shared understanding of what done means. The DoD can be evolving together with the product it is meant for.

What to consider for a Definition of Done

  • What should be included in DoD for the context of the work
  • Organization standards
  • Good practices for the domain of the development
  • Business or Functional requirements
  • Quality
  • Non-Functional Requirements

User Story DoD Example

  • The description of the User Story is fulfilled
  • Acceptance criteria are met and tested
  • Implementation is submitted to VCS (Version Control System, e.g. Git), where the review is done and the changes are accepted
  • Implementation is tested against acceptance criteria which are met
  • Necessary documentation is created/ updated

Sprint DoD Example

  • All done Sprint Backlog Items have been reviewed at Sprint Review
  • The increment is released
  • All undone Sprint Backlog items are moved into the Product Backlog and reprioritized

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.