Product Increment

What is a Product Increment?

A product increment is the sum of all completed, usable work a team adds to a product in a sprint, combined with everything delivered earlier. In Scrum, only work meeting the definition of done counts toward it.

Updated November 2026 · 3 min read


A product increment is the working, tested change to a product that a team produces during a sprint or iteration, added to everything built before it. In Scrum, an increment exists only when the work meets the team's definition of done, which means it is usable and could be released if the product owner chose to. Partially finished work, however close, is not part of the increment.

The increment is how agile teams make progress visible. Plans and status reports can look healthy while little real value exists; an increment is concrete software that stakeholders can inspect, use and react to.

The increment in the Scrum guide

The Scrum Guide lists the increment as one of Scrum's three artifacts, alongside the product backlog and the sprint backlog. The 2020 edition describes each increment as a concrete stepping stone toward the product goal, says that each increment is additive to all prior increments and thoroughly verified so that they work together, and notes that more than one increment may be created within a sprint. The sum of increments is presented at the sprint review, but an increment can be delivered to stakeholders before the sprint ends. The commitment attached to the increment is the definition of done.

Characteristics of a good increment

  • Done. It meets every item in the definition of done, such as code reviewed, tests passing, documentation updated and deployable.
  • Usable. A user or stakeholder can try it, even if the feature set is small.
  • Integrated. It works with everything built before it, not just in isolation.
  • Valuable. It moves the product toward its goal, ideally in a way that can be measured.
  • Releasable. Releasing it is a business decision, not a technical project.

Increment vs. iteration vs. release

TermWhat it isExample
Iteration or sprintA fixed period of timeTwo weeks starting on a Monday
IncrementThe finished output of that workUsers can now filter reports by date
ReleasePutting one or more increments in front of usersVersion 4.2 shipped to all customers

In the Scaled Agile Framework, the abbreviation PI refers to a longer cadence of several iterations, originally called a program increment and renamed a planning interval in SAFe 6.0. It is a time box for a team of teams, not the same thing as a Scrum increment.

Product increment example

Consider a hypothetical expense-management company whose team plans six stories in a two-week sprint toward the goal "Employees can submit mileage claims." By the sprint review, four stories meet the definition of done: entering a trip, calculating mileage at the company rate, attaching notes, and submitting the claim for approval. A fifth story, map-based distance lookup, is coded but not yet tested, and the sixth has not started.

The increment shown at the review includes only the four done stories. That is enough to release to a pilot group of 50 employees, who submit their first claims the following week. The two unfinished stories return to the product backlog, and pilot feedback shows that most users want to reuse frequent trips, which the product owner ranks above the map lookup.

Common pitfalls

  • Counting "almost done" work. Including untested or unintegrated work in the increment hides risk and inflates progress.
  • A weak definition of done. If "done" excludes testing or deployment, increments pile up work that must be finished later.
  • Technical-only increments. Finishing a database layer with no usable feature on top makes inspection and feedback impossible.
  • Never releasing. Increments that sit unreleased for months lose the feedback that justifies building them in small pieces.

Each increment should serve the sprint goal and the broader product goal. Increments are what the product owner inspects with stakeholders, and decisions about when to ship them belong to release management.

Frequently asked questions

What is the difference between a product increment and a release?

A product increment is the finished, usable output of a sprint that meets the definition of done, while a release puts one or more increments in front of users. An increment can be releasable without being released, because when to ship is a business decision. Several increments are often bundled into one release, which release management governs.

Does unfinished work count toward a product increment?

No. In Scrum, only work that meets the team's definition of done becomes part of the increment. A story that is coded but untested, or built but not integrated, goes back to the product backlog. Counting almost-done work hides risk and makes progress look better than it is, which is why a definition of done that includes testing and deployment matters.

Is a Scrum increment the same as a SAFe program increment?

No. A Scrum increment is the done, usable output a team produces in a sprint. In the Scaled Agile Framework, PI refers to a longer cadence covering several iterations for a team of teams. It was originally called a program increment and was renamed a planning interval in SAFe 6.0, so it is a time box rather than a piece of finished product.