agile3
Practices & Events

Increment

A finished, usable step toward the Product Goal that meets the Definition of Done.

2 min read · Beginner

In 30 seconds

  • An Increment is working product, not a status report.
  • It must meet the Definition of Done to count.
  • Several Increments can be created and released within one sprint.

What counts

An Increment is a piece of work that is done and usable, and that adds to all previous Increments. Half-built features, untested code and design documents don't count. The Definition of Done is the line that decides.

Increment vs release

Creating an Increment doesn't mean it must go live. The Product Owner decides when to release. Many teams release several times per sprint; others release every few sprints. Either way, the Increment should be ready to release.

At the Sprint Review

The Sprint Review shows the Increment to stakeholders. Only done work is presented as done; anything else goes back to the Product Backlog.

Myth vs reality

Myth · One sprint, one Increment.
Reality · Teams can create many Increments in a sprint.
Myth · Mostly done is good enough to demo.
Reality · If it doesn't meet the Definition of Done, it isn't part of the Increment.
Myth · An Increment must be released.
Reality · It must be releasable; releasing is a business decision.

FAQ

Is an Increment the same as an MVP?

No. An MVP is an experiment; an Increment is any done step toward the product goal.

Who decides if work is done?

The Definition of Done, which the Scrum team applies.

Can a team have nothing to show?

It happens, and it's a strong signal to inspect in the Retrospective.