Scrum Events
The Five Events
The Sprint is the container; inside it are Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective. Every event is an opportunity to inspect and adapt, has a maximum timebox, and exists for a purpose - not as a status ceremony.
Purposes to Memorize
- Sprint Planning: define why (Sprint Goal), what (selected items), and how (plan).
- Daily Scrum: Developers inspect progress toward the Sprint Goal and adapt the plan; 15 minutes, same time and place.
- Sprint Review: inspect the outcome with stakeholders and adapt the backlog; not a demo-only gate.
- Retrospective: inspect how the last Sprint went regarding people, process, tools, and Definition of Done; identify improvements.
Timebox Traps
Timeboxes are maximums, not targets - ending early is fine; running over is not. A common trap asks what to do when a Review runs long: the answer is to respect the timebox, not to extend it. Another trap treats the Daily Scrum as a reporting meeting to the Scrum Master; it is Developers' planning meeting.
Cancellation and Change
Only the Product Owner can cancel a Sprint, and only when the Sprint Goal becomes obsolete. Changes that do not endanger the Sprint Goal can be negotiated within the Sprint.
Worked rule of thumb
When a scenario asks "which event?", ask what is being inspected: the product outcome → Review; the team's way of working → Retrospective; progress toward the Sprint Goal → Daily Scrum; the Sprint's scope and plan → Planning.
Exam traps
- The Sprint Review is not a sign-off or release gate.
- The Retrospective produces improvements, not just discussion.
- Events may be combined or shortened in some scaled contexts, but the core purposes remain.