Skip to content

Stockertim Dictionary · Project management

Increment

Also called product increment, increments

In short

The usable, tested piece of a product that an iteration adds to everything delivered so far.

  • Beginner
  • Concept
  • Checked

In detail

An increment is what an iteration produces: a working addition to the product that could be used, even if the organisation chooses not to release it yet. Each increment builds on the ones before, so after several iterations the product has grown in usable steps rather than appearing all at once at the end.

The point of increments is evidence. A working piece can be tested with real users, measured and improved, while documents and partly built components cannot. Teams usually agree a definition of done that every increment must meet, for example tested, reviewed, documented and accessible, so that unfinished work is not passed off as progress.

Incremental delivery also lets benefits start earlier. An online service might launch with the most common transaction and add rarer cases later, so users and the organisation gain value months before the full scope is complete. Releasing increments in this way also spreads risk, because problems in production show up in small, manageable pieces.

In practice

Digital teams release increments to a small group of users in a beta phase, measure how they perform and widen access as confidence grows.

Watch out

  • An increment must work end to end; a finished database with no screens is not one.
  • Incremental delivery fails if each piece is not integrated with the last.

Learn it properly

Official sources

Facts last checked on 3 November 2026.

Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.

English