Increment
Part of the Scrum Guide chapter index. Read the canonical version inline in the app: Increment on app.prettyscrum.org.
Why this chapter matters for the PSM I exam
An Increment is a concrete, usable step toward the Product Goal. Multiple Increments may be created within a single Sprint — the moment a Product Backlog item meets the Definition of Done, an Increment exists. The 2020 Guide formalized the Definition of Done as the Increment’s commitment.
The Scrum Guide text
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. The sum of the Increments is presented at the Sprint Review thus 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.
Work cannot be considered part of an Increment unless it meets the Definition of Done.
Commitment: Definition of Done. The Definition of Done 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.
The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration.
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. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.
Source: 2020 Scrum Guide by Ken Schwaber and Jeff Sutherland, © CC BY-SA 4.0. License.
Key points to remember
- A usable step toward the Product Goal.
- Multiple Increments may exist within one Sprint.
- Each Increment is additive to all prior Increments.
- Commitment: the Definition of Done.
- Work not meeting DoD is not released and is reconsidered for future Sprints.
- An Increment can be delivered to stakeholders before the Sprint Review.
- If the organization has a DoD standard, the Scrum Team must follow it as minimum.
Common exam trap
Two big tests: (1) Increments can be delivered any time, not only at the end of the Sprint. (2) Work that doesn’t meet the Definition of Done is not part of the Increment and goes back to the Product Backlog.
Practice this chapter
Related chapters
Or jump back to the Scrum Guide chapter index or the PSM I hub.
Author: Maurice Heinze (PSM I, certified by Scrum.org). Last updated: 2026-05-04. Scrum Guide content licensed under CC BY-SA 4.0.