Scrum Events
What you must know
Scrum has five events, each a formal opportunity to inspect and adapt. They are timeboxed, and shortening or skipping one loses the associated transparency.
- The Sprint - the container for all other events, fixed length (typically 2–4 weeks). No changes that endanger the Sprint Goal; scope may be renegotiated with the PO as more is learned. A Sprint may be cancelled only by the Product Owner, and only if the Sprint Goal becomes obsolete.
- Sprint Planning - addresses why (Sprint Goal), what (selected backlog items), and how (plan). Timebox: up to 8 hours for a one-month Sprint.
- Daily Scrum - a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a status report to the SM or PO.
- Sprint Review - inspect the Increment with stakeholders and adapt the Product Backlog; a working session, not a formal sign-off gate. Timebox: up to 4 hours for a one-month Sprint.
- Sprint Retrospective - inspect how the last Sprint went regarding individuals, interactions, processes, tools, and Definition of Done; identify improvements. Timebox: up to 3 hours for a one-month Sprint.
Traps
- "The Review is a demo/sign-off" - it is a collaborative inspection that may change the backlog.
- "The Retrospective is only about process" - it also covers people and interactions.
- "The Daily Scrum is for the SM to collect status" - only Developers need attend; others attend only if it helps.
- "Cancel the Sprint because the team is behind" - only obsolescence of the Sprint Goal justifies cancellation.
Rule of thumb
Name the event, then name what it inspects and what it adapts. If an answer option does neither, it is wrong.
Worked example: Mid-Sprint, the PO learns a competitor launched a similar feature and the Sprint Goal is now pointless. The PO may cancel the Sprint; the team then reviews completed work and re-plans. Being "behind schedule" alone is not grounds for cancellation.