Increment & Definition of Done

PSM I PSM I · Artifacts & Commitments

By Abu Anns · Last updated 20 November 2026Exam version: PSM I (Scrum Guide 2020)

An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable. Multiple Increments may be created within a Sprint, and the sum of the Increments is presented at the Sprint Review, supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint — the Sprint Review should never be considered a gate to releasing value. This is the definition the exam tests: an Increment is concrete, additive, verified, and usable. Work that is not usable is not an Increment, however much effort went into it.

The key rule about the Increment is what counts as part of it: work cannot be considered part of an Increment unless it meets the Definition of Done. This is a bright line. A feature that is coded but not tested, or tested but not integrated, does not meet the Definition of Done and therefore is not part of the Increment — it is unfinished work, however close it looks. The Definition of Done is the commitment for the Increment: it is a formal description of the state of the Increment when it meets the quality measures required for the product. The moment a Product Backlog item meets the Definition of Done, an Increment is born. That moment matters because it is when value becomes real — before it, the work is an investment with no return; after it, the product has genuinely improved.

Where does the Definition of Done come from? If the Definition of Done for an Increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. The Developers are required to conform to the Definition of Done. And if there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done — otherwise each team would have a different idea of what finished means, and the Increments would not reliably work together. The exam tests all three of these rules, often with scenarios where teams have different standards or where an organization has no standard at all.

Definition of Done vs acceptance criteria

Candidates often confuse the Definition of Done with acceptance criteria, and the exam exploits this. Acceptance criteria belong to individual Product Backlog items: they describe what this specific item must do to satisfy its need — for example, a login feature must accept valid credentials and reject invalid ones. The Definition of Done applies to the Increment as a whole: it describes the quality standard that every item must meet — for example, code reviewed, tested, integrated, and documented. Acceptance criteria vary from item to item; the Definition of Done is the same across the Increment. An item can meet its acceptance criteria and still not be Done if it fails the Definition of Done — for instance, a feature that works correctly but has no tests and no review. Both must be satisfied for the item to count as part of the Increment.

Worked scenario

A Scrum Team finishes a Sprint with four items. Three meet the Definition of Done: coded, tested, reviewed, integrated, documented. The fourth works in a demo but has no automated tests and was never reviewed. The team presents three items as the Increment at the Sprint Review; the fourth is not part of the Increment, and returns to the Product Backlog for completion in a future Sprint. A Product Owner who wants to count the fourth item as done because it works in the demo is wrong: the Definition of Done is the standard, and it is not negotiable within a Sprint. The team's transparency here — presenting three items, not four — is exactly what empiricism requires: stakeholders see the true state of the product, and the next Sprint's planning is based on reality, not on wishful thinking.

Multiple Increments and release

A Sprint can produce more than one Increment. As the Developers complete items that meet the Definition of Done, each one becomes part of the growing Increment — and the team may choose to deliver value to stakeholders before the Sprint ends. The sum of the Increments is presented at the Sprint Review, but delivery does not wait for the Review: the Guide is explicit that the Review should never be considered a gate to releasing value. This matters in practice because it separates the rhythm of delivery from the rhythm of inspection. A team can release a valuable improvement on day five of a ten-day Sprint and still inspect the whole Sprint's outcome at the Review on day ten. Organizations that turn the Review into a release approval board delay value and contradict the empirical approach — the Increment is inspected so the team can adapt, not so stakeholders can grant permission.

Strengthening the Definition of Done

The Definition of Done is not fixed forever. As a team matures, its standard usually becomes more demanding: more automated testing, stricter review practices, better documentation, higher performance requirements. The Retrospective is where this evolution is discussed, and the team agrees together to raise the bar. A stronger Definition of Done means each Increment is more thoroughly verified and more genuinely usable — and it means the team's forecasts improve, because Done means the same thing every Sprint. The exam tests this indirectly through questions about quality: any option that weakens the Definition of Done to hit a scope target is wrong, because quality does not decrease during a Sprint. The Definition of Done is a floor, not a negotiation.

Transparency is the reason the Definition of Done matters so much. When everyone shares the same definition of finished, the state of the Increment is visible and honest: stakeholders know that Done means tested, integrated, and usable, not merely coded. Without a shared Definition of Done, each person has their own idea of finished, transparency collapses, and every forecast built on the Increment is unreliable. That is why multiple teams on one product must share one Definition of Done, and why the Developers are required to conform to it.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.Which statement BEST describes an Increment?

Report an error

Q2.What is the commitment for the Increment?

Report an error

Q3.A Product Backlog item is coded and works in a demo, but it has not been tested and does not meet the Definition of Done. Is it part of the Increment?

Report an error

Q4.If the Definition of Done is part of the organization's standards, what must Scrum Teams do?

Report an error

Q5.If there is NO organizational Definition of Done standard, who creates the Definition of Done?

Report an error

Q6.Three Scrum Teams work together on the same product. What does the Scrum Guide require about their Definition of Done?

Report an error

Q7.Which statement BEST distinguishes the Definition of Done from acceptance criteria?

Report an error

Q8.When is an Increment born?

Report an error

Q9.Who is required to conform to the Definition of Done?

Report an error