Scrum has five events: the Sprint, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. The Sprint is a fixed-length container of one month or less that holds the other four, and each of those has a maximum timebox: 8 hours for Sprint Planning, 15 minutes for the Daily Scrum, 4 hours for the Sprint Review and 3 hours for the Sprint Retrospective, based on a one-month Sprint. Shorter Sprints usually have shorter events.
That is the short answer. The rest of this article explains the purpose of each event, who takes part, what a timebox really means, and the event questions that catch people out on PSM I, PSPO I and CSM exams. Everything here follows the Scrum Guide 2020.
Scrum events and timeboxes at a glance
A timebox is a maximum, not a target. The figures in the Scrum Guide are given for a one-month Sprint.
| Event | Maximum timebox (one-month Sprint) | Who takes part | Main output |
|---|---|---|---|
| Sprint | Fixed length, one month or less | The whole Scrum Team | One or more Done Increments toward the Product Goal |
| Sprint Planning | 8 hours | The whole Scrum Team (others may be invited to advise) | Sprint Goal and Sprint Backlog |
| Daily Scrum | 15 minutes, every day | The Developers | An adapted plan for the next day of work |
| Sprint Review | 4 hours | The Scrum Team and key stakeholders | Shared understanding of progress and an adjusted Product Backlog |
| Sprint Retrospective | 3 hours | The Scrum Team | Improvements to quality and effectiveness |
The Sprint: the container event
The Sprint is an event in its own right, and it is the one people forget when they count. It has a fixed length of one month or less, and it contains Sprint Planning, the Daily Scrums, the Sprint Review and the Sprint Retrospective. All the work needed to reach the Product Goal happens inside Sprints. A new Sprint starts immediately after the previous one ends.
The Sprint has a fixed length rather than a maximum you can cut short whenever you like. The only way a Sprint ends early is if it is cancelled, and only the Product Owner can cancel a Sprint, when the Sprint Goal becomes obsolete. The Scrum Master, the Developers, stakeholders or management cannot cancel it, although they can of course raise the issue with the Product Owner.
Sprint Planning (max 8 hours)
Sprint Planning starts the Sprint. The whole Scrum Team works together on the plan, and they may invite other people to give advice. It addresses three topics:
- Why is this Sprint valuable? The Scrum Team crafts the Sprint Goal, the single objective for the Sprint.
- What can be Done this Sprint? The Developers select items from the Product Backlog, in discussion with the Product Owner.
- How will the chosen work get done? The Developers plan the work needed to turn the selected items into an Increment that meets the Definition of Done.
The Sprint Goal, the selected Product Backlog items and the plan for delivering them together form the Sprint Backlog, which belongs to the Developers.
Daily Scrum (15 minutes)
The Daily Scrum is a 15-minute event for the Developers. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as needed. It is held at the same time and place every working day of the Sprint to reduce complexity.
The Developers can use any structure or technique they like, as long as the focus is progress toward the Sprint Goal and a plan for the next day. The well-known "three questions" are one option, not a rule. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they take part as Developers.
The Daily Scrum is not a status report to the Scrum Master or a manager, and it is not the only time the Developers can adjust their plan. They can talk and re-plan at any time during the day.
Sprint Review (max 4 hours)
The Sprint Review inspects the outcome of the Sprint and decides on future adaptations. The Scrum Team presents the results of its work to key stakeholders, and together they discuss progress toward the Product Goal and what has changed in their environment. The Product Backlog may be adjusted to reflect new opportunities.
The Scrum Guide describes it as a working session and says the Scrum Team should avoid limiting it to a presentation. Two consequences matter for the exam:
- It is not a release gate. An Increment can be delivered to stakeholders as soon as it meets the Definition of Done, even before the Sprint Review. Nobody needs to wait for the Review to approve a release.
- Only Done work is shown. Work that does not meet the Definition of Done is not part of an Increment, cannot be presented at the Sprint Review, and goes back to the Product Backlog.
Sprint Retrospective (max 3 hours)
The Sprint Retrospective concludes the Sprint. Its purpose 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 its Definition of Done, then identifies the most helpful changes. The most impactful improvements are addressed as soon as possible and may even be added to the Sprint Backlog for the next Sprint.
What if an event finishes early or runs short?
Because a timebox is a maximum, an event can end as soon as its purpose is achieved. A Sprint Planning that produces a clear Sprint Goal and a workable plan in three hours is fine. A 15-minute Daily Scrum that finishes in eight minutes is fine.
The opposite case matters more: an event should not run past its timebox. If Sprint Planning keeps overrunning, that is a signal to inspect. Perhaps the Product Backlog items are not refined enough, or the meeting is drifting from its three topics. The Scrum Master helps the team make sure events take place, are positive and productive, and are kept within the timebox.
For Sprints shorter than one month, the guide says the events are usually shorter. It does not give a formula, so do not expect an exam question that asks you to calculate an exact figure for a two-week Sprint. The known numbers are the one-month maximums.
Why Product Backlog refinement is not an event
Refinement is the act of breaking down and further defining Product Backlog items into smaller, more precise items, adding details such as description, order and size. The Scrum Guide 2020 treats it as an ongoing activity, not an event, so it has no timebox and no fixed meeting.
Older versions of the guide suggested refinement usually took no more than 10% of the Developers' capacity. That figure was removed in 2020, and the current guide gives no percentage. If an answer option quotes "10% of capacity" as a rule, it is out of date.
Scrum events exam questions people usually get wrong
- "How many Scrum events are there?" Five. The Sprint counts as an event and is the container for the other four. Refinement is not one of them.
- "Who must attend the Daily Scrum?" It is for the Developers. The Scrum Master does not have to run it or be present, and the Product Owner attends only as a Developer if working on Sprint Backlog items.
- "Is the Sprint Review where the Product Owner approves the release?" No. It is a working session to inspect the Increment and adapt the Product Backlog. Releases can happen whenever an Increment is Done.
- "Can the Scrum Master cancel the Sprint?" No. Only the Product Owner can, when the Sprint Goal becomes obsolete.
- "Can you extend a Sprint to finish the work?" No. The Sprint has a fixed length. Unfinished items go back to the Product Backlog.
- "What is the timebox for a two-week Sprint Planning?" The guide only fixes the maximum for a one-month Sprint (8 hours) and says shorter Sprints usually have shorter events.
If you want to check how well these rules have stuck, try the free PSM practice exam on Scrumdemy: 20 questions in 20 minutes, with an 80% pass mark. For deeper practice, the Scrum Master certification training includes four timed exams with 316 questions.
FAQ
What are the 5 Scrum events?
The Sprint, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. The Sprint contains the other four.
What are the Scrum timeboxes for a one-month Sprint?
Sprint Planning has a maximum of 8 hours, the Daily Scrum 15 minutes, the Sprint Review 4 hours and the Sprint Retrospective 3 hours. The Sprint itself lasts one month or less.
Is Product Backlog refinement a Scrum event?
No. In the Scrum Guide 2020, refinement is an ongoing activity with no timebox, and the old guideline of 10% of capacity was removed.
Who can cancel a Sprint?
Only the Product Owner, and only when the Sprint Goal becomes obsolete.