Definition of Done

The Definition of Done (DoD) in Scrum is a set of criteria or conditions that must be met for a product backlog item to be considered complete and ready for release. DoD ensures that the increment the development team delivers is of high quality and meets the agreed-upon standards. The DoD is defined collaboratively by the Scrum Team, including the Product Owner, Scrum Master, and Development Team, and typically includes criteria related to functionality, quality, and any other relevant aspects specific to the project or organization.

Characteristics

It should cover all aspects necessary to consider a product backlog item complete, including functionality, quality, performance, documentation, and any other relevant criteria.

The DoD should be consistent across all product backlog items and sprints, providing a standard benchmark for evaluating completion.

It should include quantifiable criteria or indicators that can be used to determine whether a product backlog item meets the definition of done.

The criteria in the DoD should be feasible to accomplish within the sprint timeframe and the capabilities of the Scrum Team.

The DoD is collaboratively defined and agreed upon by the Scrum Team, including the Product Owner, Scrum Master, and Development Team.

Example

Here’s an example of the Definition of Done for a software development project:

1. Code Complete: All code written, reviewed, and refactored as needed.
2. Unit Tests Passed: Automated unit tests were written and passed successfully.
3. Integration Tests Passed: Automated integration tests validate system components’ interaction.
4. User Acceptance Criteria Met: Implemented functionality satisfies user acceptance criteria.
5. Code Reviewed: Code reviewed by at least one other team member for readability and adherence to standards.
6. Documentation Updated: Necessary documentation updated to reflect changes made.
7. Performance Requirements Met: Implemented functionality meets defined performance criteria.
8. Regression Tests Passed: Regression tests were executed and passed successfully to avoid unintended side effects.
9. Product Owner Acceptance: The Product Owner reviews completed work and accepts it as meeting criteria and value expectations.
10. Demonstrated in Sprint Review: Completed work demonstrated during sprint review meeting for stakeholder feedback alignment with expectations
11. Ready for Release: Product backlog item prepared for release or deployment to the following environment in the pipeline