A framework for iterative delivery.
WHAT IT IS
A framework organising work into fixed-length iterations.
WHAT THE ROLES ARE
A product owner, deciding what is built and in what order A scrum master, ensuring the process works and removing obstacles The development team, deciding how to build it
WHAT THE EVENTS ARE
Sprint planning, deciding what the iteration will deliver A daily coordination meeting A review, demonstrating what was built A retrospective, improving how the team works
WHAT THE ARTEFACTS ARE
A backlog of everything wanted A sprint backlog of what this iteration contains
The increment: working software
WHAT MAKES IT WORK
A team that can decide how to do the work A product owner who is available and decides Iterations that actually deliver working software Retrospectives that change something
WHAT MAKES IT FAIL
Scope added mid-iteration An absent product owner Retrospectives producing no change Ceremonies performed without purpose
WHAT TO ASSESS
Whether the team is genuinely delivering working software each iteration.
