It’s a Planv1.12.0

Definition of Done: Write a Checklist Your Team Can Verify

Learn how to write a Definition of Done your team can verify: separate it from acceptance criteria, readiness and release, turn vague items into observable checks with evidence, and handle work that does not meet the standard.

Andrii PoluosmakUpdated 10 min read

A definition of done should let two people inspect the same work and reach the same conclusion. Before moving work to Done, agree on the quality conditions it must meet and how you will verify them. Keep the supporting evidence with the work.

Read your current checklist as someone who did not perform the work. Decide what you would inspect and which result would count as a pass. Agree with your team on what to do if a check fails.

What a Definition of Done commits your team to

The 2020 Scrum Guide defines the Definition of Done as the formal description of an Increment's state when it meets the product's required quality measures. Write your standard around the result you need to inspect.

The same guide requires an Increment to be usable and to work with previous Increments. Include the integration and verification work needed to reach that state. Check the combined product before declaring an isolated change complete.

For a Scrum definition of done, begin with the organizational standard. The Scrum Guide requires teams to follow that standard as a minimum; where none exists, the Scrum Team creates a product-appropriate definition. Involve the people responsible for those requirements before agreeing on local wording.

The Scrum Guide also requires multiple Scrum Teams working on one product to define and comply with the same Definition of Done. Agree across those teams on how you will verify the combined result. Resolve product-level quality requirements before relying on separate team checklists.

The Scrum Guide makes Developers accountable for instilling quality by adhering to the Definition of Done. Agree on who will perform particular checks. Keep that shared accountability in place even if you assign a final reviewer; the Scrum Master should not carry the quality commitment alone.

Definition of Done vs acceptance criteria, readiness, and release

Give four decisions their own place in your working agreement: whether you can start the work, whether you have met its specific requirements, whether the Increment meets the quality standard, and whether you have released it.

Acceptance criteria describe the particular item

Scrum Alliance distinguishes acceptance criteria, which are unique to each Product Backlog item, from the Definition of Done that applies across the work. Keep item-specific behavior with the item and shared quality conditions in the common definition.

To resolve definition of done vs acceptance criteria, identify what the particular change must do and which quality conditions the resulting Increment must meet. Check both before treating the work as complete. A successful demonstration of the requested behavior still leaves you responsible for the required quality verification.

Readiness concerns starting work

Scrum Alliance describes a Definition of Ready as an optional tool outside Scrum, while the Definition of Done is part of Scrum. If your team uses a readiness checklist, keep it separate from completion checks.

Use readiness discussions to decide whether you can take work on. Use the completion standard to assess the result. Leave preparation items off the done list unless they also express a required completion condition.

Done does not mean released

The Scrum Guide allows an Increment to be delivered before Sprint end and states that the Sprint Review is not a gate to releasing value. Record completion and release as separate decisions.

Keep any release authorization explicit. Say whether you mean the Increment meets the quality standard or you have released it. You do not need to wait for the Sprint Review to declare completed work Done.

Turn vague wording into observable checks

Chuck Suscheck's Scrum.org explanation recommends actionable, binary Definition of Done items. Write conditions that someone can inspect and mark as met or unmet.

Use four fields for each proposed check: the criterion, its pass condition, the evidence location, and the person verifying it. Adapt the format to your team's work.

Name the condition you need

Choose a line from your existing checklist. Identify the quality concern it addresses, then specify what must be true about the result.

Remove adjectives that leave the decision to personal interpretation. For testing, name the required checks and their expected result. For review, identify the review requirement. For documentation, specify which information must reflect the change.

Keep detailed procedures in the supporting guidance and point to them from the checklist. Split unrelated decisions into separate checks so you cannot tick a condition after completing only part of it.

Decide what counts as a pass

Agree on the pass condition before checking the work. Choose applicable tests, review requirements, and quality limits from your product's required standards. Avoid adopting a coverage percentage or performance target to make the checklist look measurable.

Agree on how to decide whether a condition applies. Record the reason for an exemption against that condition, and distinguish an inapplicable requirement from a failed one.

Read the proposed wording on your own, then compare interpretations with the team. Resolve differences about what to inspect or accept before using the check.

Identify evidence for the current work

Decide where the verifier can inspect the result. Keep the relevant build or change identifier alongside the evidence so they can confirm which work it covers. Checking that a file exists is not enough.

Keep the standard and supporting instructions on one shared page. In It's a Plan, a shared Docs page can hold the agreement beside the issues it describes. Use that common definition across issues.

A four-column worksheet provides blank fields for the criterion, pass condition, evidence location, and verifier, with one pass-condition field highlighted.

Build a Definition of Done checklist from your requirements

Build an agile definition of done from the standards your product must meet. Work through the prompts below and fill in the product-specific conditions before adopting the checklist.

As you review definition of done examples, choose conditions because your product needs them. Avoid copying thresholds or aiming for a particular checklist length. Ask for enough evidence to verify each condition.

