Increment

Delivering working, valuable software at the end of each iteration, ensuring value is incrementally added to the product.

Increment refers to the tangible, usable output produced at the end of each iteration, especially in frameworks like Scrum and Agile. It represents the sum of all completed work during a Sprint, ensuring that the product is always potentially shippable and adds measurable value.

In Scrum, the Increment is a core artifact that reflects the work completed in a Sprint. It embodies the principle of delivering working software incrementally, which ensures that value is continuously added to the product. By delivering increments regularly, teams can receive timely feedback, make improvements, and reduce the risks of large-scale releases.

The significance of the Increment lies in its ability to provide transparency. It allows teams and stakeholders to inspect the progress of work, giving clear indicators of what is done and what remains. This transparency fosters collaboration and ensures alignment between stakeholders and the development team.

In Agile environments, the Increment serves as the basis for adaptation. Teams can adjust their approach based on the feedback gathered from the increment, making the development process iterative and responsive to changing needs.

By prioritising the delivery of increments, organisations can streamline workflows, foster continuous improvement, and ensure that products evolve in a way that meets customer needs. The focus on working software allows teams to minimise technical debt, avoid over-engineering, and align more closely with business objectives.

Ultimately, the Increment provides the concrete, inspectable output that drives decision-making and enhances collaboration, making it one of the most crucial artifacts in Agile and Scrum practices.

The strongest work on Increment — ranked by substance, not recency. How this is ranked

Article Scrum Product Development

Delivery is the only Measure of Progress in Scrum

Scrum teams must deliver working software to real users every Sprint; true progress is measured by delivery to production, not just by …

Read article
Article Product Development Engineering Excellence

Release planning and predictable delivery

Explores how agile teams can achieve predictable software delivery through quality focus, effective release planning, and continuous …

Read article
Article Scrum Product Development

The Scrum Master is accountable for Delivery

Explains how the Scrum Master is accountable for enabling effective product delivery, fostering team success, and ensuring each sprint …

Read article
Article Product Development Scrum

Without Delivery, There Is No Value

Value in software is only realised through delivery. Frequent releases validate assumptions, reduce risk, and enable rapid feedback, …

Read article
Video DevOps Engineering Excellence

Why “Done” Only Counts When It’s Live: Moving Beyond Fake Finishes to Real Value in Software Delivery

Discover why “done” means live in production, not just code complete. Learn to deliver real value, close feedback loops, and drive outcomes …

Watch video
Video Product Development Technical Leadership

Special Sprints: Agile Banditry or Risk Management?

Explores why special sprints like Sprint Zero or hardening sprints undermine Agile by delaying work, increasing risk, and reducing …

Watch video
Article Engineering Excellence Scrum

A better way than staggered iterations for delivery

Explains why staggered iterations harm software delivery, increasing technical debt, and recommends cross-functional teams, test-first, and …

Read article
Article Product Development Scrum

Storms of Neglect The Perils of Not Delivering Usable Products in Agile Iterations

Failing to deliver a usable product each agile iteration leads to lost trust, technical debt, poor adaptability, misaligned expectations, …

Read article
Article Product Development Engineering Excellence

How Usable Working Products Are Your Ultimate Weapon Against Risks

Delivering usable, working products frequently is key to reducing risk in Agile. Focus on feedback, automation, and lean practices over …

Read article