Skip to content
BENIBIX Learn

Iteration vs Increment

People think an iteration and an increment are the same thing. An iteration is a block of time. An increment is the working piece of product that comes out of it. One is the when, the other is the what.

Business📋 Agile Delivery

Iteration

One short round of work, often one to four weeks. Build, check and learn, then go again.

An iteration is a short, fixed stretch of time in which a team builds, checks and learns. Most last one to four weeks. At the end the team looks at what it made and what it learned. The next iteration starts with that in mind. In Scrum, an iteration is called a sprint.

Example
Emma's team works in two-week iterations. In the first one they build a sign-up form, users say it asks for too much, and the second one cuts it down.
Why it matters
Short rounds give a team many chances to change course. A long project with no rounds gets one chance, at the end.
Full entry
Business📋 Agile Delivery

Increment

A finished, usable piece of the product. Each new one adds to the last and works with it.

An increment is a usable step toward the Product Goal. Each one adds to all the ones before, and they must all work together. Work only becomes an increment when it meets the Definition of Done. A sprint can make more than one. A team may also release one before the sprint ends.

Example
After sprint 3, a booking app lets users search and book a room. The increment from sprint 4 adds paying by card, and search still works.
Why it matters
It is proof of progress that people can use. Half-done work proves nothing and cannot be shipped.
Full entry

In one line

Iteration
One short round of work, often one to four weeks. Build, check and learn, then go again.
Increment
A finished, usable piece of the product. Each new one adds to the last and works with it.