Skip to content
BENIBIX Learn

Increment

Business📋 Agile DeliveryScrum

Also known as Product Increment, Scrum Increment

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

Think of it like

It is like adding a new floor to a toy tower. Each new floor sits on the ones below, and the tower still stands.

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.

Definition

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.
Each stack is an increment. The newest block is added on top, and every block below still works.

Common mistake

Calling work an increment while it still needs testing. If it does not meet the Definition of Done, it is not one.

Key takeaways

  1. 1
    Usable. It works and could be released.
  2. 2
    Adds up. Each one builds on the last.
  3. 3
    Done means done. It meets the Definition of Done.

Compare

Learn it properly