What is the Increment
The Increment is a usable piece of the product. Each Increment is added to all prior Increments and verified to work with them.
Multiple Increments can be produced in a single Sprint. The sum of the Increments is presented at the Sprint Review.
Work is not part of the Increment unless it meets the Definition of Done.
Why It Matters
The Increment is the proof that Scrum is working. Plans and estimates are not proof. A Sprint without an Increment produced no usable value.
Frequent Increments let the Product Owner release early, gather real feedback, and adapt the Product Backlog based on what users actually do.
How It Works in Scrum
Three rules govern the Increment.
- It must meet the Definition of Done. Otherwise it is not part of the Increment.
- It is additive. Each Increment integrates with the ones before it. The product as a whole keeps working.
- It can be released at any time. The Sprint Review is not a release gate. Increments can ship during the Sprint, after Sprint Review, or whenever the business wants.
Common Mistakes
- Calling work "done" when it isn't. Hidden inventory always surfaces later, usually right before release.
- Treating Done as flexible. "Done for now" or "done pending QA" is not Done.
- Skipping integration to hit a date. Unintegrated work is not an Increment.
- Holding shippable Increments for one big release. This defers value and learning.
- Treating Sprint Review as the release gate. Increments can ship any time.
Key Takeaways
- The Increment is a usable, integrated piece of the product.
- Work that does not meet the Definition of Done is not part of the Increment.
- Multiple Increments can be produced and released in one Sprint.
- The Increment is the only real proof of progress.