1. LandOffer
  2. Blog
  3. All articles
  4. Acceptance Criteria vs. Definition of Done: Agree on What Finished Means

Onboarding & Teamwork

Acceptance Criteria vs. Definition of Done: Agree on What Finished Means

One complete fictional duplicate-frame story distinguishes item behavior criteria, shared Increment quality measures, candidate-specific evidence and separate release authorization.

9 min readLandOffer team

Acceptance criteria describe the specific behavior required for a backlog item to be accepted. A Definition of Done describes the shared quality state of the product Increment that includes that work. Passing an item's acceptance checks does not establish that its integrated product Increment meets the Definition of Done, and neither status automatically records a separate release authorization.

To agree on what finished means, write both standards before assessing the work, connect each claim to evidence for a named version, and keep pending checks visible. This guide from LandOffer.ai uses one fictional feature to resolve a concrete “the tests pass, so it's done” disagreement without inventing software results or lowering the agreed quality threshold.

Teammates comparing a feature's behavior criteria with the shared product quality standard

Keep the two questions distinct

Acceptance criteria answer a question such as, “When I duplicate a storyboard frame, does the copy appear in the expected place with the required content?” They help the team agree on this change's intended result and boundaries.

The Definition of Done asks whether the resulting product Increment meets the agreed quality requirements. Does the integrated change preserve the product's required behavior, work with supported documents, and satisfy its applicable review and documentation requirements? The actual measures depend on the product and organizational standards.

Scrum.org's explanation of the distinction places acceptance criteria at the Product Backlog Item level and the Definition of Done at the Increment level. It describes acceptance criteria as a complementary practice rather than a required part of Scrum. Saying that a story “meets the DoD” is shorthand for its integration producing an Increment that conforms to that standard.

Avoid turning the distinction into “business versus technical.” An acceptance criterion can concern technical behavior, and a shared quality measure can concern a user's experience. Distinguish the scope of each standard and the evidence needed to meet it, rather than assigning one checklist to business and another to engineering.

Agree on the standards before interpreting the result

Use the applicable Definition of Done, including any organizational minimum. Do not let one item's deadline quietly replace it with a smaller checklist. When several Scrum Teams work on the same product, the shared product quality standard matters across their work, not only within one team's branch.

The 2020 Scrum Guide defines the Definition of Done as the quality state of the Increment, requires conformity to applicable organizational standards, and requires teams working on the same product to share the Definition of Done. Work that does not meet it cannot be counted as part of an Increment. That is more specific than marking a task complete because coding stopped.

Agree how to check each requirement and which version the result will cover. “Tests passed” is incomplete if nobody knows whether the tests ran on an isolated feature branch or on the integrated product candidate. Name the artifact, environment and applicable document scope so another teammate can see what the result actually covers.

Keep acceptance criteria clear and verifiable. Scrum Alliance's acceptance-criteria guidance recommends outcome-focused conditions that can be checked rather than prescribing every implementation detail. A criterion such as “duplicates correctly” leaves the team to discover the intended behavior after development. Specific examples make disagreements visible sooner.

Worked asset: one feature and two completed standards

The product, people, versions, evidence records and outcomes below are fictional teaching artifacts. No application was built or tested for this article. The records illustrate the claims a team would need to support; they are not runtime logs or proof that real software behaves this way.

The team maintains a desktop storyboard editor. Its new backlog item is: “As an editor, I want to duplicate the selected frame so I can reuse its content without changing the original.” Product Owner Isha and Developers Rowan and Mira agree on the item criteria. The team already uses shared Definition of Done version 4 for the product. Release coordinator Elin retains the separate operational release authorization described later.

They complete these item-specific acceptance criteria:

ID Agreed behavior for Duplicate frame Example that makes the boundary checkable
AC1 Duplicating one selected frame inserts one copy immediately after it With frames A, B, C and B selected, the order becomes A, B, B-copy, C
AC2 Copy includes the selected frame's image and caption content while leaving the original unchanged B's caption remains “Wide view”; changing the copy's caption to “Close view” does not change B
AC3 If no frame is selected, duplication is unavailable and creates no frame An empty selection does not create a new blank frame
AC4 One Undo reverses one duplication without removing or changing the original Undo restores A, B, C, including B's original image and caption

The item excludes duplicating an entire project, bulk selection and copying between projects. None of those features is implicitly accepted because a single-frame example passes. Excluding those features does not authorize weakening other applicable product requirements or the shared quality standard.

The relevant shared Definition of Done version 4 is also fully specified for this fictional product:

Shared requirement Evidence required for the resulting product Increment
Reviewed, integrated change Named review record resolved and change integrated into the same identified candidate used for the remaining checks
Product verification All affected item criteria checked on that integrated candidate, with the agreed regression suite passing and failures resolved
Supported-document compatibility Existing supported project files open, save and reopen without unintended content loss under the agreed compatibility cases
Keyboard interaction Changed commands remain usable through the product's documented keyboard path, including selection and Undo, under its agreed interaction checks
User-facing change documentation Current command behavior and limitations recorded in the versioned help/update notes included with the candidate

