Scrum Events
The Sprint as container
Every other event happens inside the Sprint, which is fixed in length at one month or less. Within a Sprint: no changes that endanger the Sprint Goal, quality does not decrease, and scope may be clarified and renegotiated with the Product Owner as more is learned. Only the Product Owner can cancel a Sprint, and only when the Sprint Goal becomes obsolete.
The four events
Sprint Planning (maximum 8 hours for a one-month Sprint) answers why (Sprint Goal), what (items selected) and how (the plan). The output is the Sprint Backlog.
Daily Scrum is a 15-minute event for the Developers, held every working day at the same time and place. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. The structure is chosen by the Developers. It is not a status meeting, and it is not the only time Developers may adjust their plan.
Sprint Review (maximum 4 hours) is a working session with stakeholders to inspect the Increment and adapt the Product Backlog. It is not a sign-off gate, a demo ritual, or an approval stage.
Sprint Retrospective (maximum 3 hours) concludes the Sprint. The team inspects individuals, interactions, processes, tools and the Definition of Done, and identifies improvements. A new Sprint starts immediately afterwards.
Traps
- Only Sprint Planning shortens for shorter Sprints (2 hours for a one-week Sprint); the other timeboxes are fixed maximums.
- The Review and Retrospective happen inside the Sprint, not after it.
- "Sprint 0", "hardening Sprints" and "release Sprints" are not Scrum events.
- The Daily Scrum is not where the Product Owner assigns work or collects status.
Rule of thumb
For any event, name what is inspected and what is adapted. If you cannot name both, the event is being run as a ritual.