Definition of Done

According to scrum Definition of done (DOD) is a shared understanding of expectations that the current sprint or increment must meet in order to be released to the users. It is an agreed upon the set of items that have to be completed before a user story or a project can be considered/terminated. A set of acceptance criteria that user story has to fulfill is deemed to be done from the list of user stories. Only when user stories qualify as a done, it is considered to be launched as an update in the product.

The difference between the user story whereas all acceptance criteria is applicable for the specific user story. Acceptance criteria of each user story is different based on the requirement of the user story. In other words, DOD and acceptance criteria both should be met in order to complete the user story requirement.

Features of Definition of Done:

Most of the companies have their own definition of done according to their convenience and collaborationist typical criteria that have to be fulfilled for the product to be considered are listed below.

  1. The code should be peer reviewed
  2. Code is check in
  3. Code is deployed to the test environment
  4. Regression test should be passed be feature/code
  5. The code should give some testing
  6. Documentation of code
  7. Help documentation should be updated
  8. The stakeholders approve the features.

Finally the goal for definition of done is to build a common understanding within the team about quality and completeness. Use as a checklist that user stories or checked against. Ensure that the increment is shipped at the end of each sprint has high quality and that quality is well understood by all involved.