In Scrum, everything revolves around delivering value in short cycles. The Increment is that concrete, working solution that is ready at the end of each sprint. At Spark Academy, we see that the Increment is not just a final product, but also an opportunity to learn from feedback and discover where the team can continue to grow.
An Increment is the sum of all completed and ‘done’ items from the sprint, combined with the results from previous sprints. It's not just about a piece of code, but about every form of value that has been added to the product and is ready for use. This could be a new functionality, an improved module, or a fixed bug. As long as it meets the ‘Definition of Done’, the Increment can be delivered, demonstrated, or even put into production.
Characteristics of an Increment:
Development Team: Works on the items that together form the Increment and ensures that everything meets the agreed-upon quality criteria.
Product Owner: Ensures that the delivered functionality aligns with the product vision and priorities.
The Scrum Master has no direct influence on the content of the Increment, but plays a key role in safeguarding the process:
The Increment is at the core of what makes Scrum so powerful: regularly delivering a fully functional and valuable piece of product. For the Development Team, this means clear quality criteria; for the Product Owner, a strong alignment with the product vision; and for the Scrum Master, an important task in safeguarding transparency and process discipline. This way, the product grows sprint after sprint, and the team gains control over both progress and quality.