StackLift
All terms

Glossary

Definition of Done (DoD)

A shared checklist of quality standards every piece of work must meet before it counts as finished.

The definition of done (DoD) is a shared checklist of quality standards that all work must meet before a team calls it finished, such as code review, tests, security checks and deployment. In Scrum it is the commitment for the increment.

It applies to every item, unlike acceptance criteria, which are specific to one story. Work that does not meet it is not done and returns to the backlog.

A good one is short, checkable and reviewed at retrospectives. It is what separates a working demo from software ready for production.

Start in 60 seconds

Put this to work on your project.

Get an AI-assisted, architect-reviewed scope, cost range, and timeline. Free, no login.

The complete guide

Definition of Done (DoD): the complete guide

Updated November 18, 2026 ยท Published by , Founder, StackLift AI. Written with AI assistance; how we make content.

Short answer

A definition of done (DoD) is a shared checklist of quality standards that every piece of work must meet before the team calls it finished. It typically covers code review, testing, security checks, documentation and deployment. In Scrum, it is the formal commitment for the increment, and work that does not meet it is not done.

What is the definition of done?

The definition of done is a clear, shared statement of what finished means. It applies to all work, not one feature. Without it, one person's done means the code is written and another's means it is live, and the gap shows up as surprises late in the project.

In Scrum, the Scrum Guide describes the definition of done as the commitment for the increment. If an item does not meet it, it does not count as part of the increment and goes back to the backlog.

What does a definition of done include?

Each team writes its own, based on its product and risks. A typical software checklist looks like this.

Example definition of done for a web feature
AreaExample check
CodeMerged through a pull request with a code review
TestsAutomated tests added and passing in the pipeline
AcceptanceAll acceptance criteria verified
SecurityDependencies and secrets checked; no known critical issues
OperationsDeployed through CI/CD to a staging environment; monitoring in place
DocumentationUser-facing or API notes updated

Definition of done vs. acceptance criteria

Acceptance criteria describe what one story must do. The definition of done describes how every story must be built and checked. Both must be satisfied. A story can do exactly what was asked and still not be done if it was never tested or reviewed.

Do not confuse the definition of done with a sprint goal or a project deadline. The goal says what the team aims to achieve in a sprint. The definition of done says what quality that work must have.

How do you create a definition of done?

  1. Start from the standards the organization already requires, such as security or compliance steps.
  2. Ask the team what has gone wrong before: bugs found late, missed deployments, undocumented behavior.
  3. Turn each into a check that is yes or no.
  4. Keep it short enough to apply every time. A long list gets skipped.
  5. Agree on it with the team and the product owner, and post it where people work.
  6. Review it at retrospectives and tighten it as the team matures.

What goes wrong with a definition of done?

  • It exists on paper but is not applied, so items are marked done without the checks.
  • It is so strict the team cannot finish anything, so people work around it.
  • It is vague, such as well tested, so nobody can verify it.
  • It never changes, so it stops matching the product's risks.
  • Quality steps are pushed into a later hardening phase, which hides unfinished work and builds up technical debt.

Why it matters when you hire a delivery team

A visible definition of done lets you tell the difference between demo-ready and production-ready. Ask a partner to show theirs, and ask how it is enforced. If you are comparing what to expect from a team, see the production readiness checklist.

At StackLift, CI/CD, observability, security review and rollback are part of the plan from sprint one, and agents work on feature branches that are reviewed before they reach the default branch. The free estimate shows scope, timeline and team for your project.

How does the definition of done apply to AI-assisted code?

Code written or suggested by AI tools should meet the same standard as any other code. A good definition of done makes that explicit: a human reviews it, it passes automated tests, it is checked for security issues and secrets, and it is understood by the engineer who merges it.

The danger with generated code is that it looks complete. It compiles and the demo works, so it is tempting to call it done. The checklist is what separates a convincing prototype from software you can run in production, which is why teams add checks for tests, review and deployment rather than relying on appearance.

What are the levels of done?

Done is not a single moment. Work is finished at several levels, and each one has its own checks. Naming the levels stops arguments about whether something is really finished.

Levels of done
LevelWhat is finishedTypical checks
TaskOne piece of work, such as a function or a screenCode written, reviewed and merged
StoryA user-visible capabilityAcceptance criteria met, tests pass, accessibility checked
Sprint incrementEverything the team finished this sprintIntegrated, deployed to staging, demonstrated
ReleaseWhat reaches usersRelease notes, monitoring in place, rollback tested, approvals recorded

A user story is done when its acceptance criteria and the team's definition of done are both satisfied. A sprint is only done when the increment could be released.

What does a definition of done look like in practice?

Good definitions are short, checkable and written in plain words. Here is a sample for a web product team. Treat it as a starting point and adapt it to your risk.

  • Code reviewed by a second engineer, with required comments resolved.
  • Automated tests written or updated, and the full suite passes in CI/CD.
  • No new high-severity findings from security and dependency scans.
  • Works on the supported browsers and devices, and meets the agreed accessibility standard.
  • Error handling, logging and alerts are in place for new behavior.
  • Documentation or release notes updated where users or support will notice.
  • Deployed to staging, checked by the product owner and approved.
  • Configuration, secrets and database changes are scripted and repeatable.
  • Feature flag or rollback path exists for anything risky.

Notice that every line can be answered yes or no. Lines like "high quality" or "well tested" invite debate and should be turned into something concrete.

How does the definition of done change by type of project?

