Increment

Increment is a usable, high-quality addition to a product in Scrum, meeting the Definition of Done and representing tangible progress toward the Product Goal

Definition and Core Concept

An Increment in Scrum is a concrete, usable step toward the Product Goal. It encompasses all completed Product Backlog items for a Sprint, integrated with prior Increments, and must meet the Definition of Done. Each Increment is additive, ensuring that the product remains in a potentially releasable state at all times. Multiple Increments can be created within a single Sprint, but only work meeting the Definition of Done is considered part of an Increment.

Origins and Evolution

The concept of the Increment has been part of Scrum since its inception in the 1990s by Ken Schwaber and Jeff Sutherland. It draws from Agile’s emphasis on delivering working software frequently and Lean’s focus on continuous flow of value. Over time, the Scrum Guide has refined the definition to emphasize integration, usability, and quality. The 2020 Scrum Guide reinforced the Increment’s role by explicitly linking it to the Scrum Commitment of the Definition of Done, ensuring consistent quality across all deliverables.

Increment in the Agile Landscape

In Agile software development, the Increment embodies the principle of delivering value early and often. It aligns with Lean’s “build quality in” mindset and DevOps practices of continuous integration and continuous delivery (CI/CD). In product management, the Increment represents measurable progress toward strategic objectives, enabling stakeholders to inspect outcomes and adapt priorities based on real, working product functionality.

Key Characteristics of an Increment

Usable: The Increment must be in a state that could be released to users, even if the Product Owner chooses not to release it immediately.
Integrated: It includes all prior Increments, ensuring compatibility and cohesion.
Meets the Definition of Done: Quality standards are consistently applied to every Increment.
Additive: Each Increment builds upon the last, moving the product closer to the Product Goal.
Transparent: Its state and readiness are visible to all stakeholders.

Relationship to Scrum Artifacts and Commitments

The Increment is one of the three Scrum Artifacts, alongside the Product Backlog and Sprint Backlog. Its associated commitment is the Definition of Done, which ensures that every Increment meets agreed quality standards. This relationship reinforces the Scrum pillars:

Transparency: The Definition of Done makes the state of the Increment clear.
Inspection: Stakeholders can assess the Increment’s value and quality during the Sprint Review.
Adaptation: Feedback on the Increment informs adjustments to the Product Backlog and future Sprints.

Creating an Increment

In Scrum, Increments are created through collaborative work during the Sprint. The process typically involves:

Selecting Product Backlog Items: Chosen during Sprint Planning to align with the Sprint Goal.
Developing and Integrating: Work is completed and integrated with existing functionality throughout the Sprint.
Verifying Against the Definition of Done: Ensuring all quality criteria are met before considering work part of the Increment.
Reviewing and Demonstrating: Presenting the Increment to stakeholders in the Sprint Review for feedback and inspection.

Multiple Increments in a Sprint

While at least one Increment must be produced each Sprint, teams may create multiple Increments within the same Sprint. This is common in environments with continuous delivery pipelines, where features are deployed as soon as they meet the Definition of Done. Regardless of frequency, all Increments must be integrated and usable.

Benefits of Well-Managed Increments

Provide tangible evidence of progress toward the Product Goal.
Enable early and frequent delivery of value to stakeholders.
Reduce risk by ensuring quality and integration at every step.
Support adaptability by allowing feedback on working product functionality.
Facilitate continuous improvement through regular inspection and adaptation.

Common Misunderstandings

Increment equals a release: An Increment is potentially releasable, but release is a separate decision by the Product Owner.
Increment is just completed tasks: Only work meeting the Definition of Done and integrated into the product counts as part of the Increment.
Increment is optional: Every Sprint must produce at least one Increment, regardless of release plans.

Enablers for Effective Increments

Clear Definition of Done: Ensures consistent quality and readiness.
Continuous Integration: Automates merging and testing to maintain a usable product state.
Collaborative Development: Encourages shared ownership and accountability for the Increment.
Automated Testing: Validates functionality and quality quickly and reliably.
Stakeholder Engagement: Regular feedback ensures the Increment delivers value.

Example in Practice

A Scrum Team developing a project management tool sets a Sprint Goal to “Enable task assignment with due dates.” During the Sprint, they complete the necessary Product Backlog items, integrate the new feature with existing functionality, and ensure it meets the Definition of Done - passing automated tests, meeting performance benchmarks, and updating user documentation. This Increment is demonstrated at the Sprint Review, where stakeholders provide feedback that informs future backlog refinement. Even if the Product Owner chooses not to release it immediately, the Increment is fully usable and ready for deployment.

Conclusion

The Increment is a cornerstone of value delivery in Scrum, representing tangible, high-quality progress toward the Product Goal. By ensuring that each Increment is usable, integrated, and meets the Definition of Done, Scrum Teams maintain transparency, enable frequent inspection, and adapt effectively to change. When managed well, Increments provide a reliable rhythm of delivery, reduce risk, and keep the product in a state of continuous readiness for release.