Skip to navigation
Team Documents

Definition of Done

The DOD (Definition of Done) provides a clear and shared understanding of what “Done” means for each user story or product backlog item. This eliminates ambiguity and ensures everyone is on the same page.

It sets quality standards that must be met before a piece of work is considered complete.

  1. CODE DEVELOPMENT

  • Code has been written and peer-reviewed. Minimum two persons must do the peer review. Avoid self-review and self-approve. (All review comments are resolved and closed)
  • Code adheres to coding standards and guidelines (zero Lint errors or warnings)
  • All changes committed to the version control system.
  • Unit tests have been written and passed by developers
  • Code coverage is above 80%

  1. Testing

  • Functional tests have been conducted and no critical bugs are open
  • Integration tests have been run and no critical bugs are open
  • Regression tests have been run and no critical bugs are open
  • Medium or Low bugs can remain open as long as the PO or business needs does not hinder functionality

  1. Documentation

  • Code is properly commented
  • Documentation should be created or updated as needed
  • Test Evidence must be attached to the product backlog item (PBI) by QA

  1. Integration
  • Increment is integrated into the main codebase without conflicts
  • Build is successful
  • All unit test must be passed during integration