Definition Of Done (DOD)

The Definition Of Done (DOD) is a set of clear, measurable criteria that a feature, user story, or task must satisfy to be considered complete. It establishes a common quality standard for the entire development team. The DOD eliminates ambiguity around the term 'done' and ensures every deliverable meets technical, functional, and quality requirements before being integrated into the product.

Fundamentals

• Collective agreement established by the development team defining minimum quality standards
• Checklist applicable to each backlog item before final validation
• Guarantee of consistency and predictability in sprint deliveries
• Prevention mechanism for technical debt and quality defects

Benefits

• Eliminates misunderstandings between developers, testers, and Product Owner about completion status
• Significantly reduces technical debt by enforcing standards from development onwards
• Accelerates sprint reviews by providing objective validation criteria
• Improves predictability and velocity by standardizing the definition of 'done'
• Strengthens stakeholder confidence in delivery quality
• Facilitates continuous integration and deployment by ensuring code stability

Practical Example

Here's an example Definition Of Done for a team developing a modern web application:

# Definition Of Done - Yield Studio Team

## Code Criteria
- [ ] Code written following team conventions (ESLint/Prettier validated)
- [ ] Unit tests written with ≥ 80% coverage
- [ ] Integration tests for critical flows
- [ ] Code review approved by at least 1 peer
- [ ] No compilation or build warnings

## Functional Criteria
- [ ] User story acceptance criteria validated
- [ ] Exploratory manual testing performed
- [ ] Feature validated in staging environment
- [ ] User documentation updated if necessary

## Technical Criteria
- [ ] CI/CD pipeline passes successfully (build, tests, lint)
- [ ] No regression detected on existing features
- [ ] Performance verified (load time < 3s)
- [ ] WCAG 2.1 Level AA accessibility compliance
- [ ] Code merged into main branch

## Deployment Criteria
- [ ] Environment variables documented
- [ ] Database migrations tested
- [ ] Rollback plan documented if needed
- [ ] Monitoring and alerts configured

Implementation

1. Organize a workshop with the entire team (developers, testers, Product Owner) to co-create the initial DOD
2. Identify essential criteria by category: code, tests, documentation, deployment
3. Prioritize realistic criteria for your current context (avoid unattainable goals)
4. Formalize the DOD in an accessible document (wiki, README, project management tool)
5. Integrate DOD verification into your review and sprint validation process
6. Revisit the DOD during retrospectives to adjust it according to team and product evolution
7. Automate verifications as much as possible (linting, tests, code analysis) via CI/CD

Related Tools

• Jira, Azure DevOps, or Linear to define and track DOD criteria per user story
• GitHub Actions, GitLab CI, or CircleCI to automate technical verifications
• SonarQube or CodeClimate to measure code quality and coverage
• Checklist templates in Notion or Confluence to standardize manual verifications
• Miro or Mural for collaborative DOD creation/revision workshops

The Definition Of Done transforms ambiguity into clarity, reducing misunderstandings and quality defects. By establishing shared, measurable criteria, it enables teams to deliver with confidence, accelerate their velocity, and maintain consistent quality. It's a minimal investment that generates exponential benefits in terms of predictability, customer satisfaction, and technical debt reduction.