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 definition of done can be evolving together with the product it is meant for.
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
• Mock screens for all the views are
provided
• The technical solution is provided
• Item is assigned to somebody
WHAT TO CONSIDER FOR A DOD
• Organization standards
• What should be included in DOD for the
context of the work
• Good practices for the domain of the
development
• Business or Functional requirements
• Quality
• Non-Functional Requirements
English 
Dutch