DoD (Definition Of Done) - Wa1ssy/Agiilsed-Tarkvaraarendus GitHub Wiki
Definition of Done (DoD)
The Definition of Done is a clear and shared understanding within a team of what it means for a task, user story, or product increment to be "done." It sets the quality and completeness standards that must be met before work is considered finished and ready to be delivered or released.
Why is it Important?
- Ensures consistency and quality across the team
- Prevents misunderstandings about whether a task is truly complete
- Helps avoid unfinished or buggy features going live
- Acts as a checklist to improve accountability and transparency
What Might Be Included in a Definition of Done?
Depending on the project and team, a DoD might include:
- Code is written, reviewed, and merged
- Tests (unit, integration) are written and passed
- No major bugs remain
- Documentation is updated
- Feature is deployed to a staging/production environment
- Accepted by the product owner
Example:
“A user story is done when:
- All acceptance criteria are met
- Code is peer-reviewed
- All automated tests pass
- No critical bugs remain
- Documentation is updated if needed
- Deployed to staging environment”