# Increment

A usable, verified addition to a product that meets the Definition of Done and advances its Product Goal.

- Type: artifact
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/increment/>)

## What it means

In Scrum, an Increment is a concrete stepping stone toward the Product Goal. It adds to all previous Increments, works with them, is usable, and meets the Definition of Done; multiple Increments may be created or released within a Sprint.

## Why it matters

A usable Increment makes progress inspectable and creates an option to deliver value or gather evidence. It shifts attention from percentage-complete work toward integrated quality and reduces the risk hidden in unfinished inventory.

## When to use it

Use the concept in Scrum to assess whether work has produced a usable product state. Do not label partially integrated components as Increments, and do not wait for a Sprint boundary when releasing a completed Increment earlier is valuable and safe.

## How it works

1. Select work that advances the current Product Goal.
2. Build and integrate changes with the existing product.
3. Verify the combined result against the shared Definition of Done.
4. Make the usable state available for inspection and, when appropriate, release.
5. Use feedback and evidence to adapt the Product Backlog.

## A practical example

A banking team completes and integrates a new beneficiary-verification flow. It passes the product’s security, accessibility, testing, and operational criteria, works with existing transfers, and can be released independently, so it constitutes an Increment.

## Where it breaks

An Increment proves conformance to agreed quality measures, not customer value or business impact. Weak Definitions of Done can hide risk, while large increments delay feedback. Release decisions may still depend on regulatory, commercial, or operational conditions.

## Common mistakes

- Calling unintegrated or unusable work an Increment.
- Assuming only one Increment may be created per Sprint.
- Using the Sprint Review as a mandatory release gate.
- Equating technical completion with validated customer value.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/increment/#visualization-increment>)

## Sources

1. [The 2020 Scrum Guide](<https://scrumguides.org/scrum-guide.html>) — Scrum Guides · Official framework guide
2. [Scrum Guide Revisions](<https://scrumguides.org/revisions.html>) — Scrum Guides · Official framework history

## Related topics

- [Definition of Done](<https://wiki.soroush.uk/topic/definition-of-done/>)
- [Sprint Review](<https://wiki.soroush.uk/topic/sprint-review/>)
- [Continuous Delivery](<https://wiki.soroush.uk/topic/continuous-delivery/>)
