Scrum was developed by Sutherland and Schwaber in the early 1990s. It’s is a lightweight framework that helps people, teams and organisations generate value through adaptive solutions for complex problems.
The Scrum framework is purposefully incomplete, only defining the parts required to implement empiricism. It’s not designed to be modified or customised, but to be built on top of to help adapt it to your team’s context, their work, and their goals.
Various processes, techniques and methods can be employed within the framework. Scrum makes visible the relative efficacy of current management, environment, and work techniques, so that improvements can be made.
Scrum combines four formal events for inspection and adaptation within a containing event, the Sprint. These events work because they implement the empirical Scrum pillars of transparency, inspection, and adaptation.
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.
The Sprint is a container for all other events and is used to deliver value. They are fixed length events of one month or less to create consistency. A new Sprint starts immediately after the conclusion of the previous Sprint.
A concrete stepping stone toward the Product Goal. Each Increment is additive, verified, and ensures that all Increments work together. In order to provide value, the Increment must be usable.