Scrum Events
The Sprint as a container
All other events happen inside the Sprint, which is fixed at one month or less and of consistent length. A Sprint may only be cancelled by the Product Owner, and only when the Sprint Goal becomes obsolete - it is a rare, expensive act, not a routine management response to scope change.
The four inside events
- Sprint Planning addresses three topics: why (Sprint Goal), what (items selected), how (the plan).
- Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a status report upward.
- Sprint Review inspects the outcome with stakeholders and adapts the Product Backlog. It is a working session, not a gate, sign-off or pure demo.
- Sprint Retrospective inspects how the last Sprint went regarding individuals, interactions, processes, tools and the Definition of Done, and identifies the most helpful changes.
Timeboxes
For a one-month Sprint: Planning ≤ 8 hours, Review ≤ 4 hours, Retrospective ≤ 3 hours. Shorten proportionally for shorter Sprints.
Traps
- Inventing "backlog refinement" as a fifth formal event - it is an ongoing activity, typically up to 10% of capacity.
- Treating the Daily Scrum as a report to the Scrum Master.
- Retrospectives that produce actions with no owner and no follow-through.
- Confusing the Sprint Review's purpose (inspect outcome, adapt backlog) with stakeholder approval.
Worked example
A two-week Sprint halves the one-month timeboxes: Planning up to 4 hours, Review up to 2 hours, Retrospective up to 1.5 hours. Scale proportionally; never scale upward.