artifactDelivery & agility

Increment

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

Download Markdown (.md)

01What 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.[1][2]

A usable addition integrated with everything completed before it Selected work becomes an increment only after integration and the Definition of Done
  1. Product GoalLonger-term objective gives context
  2. Selected backlog itemsWork chosen to advance the current objective
  3. Implemented behaviorSmall additions created during the interval
  4. Integrated productNew work combines with all prior increments
  5. Done incrementUsable and verified against the shared quality standard

An increment may be released before the Sprint ends, but unfinished or unintegrated work is not part of the usable product increment.

02Why 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.

03When 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.

04How 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.

05A practical example

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.

06Where 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.

07Sources

  1. The 2020 Scrum GuideScrum Guides · Official framework guideThe 2020 Scrum Guide
  2. Scrum Guide RevisionsScrum Guides · Official framework historyScrum Guide Revisions
View saved topics

Start typing to search titles, definitions, categories, and frameworks.