Extra checks for different products
Product typeAdded checks
Mobile appTested on target devices and OS versions; store review requirements met; crash reporting enabled
Data dashboardFigures reconciled with a trusted source; refresh schedule verified; access limited by role
IntegrationError and retry paths tested; failures visible to someone; credentials stored safely
AI featureEvaluation set passes; guardrails tested; cost per request checked; human fallback exists
Regulated productRequired evidence recorded, such as approvals and audit trails, for the rules that apply
Internal toolUsers trained or guided; permissions set; support owner named

For AI features see agent evaluation and AI guardrails, which supply many of the added checks.

Definition of ready vs. definition of done: what is the difference?

The two bookends of a work item are often confused. A definition of ready says when a story is clear enough to start. A definition of done says when it is finished well enough to count.

Ready and done compared
AspectDefinition of readyDefinition of done
Question it answersCan we start this?Can we call this finished?
Applies atThe start of workThe end of work
Typical itemsClear goal, acceptance criteria, estimate, dependencies knownReviewed, tested, secure, deployed, documented
OwnerProduct owner with the teamThe whole team
Risk if missingWork begins on vague ideasUnfinished work is called complete

Teams do not need both from day one. Many start with a definition of done, since it directly protects quality, and add a definition of ready if unclear stories keep slowing sprints.

How do you keep a definition of done useful over time?

  • Review it in each retrospective. Add a line when a defect escaped, remove one nobody follows.
  • Automate every item you can, so the pipeline enforces it instead of memory.
  • Keep it visible: on the board, in pull request templates and in the project space.
  • Tie it to real consequences. Work that misses it returns to the backlog and does not count as progress.
  • Separate team rules from client agreements, so both are clear.
  • Version it, so you can see when and why it changed.

How do you tell whether your definition of done is working?

The test is what reaches users. If work that is called done keeps returning for fixes, the definition is too weak or not being applied.

  • Defects found after release that a done check should have caught.
  • Rework: stories reopened after sign-off.
  • Demo surprises: features that do not work when shown.
  • Velocity that is steady, with no unfinished work piling up at the end of sprints.
  • Stakeholder confidence: product owners trust that done means releasable.
  • How much release preparation remains. If a hardening phase is needed after the sprints, done is too loose.

What does a definition of done mean for cost and timeline?

A stricter definition makes each story take a little longer, and it makes the project cost less overall, because defects, rework and late surprises are far more expensive than checks done on the day. The time shows up in tests, reviews and documentation, and the savings show up in fewer emergency fixes near release.

When you compare quotes, ask what done means in each. Two prices can look different because one includes testing, security review and deployment and the other leaves them out. Pricing by deliverable complexity, as with story points, only compares fairly when done is defined. Scope your own project with the free estimate, and use the software estimation playbook to compare offers.

How should a definition of done appear in a client agreement?

When one company builds software for another, done decides when work is accepted and when payment is due. If it is left vague, each side can claim a different meaning. Putting it in writing protects both.

  • Attach the definition of done to the statement of work, or reference the shared project space where it lives.
  • Say who accepts each level of done, and how quickly they must respond.
  • Separate the team-wide definition from the acceptance criteria of each story.
  • State what evidence you will see, such as test results, release notes and approvals.
  • Agree how changes to the definition are proposed and approved, so scope stays visible, as in a change request.
  • Make sure the definition covers deployment and handover, not just code written.

At StackLift, approvals, releases and invoices are visible in the client portal, and the estimate, proposal and project share one baseline, so what counts as finished is not a surprise.

Which tools help enforce a definition of done?

Tool types
Tool typeExamplesWhat it enforces
Pull request templatesGitHub, GitLab, BitbucketA checklist shown on every change
Branch protectionThe same platformsNo merge without review and passing checks
CI/CD pipelinesGitHub Actions, GitLab CI, CircleCITests, scans and build on every change
Code quality scannersSonarQube, Dependabot, SnykCode smells and vulnerable packages
Project boardsJira, Linear, Azure DevOps, ClickUpColumns that mean done only when checks pass
MonitoringSentry, Datadog, GrafanaProof that the release is healthy

Automate what you can and keep the human checks few and meaningful.

Questions people ask

What is the difference between done and done done?

It is informal wording for the gap between a feature that works on a developer's machine and one that is tested, reviewed and ready to release. A good definition of done closes that gap.

Who owns the definition of done?

The team owns and applies it. In Scrum, if the organization has a standard, the team follows at least that. The product owner and stakeholders help shape it.

Can the definition of done change?

Yes, and it should as the team learns. Change it deliberately, usually at a retrospective, and apply the new version to future work.

Is the definition of done only for Scrum?

No. The idea is useful in any approach. Scrum names it formally, but any team can benefit from a shared standard for finished work.

What happens when work does not meet it?

It is not counted as done. It returns to the backlog or stays in progress, and it is not released or presented as complete.

Who writes the definition of done?

The team that does the work writes it together with the product owner, and the client agrees to it. It should reflect your quality and compliance needs, not just developer preferences.

Is the definition of done only for Scrum?

No. Any team that wants a shared standard for finished work can use one. Kanban teams and teams without a named method use it just as well.

Can the definition of done be different for each story?

The team-wide definition applies to every story. Story-specific needs belong in acceptance criteria. You may keep a short list of extra checks for unusual items, such as a security-sensitive change.

Sources

Sources and further reading

The standards, rules, research and official documentation this page draws on.