The 5 Scrum Events Explained (With Purpose and Timeboxes)
Direct answer: Scrum defines five events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. They create regularity and minimize the need for meetings not defined in Scrum. Each event is a formal opportunity to inspect and adapt something specific.
For PSM I, “knowing the names” is not enough. You need purpose, timebox, participants, and what is inspected or adapted — and you must not invent extra mandatory ceremonies.
Video: Scrum Events Explained
Why Scrum uses events
Scrum is founded on empiricism: transparency, inspection, and adaptation. Events are the cadence that makes those three pillars practical. Without events, teams invent status theater; with events used poorly, teams still miss the purpose (for example, turning Daily Scrum into a report to managers).
Quick reference: purpose + timebox
| Event | Primary purpose | Max timebox (1-month Sprint) | Who |
|---|---|---|---|
| The Sprint | Container for all other events; create a usable Done Increment toward the Product Goal | 1 month or less | Scrum Team |
| Sprint Planning | Initiate the Sprint; define why, what, and how | 8 hours | Scrum Team (others as needed) |
| Daily Scrum | Inspect progress toward the Sprint Goal; adapt the Sprint Backlog | 15 minutes | Developers (others may attend if invited; Developers run it) |
| Sprint Review | Inspect the Increment and adapt the Product Backlog | 4 hours | Scrum Team + key stakeholders |
| Sprint Retrospective | Plan ways to increase quality and effectiveness | 3 hours | Scrum Team |
Shorter Sprints usually mean shorter Planning, Review, and Retrospective timeboxes proportionally. Daily Scrum stays 15 minutes.
1. The Sprint
The Sprint is a container event of one month or less during which a usable Increment is created. Sprints have consistent durations. A new Sprint starts immediately after the previous Sprint concludes.
- All work necessary to achieve the Product Goal — including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective — happens inside Sprints.
- During the Sprint: no changes are made that would endanger the Sprint Goal; quality does not decrease; the Product Backlog is refined as needed; scope may be clarified and renegotiated with the Product Owner as more is learned.
- A Sprint can be cancelled if the Sprint Goal becomes obsolete — only the Product Owner has the authority to cancel the Sprint.
Exam traps: Sprints are not projects with variable quality at the end; “hardening sprints” that defer Done contradict the Increment commitment.
2. Sprint Planning
Sprint Planning initiates the Sprint by laying out the work to be performed. The resulting plan is created by the collaborative work of the entire Scrum Team.
The Scrum Guide structures Planning around three topics:
- Why is this Sprint valuable? The Product Owner proposes how the product could increase its value and utility in the current Sprint. The whole Scrum Team then collaborates to define a Sprint Goal.
- What can be Done this Sprint? Developers select items from the Product Backlog. Through discussion with the Product Owner, Developers may refine items.
- How will the chosen work get done? Developers plan the work necessary to create an Increment that meets the Definition of Done. This is often by decomposing Product Backlog items into smaller work items of one day or less.
The Sprint Goal, selected Product Backlog items, and the plan for delivering them together form the Sprint Backlog.
Exam traps: stakeholders do not “assign capacity”; the Scrum Master does not decide the Sprint Goal alone; Planning is not a handoff of a fixed scope contract.
3. Daily Scrum
The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. It is a 15-minute event for the Developers of the Scrum Team.
- To reduce complexity, it is held at the same time and place every working day of the Sprint.
- If the Product Owner or Scrum Master is actively working on items in the Sprint Backlog, they participate as Developers.
- Developers can select whatever structure and techniques they want, as long as the Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work.
- Daily Scrums improve communications, identify impediments, promote quick decision-making, and eliminate the need for other meetings.
Critical 2020 update: the three classic questions are not mandated. If a question says the Daily Scrum “must” use three questions, that is usually a trap.
Exam traps: it is not a status meeting for managers; the Scrum Master does not have to run it; it does not replace detailed technical collaboration that may happen throughout the day.
4. Sprint Review
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
- Attendees collaborate on what to do next.
- The Product Backlog may be adjusted to meet new opportunities.
- The Sprint Review is a working session, not a mere presentation or “demo theater.”
Exam traps: the Review is not only a slide show; stakeholders help inspect outcomes and adapt the backlog; DoD still gates what is truly complete.
5. Sprint Retrospective
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regard to individuals, interactions, processes, tools, and their Definition of Done.
- Assumptions that led them astray are identified and their origins explored.
- The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.
- The most impactful improvements are addressed as soon as possible — they may even be added to the Sprint Backlog for the next Sprint.
Exam traps: Retrospective is not optional “if we have time”; it is not a blame session run by management; it is for the Scrum Team.
Event sequence in a Sprint
- Sprint starts with Sprint Planning.
- Each working day: Daily Scrum (and collaborative work).
- Near end: Sprint Review with stakeholders.
- Then: Sprint Retrospective.
- Next Sprint starts immediately after.
PSM I traps about events
| Trap | Better answer direction |
|---|---|
| Daily Scrum must use three questions | Structure is up to Developers; purpose is inspect Sprint Goal progress and adapt the plan |
| Sprint Review is only a demo | Working session to inspect Increment and adapt Product Backlog |
| Anyone can cancel a Sprint | Only the Product Owner has authority to cancel |
| Retrospective is for stakeholders | Scrum Team inspects itself; stakeholders belong in Review, not as default Retro attendees |
Practice these topics
Use free adaptive practice for weak event topics: PSM I practice test. When you are close to exam readiness, run a timed 80-question mock exam. Full map: PSM I certification guide.