Skip to content

The Scrum Definition of Done

Step 9 of 18

The Scrum Definition of Done: Quality, Increments, and Release

Introduction

The Scrum Definition of Done gives a team and its stakeholders a shared way to tell whether an Increment meets the product’s quality standard. If checkout code works but still needs an agreed security scan, the team can inspect what remains without counting the feature as part of the usable product.

This PSM I lesson covers Done in the Understanding and Applying the Scrum Framework focus area. You will apply the Definition of Done when planning work, integrating changes from several teams, and deciding what can be presented at the Sprint Review or delivered to users.

Learning objectives

  • Define Done and the Definition of Done, and explain why the DoD is the commitment of the Increment.
  • Explain who creates, applies and improves the Definition of Done.
  • Apply the rules for organisational standards and for several Scrum Teams on one product.
  • Explain how an incomplete Definition of Done produces technical debt and reduces transparency.
  • Distinguish between Done, Sprint Backlog completion and release.

1. What "Done" means

The Definition of Done (DoD) describes the quality conditions an Increment must meet. It is the commitment attached to the Increment. Compare it with the Product Goal and Sprint Goal in Scrum artifacts and their commitments.

Use the standard during Sprint Planning to judge what work can fit, and again as the work is integrated. Only work that meets the standard can be part of an Increment. If an item remains incomplete at the end of the Sprint, it returns to the Product Backlog for future consideration. It cannot be released or presented at the Sprint Review. The team can still explain the gap and what it learned.

Example: a Definition of Done for a web shop

A Scrum Team building a web shop agrees on these product quality checks. Each applies to the relevant change in the integrated product:

  1. Code is reviewed by at least one other Developer.
  2. Unit tests pass and coverage of new code is at least 80%.
  3. Automated integration and accessibility checks pass.
  4. Security scan reports no high-severity findings.
  5. Documentation for support staff is updated.
  6. The change is deployed to staging and its agreed smoke tests pass.

The Developers verify the applicable checks before counting work as part of the Increment. These example checks reflect the needs of this product. Scrum does not prescribe a coverage percentage, a particular staging setup, or a Product Owner sign-off.

Example: acceptance criteria and the Definition of Done

Suppose a web shop adds an order cancellation screen. One acceptance criterion says the customer must see the refund amount before confirming. A tester can verify that behaviour by cancelling a test order. The product’s Definition of Done also calls for accessibility checks, regression tests, and a security scan. Even if the amount appears correctly, the change cannot be included in the Increment while those checks are missing.

The reverse can happen too. A build can pass the shared checks and still omit a promised refund detail. The Product Owner and Developers can clarify or split the selected item if that preserves the Sprint Goal. They should make the remaining work visible and verify that any part they keep is usable. A smaller change can be Done when it meets the same quality standard.

A team might also use a refinement checklist to identify dependencies before Sprint Planning. That checklist helps a selection decision. The Scrum Guide does not define a separate Definition of Ready, and a checklist for refinement does not determine when work is part of an Increment.

2. Who creates and applies the Definition of Done

The guide gives three situations:

  1. The organization has a Definition of Done. The team treats that standard as a minimum and can agree on stricter criteria that the product needs.
  2. The organization has no standard. The Scrum Team defines a quality standard suitable for the product.
  3. Several teams share one product. They agree on and follow one product-level Definition of Done.

The Developers apply the Definition of Done as they build and verify the Increment. The Product Owner and Scrum Master can help the team understand risks and improve its standard. The team respects any organizational minimum.

Comparison: who owns what quality decision

Situation Who defines the Definition of Done Who applies it
Organisational standard exists The organisation sets the minimum; the Scrum Team may add to it Developers
No standard exists The Scrum Team Developers
Several teams on one product All teams together define one shared DoD Developers of every team
Different products in one company Each product's Scrum Team (or the organisational minimum) Developers

Can the Definition of Done change?

The team can improve its Definition of Done as the product or its practices change. At the Retrospective, for example, it might agree to add an automated check for a recurring defect. Scrum sets no separate date for revising the standard. Maintain or improve quality during the Sprint, and do not weaken checks to meet a deadline.

3. Quality, technical debt and transparency

Build quality into the work as it is integrated. Technical debt describes choices or shortcuts that make future change more costly or risky. Missing tests can create that cost, but defects or unfinished work are not automatically technical debt. Inspect what the gap will cost before deciding how to address it.

How a weak DoD hurts:

  • Transparency declines. Stakeholders believe a feature is finished when it is not.
  • Forecasts become unreliable. The hidden remaining work arrives later, as bugs or a "hardening" phase.
  • Value is delayed. The Product Owner cannot release an Increment that is not usable.

Scrum has no "hardening Sprint", "stabilisation Sprint" or "testing Sprint", because all the work necessary for a usable Increment belongs to the Sprint in which the item is built.

Example: the cost of deferring integration tests

A telecom team counts items as complete when code is merged. Five Sprints later, integration tests reveal that its checkout and billing services disagree on how to handle refunds. The Scrum Team adds a shared contract test to its Definition of Done and makes the test environment available during each Sprint. At first, it selects fewer items while building the test. It then tracks escaped defects and time spent on rework to see whether the new practice helps.

Make quality visible during the Sprint

Suppose the refund contract test fails on day six. The Developers record the failed check alongside the item and inspect how it affects the Sprint Goal. If a fix fits, they revise the plan and retest the integrated product. If the selected scope needs to change, they discuss it with the Product Owner. The current usable version remains available while they decide what to do with the incomplete item.

The Scrum Team can also look for patterns across Sprints. If the same test fails late three times, running it earlier might reveal the problem when it is easier to fix. At the Retrospective, agree when to run it and what evidence would show that earlier testing helped. For example, compare the time between the first failed check and a verified fix.

4. Several teams, one Definition of Done

When several teams share a product, they use the same Definition of Done so the integrated Increment can be inspected consistently. They also share the Product Goal, Product Backlog, and Product Owner.

A shared standard gives everyone the same basis for inspecting the combined product. A team can add checks for component-specific risks while still meeting the common standard for the Increment.

Example: three teams, one mobile app

Three Scrum Teams develop the iOS app, the Android app and the backend API of a food-delivery product. They agree on a shared Definition of Done: automated tests pass, code is reviewed, API contract tests pass against a shared environment, accessibility rules are checked and release notes are updated. The backend team also adds a performance test because its component is on the critical path. At the Sprint Review, stakeholders can inspect the combined product. In this example, the teams choose to run a joint Review. A shared Definition of Done applies regardless of how they coordinate the event.

5. Done, Sprint end and release

Three different states are easy to confuse:

State Meaning Who decides
Item is Done The item meets the Definition of Done The Developers apply the DoD; the Scrum Team understands it
Sprint is complete The Sprint's timebox has ended The calendar (fixed-length)
Increment is released The Increment is delivered to users The organization’s release process determines who authorizes delivery

An Increment may be delivered before the Sprint Review once it meets the Definition of Done and the organization’s release requirements are met. The Review is an opportunity to inspect the Sprint outcome. For the distinction between product inspection and process improvement, see the Sprint Review and Retrospective.

What if the DoD is not satisfied when the Sprint ends?

The item is not Done. It does not count in the Increment, is not demonstrated as Done at the Sprint Review, and returns to the Product Backlog. The Product Owner reorders it. It may or may not be selected in the next Sprint. Re-estimating it is a good idea because new knowledge exists.

6. Worked example: the unfinished documentation

Statement. Day 10 of a two-week Sprint. Item X is working, tested and reviewed, but the user documentation required by the Definition of Done has not been written. The Product Owner wants to release the feature this afternoon because a customer is waiting, and asks the Scrum Master to declare it Done. The Developers say they can write the documentation next Sprint. What should the Scrum Master do?

Reasoning, step by step.

  1. Does the item meet the Definition of Done? No, the documentation is missing.
  2. Can it be part of the Increment? No. Work that does not meet the DoD is not part of the Increment.
  3. Who may change the DoD? The Scrum Team, usually by reflecting in the Retrospective, not on the last day to make an item fit.
  4. Can the Developers still finish it in the Sprint? Possibly, if the documentation takes a few hours. The Developers assess what they can finish while protecting the Sprint Goal and quality.
  5. What if they cannot finish? The item returns to the Product Backlog and is not presented as Done at the Sprint Review.

Solution. The Scrum Master helps the Developers decide whether the documentation can be completed before the end of the Sprint. If the documentation is complete and all other criteria still hold, the Increment can include the item and follow the organization’s release process. If not, it goes back to the Product Backlog. The Scrum Master helps the team raise the recurring pressure at the Retrospective and consider an improvement, such as writing documentation alongside the feature.

Why the other choices are worse. Declaring it Done lies about the state of the Increment and breaks transparency. Releasing it "with a note" accepts a known quality gap. Removing the documentation from the DoD for this item alone makes the DoD meaningless. Shifting the documentation to a "documentation Sprint" is not a Scrum practice.

7. Common pitfalls and exam tips

  • The Definition of Done is the commitment for the Increment. It describes quality. The Sprint Goal and Product Goal describe objectives.
  • The Developers conform to the Definition of Done. The Scrum Master does not enforce quality by inspection; the Scrum Master helps the team to understand and improve it.
  • Use the agreed quality checks. Developers verify the Increment against the Definition of Done. Stakeholder feedback can guide what the team changes next.
  • Several teams, one product: one Definition of Done, mutually defined.
  • Organisational standard is a minimum that the Scrum Team can extend, not replace with a weaker version.
  • No "hardening" or "release" Sprint. All work for a usable Increment happens in the Sprint.
  • Undone work does not show at the Review. It returns to the Product Backlog.
  • Increasing quality is a Retrospective topic. The DoD is one of the explicit things the Retrospective inspects.
  • Exam tip: when two answers differ only by "lower the DoD to meet the date" versus "keep the DoD and adjust scope", choose the second. The Scrum Guide protects quality; scope is the variable.

8. Mini case study

Situation. Two Scrum Teams share one banking product and one Product Backlog. Team A's Definition of Done includes automated regression tests and a security scan. Team B's includes unit tests only, because "our area is low risk". The integrated Increment fails in production twice in a month. The Product Owner suggests that Team A removes the security scan to keep up with Team B's pace. The company has an organisational standard that requires a security scan for any customer-facing change.

Questions. (1) What rule is violated? (2) What would you advise?

Commented solution.

  1. Violated rules: The two teams work on the same product and must mutually define and comply with the same Definition of Done. In addition, the organisational standard is a minimum that all Scrum Teams must follow, so Team B's definition is below it.
  2. Removing Team A’s scan would violate the organizational minimum and leave the affected customer-facing changes without the required check.
  3. Advice: Have both teams agree on a common Definition of Done that includes the required security scan and shared regression tests. Where a component has extra risks, add appropriate checks and make them visible. Inspect escaped defects and cycle time after several Sprints to learn how the changes affect delivery.

Why this matters. If the Definition of Done is not shared, the Increment is only as good as the weakest team's work, and stakeholders have no reliable picture of the product.

Key terms

  • Definition of Done (DoD): agreed conditions that show whether the Increment meets the product’s quality standard.
  • Done: state of a Product Backlog item that meets the Definition of Done.
  • Increment: usable stepping stone toward the Product Goal; created when an item meets the DoD.
  • Technical debt: accumulated shortcuts that make future change harder (a common term, not defined in the Guide).
  • Organisational standard: minimum quality criteria set by the organisation for all Scrum Teams.
  • Release: delivery of an Increment to users under the applicable release process.

Summary checklist

  • The Definition of Done is the commitment of the Increment and creates transparency.
  • Work not meeting the DoD is not part of the Increment and returns to the Product Backlog.
  • The Developers must conform to the DoD; the Scrum Team creates it unless an organisational standard exists.
  • An organisational standard is a minimum; teams may add to it.
  • Several Scrum Teams on one product share one Definition of Done.
  • The DoD evolves, notably through the Sprint Retrospective.
  • There is no hardening Sprint; quality is built in during the Sprint.
  • I can distinguish a Done Increment, its delivery to users, and the Sprint Review.

Sources