Establish the shared baseline

  • Identify the organizational quality requirements that apply to the Increment.
  • Map each requirement to an observable check and its supporting instructions.
  • Confirm that every team working on the product uses the shared Definition of Done.

Keep the original requirement traceable as you simplify its wording. Resolve conflicts between a proposed local rule and the organizational minimum before using the checklist. Retain the harder requirement until you resolve the conflict.

Specify the checks for the resulting Increment

  • Name the required verification checks and record the result needed to pass each one.
  • Include the verification needed to establish that the change works with previous Increments.
  • Identify required reviews and the evidence that their conditions were satisfied.
  • Identify required documentation updates and where their completion can be inspected.

Replace these broad categories with the completion conditions your team has agreed to check. Spell out what you mean by sufficient testing or review so the verifier can make a decision without guessing.

Make completion inspectable

  • Record where the evidence for each condition will be kept.
  • Identify the build or change covered by that evidence.
  • Agree who verifies each condition before work is declared Done.
  • Record failed checks and unresolved requirements without marking them complete.

Work through the finished checklist against a real backlog item. Identify what each check would require without marking it as passed. Clarify the evidence location and pass condition wherever you cannot yet make that decision.

Agile Alliance describes an explicit Definition of Done that the team can point to as a sign of use. Keep the agreed version accessible during planning and verification, where people can consult it without reconstructing meeting notes.

Handle work that does not meet the standard

The Scrum Guide states that work cannot be part of an Increment unless it meets the Definition of Done. Record the failed condition and describe the remaining work. Keep its status consistent with that result.

The guide also says that a Product Backlog item that fails the Definition of Done cannot be released or presented at the Sprint Review and returns to the Product Backlog for future consideration. Reconsider unfinished work there before selecting it for another Sprint.

If a required check fails:

  1. Record the failed condition. Name the unmet requirement and the current result.
  2. Describe what remains. Specify the missing verification, correction, or integration work.
  3. Keep its status truthful. Leave the condition unticked while you resolve it.
  4. Reconsider the work in planning. Decide what to take on while keeping unfinished work distinct from a completed Increment.

The Scrum Guide states that quality does not decrease during the Sprint. Keep the agreed minimum intact if time runs short. Renegotiate what work to attempt while retaining the completion standard.

Make dependencies part of the completion decision

The Scrum Guide requires Increments to work together. Check the combined result against the shared standard before treating separate completed tasks as proof of finished integration.

Name the unresolved dependency and the verification it prevents. Record what you have implemented and what you have verified. Keep the remaining requirement attached to the work so another person can see why you have not declared it Done.

At the Sprint Review, make the remaining work and its planning implications clear. Avoid presenting the unfinished item as a completed Increment.

Review the checklist when it stops resolving decisions

The Scrum Guide includes inspecting the Definition of Done in the Sprint Retrospective. Bring failed checks and disagreements to the discussion. Decide whether to clarify the wording, ask for different evidence, or add a missing quality condition.

In a survey published as a 2022 Journal of Systems and Software paper, 93% of 137 practitioners surveyed in 2020 perceived the Definition of Done as at least valuable. Ask your team which completion decisions its standard helps them make and which ones they still have to negotiate.

Start with a check that people interpreted in different ways. Ask what each person inspected and why their answers diverged. Revise the condition or its instructions so the next verifier can use it without needing to recall the discussion.

For defects, establish whether someone skipped a required check, whether the check failed, or whether the standard omitted a relevant condition. Address that gap. Before adding a checkbox, agree on how someone will verify it.

After a dependency or product change exposes a new requirement, decide which work needs the check and how you will verify it. Involve the teams that must agree on the wording. Retain the organizational minimum as you clarify product-specific conditions.

Record the revised agreement and tell the people who use it what changed. At the next retrospective, review how they used it to make completion decisions and whether they could find the instructions they needed.

Agree on the evidence before marking work Done

Review your team's current completion checklist together. Choose an ambiguous line, write its observable pass condition, and agree where the evidence will live. Repeat until someone who did not perform the work can inspect each required condition.

Keep the shared agreement in a place the team already consults. If you use It's a Plan, put the revised standard in Docs beside the relevant issues. Before the next move to Done, check the current work against that standard and leave any unmet condition visibly unfinished.

Key takeaway

The Definition of Done describes the quality state of a usable Increment, not just the end of a task list. Acceptance criteria cover a particular backlog item, and the shared quality standard still applies. Give each check an observable pass condition and an evidence location, and keep unfinished work visible instead of changing the standard to make it count as Done.

Andrii Poluosmak

Founder

Andrii founded It’s a Plan and leads its product and roadmap, from the open-source edition to Pro for teams. He works with the project’s contributors and the teams that run It’s a Plan.

All posts by Andrii Poluosmak

Put your next project on the board.

The open-source issue tracker you host yourself.