Events
Scrum events create regularity and limit risk. The exam tests each event's purpose, timebox, participants, and how events support inspection and adaptation.
Core rules
- The Sprint is the container for all other events and is one month or less.
- Sprint Planning sets the Sprint Goal and Sprint Backlog; for a one-month Sprint, the timebox is eight hours.
- The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the plan.
- The Sprint Review inspects the Increment and adapts the Product Backlog; it is at most four hours for a one-month Sprint.
- The Sprint Retrospective inspects the team's way of working and plans improvements; it is at most three hours for a one-month Sprint.
- Events are not optional ceremonies; skipping them removes opportunities to inspect and adapt.
Worked example
A Scrum Master notices the Daily Scrum has become a 30-minute status report to the manager. The fix is not to shorten the meeting only. The team should clarify that Developers own the event, focus on the Sprint Goal, and use a lightweight format. Reasoning: the event's purpose is adaptation by Developers, not reporting upward.
Traps
Calling the Sprint Review a demo only; letting stakeholders direct the Daily Scrum; using the Retrospective only for complaints; cutting timeboxes by skipping inspection; treating Sprint cancellation as normal.