Skip to content

Definition of Done

DOD = Definition of Done

Code:

  • Code is reviewed and approved by at least one other team member.
  • Code is formatted consistently and follows established coding conventions.
  • Code is well*documented with comments and explanations.
  • Code passes all unit tests.

Documentation:

  • User documentation is complete and accurate.
  • Technical documentation is up-to-date and reflects the current state of the code.
  • Documentation is written in clear and concise language.

Testing:

  • All features are tested and verified.
  • Unit tests are written for all code components.
  • Integration tests are performed to ensure components work together correctly.
  • Regression tests are run to ensure that new changes do not break existing functionality.

Team Approval:

  • All team members agree that the work meets the agreed-upon DoD criteria.
  • The product owner signs off on the work.
  • The work is considered "done" and ready for deployment.

DOD stands for Definition of Done in agile development. It is a set of criteria that a team agrees to meet before declaring a product or feature as completed. The purpose of DOD is to avoid any confusion or misunderstanding between the development team and the stakeholders about what constitutes as done. For example, a DOD might include code quality, testing, documentation, and user feedback. You can learn more about DOD from these sources: