Scrum
A lightweight framework that helps a small team deliver value in short cycles (sprints) of up to a month, learning from every delivery. It's simple to explain and demanding to practice: it works when the team, the Product Owner, and management all do their part.
Origin: Ken Schwaber and Jeff Sutherland; the current Scrum Guide dates from November 2020
01The essentials
The essentials
- 01
Three accountabilities
The Product Owner decides what gets built and in what order; the Scrum Master looks after the method and removes obstacles; developers decide how to do the work.
- 02
Five events
The sprint and, within it, planning, the daily scrum, the review with the business, and the team retrospective.
- 03
Three artifacts
The product backlog, the sprint backlog, and the increment, each with its commitment (product goal, sprint goal, and definition of done).
- 04
Empiricism
Transparency, inspection, and adaptation. The plan adjusts to what each sprint teaches, not the other way around.
- 05
Where it usually fails
Product Owners without time or authority, sprints that don't end in something usable, and retrospectives that change nothing.
Sources
- Ken Schwaber and Jeff Sutherland, The Scrum Guide (2020)(opens in a new tab)
- Manifesto for Agile Software Development(opens in a new tab)
This page is an orientation guide and does not replace the official documentation of each framework. Framework names belong to their respective owners.