Understanding Definition of Done (DoD) and Acceptance Criteria (AC) in Scrum

"Pitfall" Description

When the Definition of Done (DoD) is unclear, misunderstandings arise not only from the concept itself but also from deeper underlying reasons.

Definition of Done and Acceptance Criteria

Possible Real‑World Example

During the daily stand‑up, Team Member A says: "Yesterday I completed item 1! Today I will start working on item 2." Two days later, the Product Owner approaches the team: "What happened to item 1? The flow is not what I expected…" This scenario repeats across many teams because they lack a clear Definition of Done and Acceptance Criteria.

Definition of Done (Excerpt from the Scrum Guide)

When a product backlog item or increment is described as "Done," everyone must understand what "Done" means. Although the interpretation may vary between Scrum teams, each team member must share a common understanding to ensure transparency. This is the Scrum Team’s Definition of Done used to assess whether a product increment is complete. The definition also guides the Development Team in deciding how many backlog items can be selected during Sprint Planning. Each Sprint aims to deliver a potentially shippable product increment that meets the current Definition of Done. The Development Team delivers a usable increment each Sprint, allowing the Product Owner to release it immediately. If the Definition of Done is an organizational convention, standard, or guideline, all Scrum Teams must adhere to it as a minimum standard. If not, the Development Team must create a suitable Definition of Done for the product. When multiple Scrum Teams collaborate on a product, all Development Teams must jointly create the Definition of Done. Each increment builds on all previous increments and is thoroughly tested to ensure the integrated product works. As the team matures, the Definition of Done expands to include stricter standards for higher quality. When a new definition is adopted, previously "Done" increments may reveal work that still needs to be completed. Every product or system should have a clear Definition of Done for the work performed on it.

From the Scrum Guide we can see:

The entire product shares a unified Definition of Done.

The Definition of Done is created by the Scrum Team and understood collectively.

Each team can tailor its own Definition of Done.

The Definition of Done can be expanded as the team matures.

Example of a Definition of Done (underlined parts represent the current product’s Definition of Done; additional non‑underlined items can be added as the team matures):

Acceptance Criteria

Acceptance Criteria (AC) apply to a single backlog item (e.g., a user story) and describe how to verify that the item meets the customer's requirements. AC serve the following purposes:

Define the boundaries of a user story or feature.

Help clarify customer requirements.

Enable the team, customer, and Product Owner to reach a shared understanding.

Provide a basis for generating test cases.

Example of Acceptance Criteria:

User Story:

As an online banking user, I want to see daily transaction details so that I clearly understand my account status after each transaction.

Acceptance Criteria:

Display transaction details for the most recent week by default.

Show the current account balance.

Allow viewing transaction details for a specified date range.

Definition of Done vs. Acceptance Criteria

Common Points

Both describe whether an item (feature, user story) is complete.

Both require team discussion and consensus.

Differences

The Definition of Done is generic and applies to every item; Acceptance Criteria are specific to an individual item.

The Definition of Done does not require customer involvement, whereas Acceptance Criteria often involve the customer or stakeholders.

Recommendations

Before the first Sprint, the team should establish an initial Definition of Done (and, if multiple teams work on the same product, a product‑level Definition of Done).

For each backlog item, discuss with the Product Owner (or customer) to define clear Acceptance Criteria.

If you have any suggestions or comments on the viewpoints presented, feel free to contact BoB.

BoB at c4at.cn