Scrum is a widely used framework that helps teams manage complex projects by breaking down large undertakings into smaller cycles of work. At the heart of this approach are components known as artifacts, and one of the most significant is the Increment. It represents the actual, usable result produced during a work cycle. Understanding the Increment is fundamental to grasping how Scrum turns plans into tangible progress and delivers value consistently.
The Core Definition of an Increment
An Increment is a concrete, usable piece of work that serves as a stepping stone toward the overarching Product Goal. It is not just the work completed in the most recent Sprint, but the sum of all Product Backlog items finished during that Sprint plus the value of all previous Increments. This additive nature is a defining characteristic.
Each new Increment is integrated with and thoroughly verified against all prior ones to ensure they work together seamlessly. The result is a single, cohesive, and usable version of the product. For an Increment to be valuable, it must be in a usable condition, meaning it could potentially be released to stakeholders.
The Purpose of the Increment
The primary purpose of producing a potentially releasable Increment in every Sprint is to deliver a tangible piece of value to stakeholders on a predictable schedule. This regular delivery moves progress from an abstract report to a functional piece of the product that can be seen and used.
This process also serves as a mechanism for gathering feedback. When stakeholders interact with a working part of the product, they can provide specific, actionable insights. This feedback loop guides future development, ensuring the team is building what users need.
By regularly producing a tested and usable product, the team reduces risk. The danger of investing time and resources in building the wrong thing is minimized because the product’s direction is validated at the end of each Sprint.
The Connection to the Definition of Done
The creation of an Increment is directly governed by the “Definition of Done” (DoD). The DoD is a formal, shared understanding across the Scrum Team of what it means for work to be complete. It acts as a checklist that ensures every completed item meets a consistent level of quality. This can include activities such as:
- Writing code
- Creating automated tests
- Peer review
- Passing specific quality assurance checks
A Product Backlog item cannot be considered part of an Increment unless it meets every criterion in the Definition of Done. The moment a work item fulfills the DoD, a new Increment is born.
If a team works on an item but fails to meet the Definition of Done by the end of the Sprint, that item cannot be included in the Increment. It is returned to the Product Backlog for reconsideration in a future Sprint.
How an Increment is Created During a Sprint
The Developers on the Scrum Team are responsible for creating the Increment. The process begins during Sprint Planning, where the team selects items from the Product Backlog. Developers then create a forecast of which items they can transform into a “Done” Increment within the upcoming Sprint, and this plan becomes the Sprint Backlog.
Throughout the Sprint, Developers execute the tasks necessary to turn the selected backlog items into a finished piece of the product. This work covers everything from software design and coding to testing and integration to ensure all items meet the team’s shared Definition of Done.
Multiple Increments can be created within a single Sprint, as each time a Product Backlog item meets the DoD, an Increment is formed. These are then integrated, and the sum of all completed items forms the final Increment for the Sprint Review.
Inspecting the Increment at the Sprint Review
The Increment plays a central role in the Sprint Review. The purpose of this meeting is for the Scrum Team and its stakeholders to inspect the Increment that was produced during the Sprint. This provides a formal opportunity to demonstrate the progress made toward the Product Goal.
This event is a working session where stakeholders can interact with the product and provide valuable feedback. The Scrum Team presents the completed work, and the conversation focuses on what was accomplished and how it impacts the future direction of the product.
The feedback gathered is a direct input for the Product Backlog. Based on this inspection, the Product Owner may adjust priorities for the next Sprint.
Examples of an Increment
Tangible examples across different fields help illustrate the concept. For an e-commerce website, a team’s first Increment might be a basic but functional search bar that allows users to find products. A subsequent Increment could build upon that by adding a working shopping cart feature that integrates with the search results.
In the context of a mobile banking application, an early Increment could be a secure user login and authentication feature. The next Increment might be a feature that allows authenticated users to view their current account balances.
The concept also applies outside of software. For a marketing team running a campaign, an Increment could be a complete set of social media ad creatives for a single platform. The next Increment might be the finished landing page that those ads will direct traffic to.