ScrumTool
Agile6 min read·May 16, 2026

Definition of Done Checklist: 40+ Items for Agile Teams (By Team Type)

A comprehensive definition of done checklist with 40+ items organized by team type: startup, enterprise, mobile, API, and data teams. Use it to build your team's starting DoD.

A definition of done checklist is only useful if your team actually uses it. Start with the items that apply to your context and add more as the team matures. Here are 40+ items organized by team type.

Universal (every software team)

  • Code reviewed by at least one peer
  • All existing automated tests pass
  • No new compiler or linter errors introduced
  • Acceptance criteria verified by the developer
  • Feature tested in a non-local environment
  • No hardcoded secrets or credentials in code
  • Story marked as done in the project tool

For web application teams

  • Feature works in supported browsers (Chrome, Firefox, Safari, Edge)
  • Responsive layout verified on mobile viewport
  • Accessibility: keyboard navigation works, ARIA labels present
  • No console errors in the browser
  • Page load does not regress Core Web Vitals by more than 10%
  • New UI strings are localized (if the app is internationalized)

For API/backend teams

  • API contract documented (OpenAPI or equivalent)
  • Error responses follow the team's error format
  • Rate limiting and authentication applied to new endpoints
  • Logging covers key success and failure paths
  • Database migrations are reversible
  • No N+1 query patterns introduced

For mobile teams

  • Feature tested on minimum supported OS version
  • No memory leaks detected in profiler
  • Feature tested on physical device (not only simulator)
  • App size increase is within acceptable limits
  • Crash-free rate does not regress

For data and ML teams

  • Data pipeline tested with production-scale sample
  • Model accuracy meets agreed threshold
  • Experiment tracked in the team's experiment registry
  • Data schema changes are backward compatible
  • PII handling reviewed and approved

For enterprise/regulated teams

  • Security review completed for any auth or data change
  • Compliance checklist signed off by the relevant team
  • Change management ticket raised if required
  • Performance test run if feature affects high-traffic paths
  • Architecture decision record (ADR) written for major technical decisions

How to use this list

Pick the items that your team can honestly commit to today. Start small — five to eight items. Add more in retrospectives as the team builds capacity. Use our free definition of done generator to create a tailored DoD for your team type automatically.

Related reading: Definition of done guide · Definition of ready vs done · DoD vs acceptance criteria.

Run better ceremonies starting today.

Retro boards, planning poker, and async standup — with AI built in. Free to start, no credit card required.

Start for freearrow_forward

Related reading