These are this team's shared product measures, not a universal minimum list or a claim of complete accessibility, security, or compatibility with every possible file. Their check records must identify the supported cases and results. A new risk may require additional work even when an old checklist was too narrow; the team should discuss and record that risk rather than hide it.

Use evidence labels that do not overstate coverage

An item can have all four acceptance checks passing on one build while integration checks are still pending on another. State that precisely. Do not copy the earlier green result into a later candidate without checking that the evidence applies.

Use “verified for this candidate and these cases,” “failed,” “pending,” or “not applicable with a recorded reason.” An unchecked box is not a pass. A proposed exception is not an approved change to the product's standard. A reviewer looking at a demo is not automatically evidence that every acceptance criterion was exercised.

Where a check finds an issue, describe the observed result and required repair. Avoid vague states such as “mostly done” when a specific shared requirement has not been met. A partially completed set of work can be visible without being counted as a Done Increment.

If new work changes the scope of an existing criterion, update the agreement with the people responsible for the product and implementation. Do not silently rewrite the criterion to match what happened to pass. Also avoid adding unrelated preferences after the fact and pretending they were always required.

A candidate evidence record retaining pending quality checks beside completed item checks

Worked asset: resolve “accepted” versus “Done”

At checkpoint 1 in the fictional case, Rowan says, “The four acceptance checks passed on branch build B17. Isha liked the walkthrough. Can we mark it Done?” Mira replies that the shared standard requires integrated verification and supported-document checks. Those have not occurred on B17, and the help notes are missing.

Isha clarifies: “The demonstrated behavior is the behavior I want. My walkthrough feedback does not replace the criteria records or our shared quality standard. Record B17's results, but do not count it as a Done Increment.” Rowan and Mira agree on a concrete next step: retain the unfinished status and list the remaining checks against a new integrated candidate.

They create this completed checkpoint record:

Evidence area Checkpoint 1: branch B17 Checkpoint 2: integrated candidate C18
Four item criteria Recorded as passing on branch B17 only All four rechecked and recorded as passing on C18
Review and integration Review complete; integration pending Review record resolved and change integrated into C18
Regression and supported documents Pending for the integrated product Agreed regression and compatibility cases recorded as passing on C18
Keyboard command path Pending for the integrated product Agreed selection, duplication and Undo interaction cases recorded as passing on C18
Included help/update notes Missing Still missing; shared requirement not met
Status conclusion Not Done Not Done; successful behavior and quality checks do not erase missing documentation

The table contains fictional check results, not an independently executed editor test. Its point is the scope of the status claim. C18 improves the evidence but still does not satisfy the completed Definition of Done. The team does not declare documentation optional because the coding work is over.

Rowan accepts preparing command notes that describe single-frame placement, independent caption edits, empty selection and one-step Undo. Mira accepts reviewing them against AC1–AC4 and the stated exclusions. They include the reviewed notes in candidate C19 and repeat the required verification on that candidate so earlier evidence is not silently assumed to cover a changed package.

At checkpoint 3, the fictional evidence index records the resolved review/integration record, four item checks, agreed regression and compatibility cases, keyboard interaction cases, and included reviewed notes, all against C19. Rowan and Mira record that the resulting product Increment meets shared Definition of Done version 4. Within this fictional record, every requirement in that definition has candidate-specific supporting evidence; none is pending or waived. This describes the example, not an actual software result.

Their completed disagreement-resolution note reads:

B17's item-specific behavior results did not establish integrated product quality. C18 supplied integrated check evidence but still lacked required user-facing documentation. C19 includes the reviewed documentation and the required verification for that candidate, so its resulting Increment meets Definition of Done version 4.

We have not granted operational release authorization or deployed C19. Elin still needs to decide the scheduled distribution under our local release process. That decision is separate from whether the Increment meets its quality standard. We will not change the quality status to “not Done” merely because distribution has not occurred, or call it “released” because quality checks are complete.

This resolution records three different states without using the word accepted to cover all of them. It also assigns a bounded repair and shows what evidence would close it. The article's written scenario does not establish that any actual storyboard editor, file format, or release process has been validated.

Keep release authorization separate without creating a quality loophole

A usable Increment and its distribution decision are related but different. The Scrum Guide says the Sprint Review is not a release gate; an Increment may be delivered before the Sprint ends. Do not turn “wait for the next review” into an invented Scrum requirement. Equally, a local release schedule does not make unfinished quality work releasable.

In the fictional case, Elin's scheduling decision does not stand in for missing testing or integration. Those were already required to meet the Definition of Done. If the team discovers a genuine quality failure in C19, it must investigate and update the status rather than insist the earlier Done record settles the new evidence.

For more practical teamwork guides, visit LandOffer.ai. Before calling your next item finished, identify its acceptance evidence, the shared quality evidence for the integrated candidate, and any separate release decision. If one is missing, name the gap rather than hiding it behind a single green status.

Sources and Further Reading