In this post I want to explore whether the Increment, a core concept to Scrum, needs to be changed for Scrum in a non-IT context. In future posts, I will do the same for the Definition of Done, or other concepts that may provide a better understanding of Scrum when applied to non-IT context.

Most organizations are using Scrum, however, many of them feel like the agility of their organization has degraded, and they might be right! Often, using Scrum starts out as a way to improve development efforts coordinated within an IT division or department, but that is not the most effective organization structure to potentially get maximum benefit from Scrum.

A goal, a forecast of functionality, plus the plan to deliver it. the Why, the What and the How. Sprint Goal + Sprint Backlog. How do these relate, plus a practical example.

The purpose of Scrum is to deliver Increments of releasable functionality. So at each Sprint Review, a “Done” Increment is required to make transparent the progress made by the team.