The Five Scrum Events: Purpose, Participants, and Timeboxes
Introduction
The five Scrum events give teams a regular way to plan, inspect results, and act on what they learn. If a payment feature is behind schedule, the Developers can adapt their plan during the Sprint. At the Sprint Review, stakeholders can help evaluate the outcome. At the Retrospective, the team can address a problem in how it works. Each event answers a different question.
This PSM I lesson covers the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective in the Understanding and Applying the Scrum Framework focus area. You will identify each event’s purpose, participants, and timebox, and decide what to do when the Sprint Goal is at risk.
Learning objectives
- Describe the Sprint as a container event and explain why its length is fixed.
- Explain the three topics of Sprint Planning and who contributes to each.
- Run, or recognise a correct, Daily Scrum, including who owns it and what it is for.
- Distinguish the Sprint Review (inspect the Increment and adapt the Product Backlog) from the Sprint Retrospective (inspect the way of working and adapt it).
- State the timeboxes for a one-month Sprint and explain what changes for a shorter Sprint.
- Explain who can cancel a Sprint and when it makes sense.
1. The Sprint: the container for everything else
A Sprint lasts a fixed period of one month or less. The next Sprint starts immediately after the previous one ends. Sprint Planning, Daily Scrums, the Sprint Review, the Sprint Retrospective, and the work toward the Product Goal all take place within Sprints.
Keep the Sprint Goal safe and maintain the quality standard. Refine the Product Backlog when needed. If the team learns that its initial forecast needs to change, the Developers discuss the selected scope with the Product Owner and update their plan. This regular cadence makes transparency, inspection, and adaptation part of day-to-day work.
Why a fixed length?
A fixed length lets the team compare Sprints, forecast with data, and avoid endless planning. A shorter Sprint can help a team learn sooner and limit the time and cost committed before the next review. When a Sprint is too long, the definition of what is being built may change, complexity may rise, and risk may increase. A Sprint may be seen as a short project, but it is not a mini-waterfall: planning, design, build and test are not phases; they overlap throughout the Sprint.
Sprint length is a decision of the Scrum Team. It can be changed between Sprints (for example, from four weeks to two weeks) but never in the middle of a Sprint to "make room" for unfinished work. A common trap on the exam: "extend the Sprint by two days because the work is not done". This is never correct. When the Sprint reaches its planned end, unfinished items return to the Product Backlog for future consideration.
Example: a Sprint that does not slip
A team of seven builds an online ticketing product with two-week Sprints. On the last Monday, three items are still open. A manager suggests adding three days. The Scrum Master explains that the timebox is what produces the fast feedback the company wanted. The team presents the Increment that is actually Done at the Sprint Review. The three unfinished items return to the Product Backlog, where the Product Owner reorders them. Velocity data and the Retrospective help the team understand why the forecast was too optimistic.
Cancelling a Sprint
Only the Product Owner can cancel a Sprint if its goal becomes obsolete. A decision to abandon the product feature or market the goal serves may make the goal obsolete. A delay alone usually calls for adapting the plan or scope.
The 2020 Scrum Guide gives no separate cancellation checklist. Work that already meets the Definition of Done remains usable. Reassess unfinished work against the Product Backlog and use the usual Sprint Planning process for the next Sprint.
2. Sprint Planning
Sprint Planning starts the Sprint. The Scrum Team creates a plan together. The Product Owner prepares people to discuss the most important Product Backlog items and how they serve the Product Goal. The team can invite others for advice. The timebox is up to eight hours for a one-month Sprint and is usually shorter for a shorter Sprint.
Topic one: why is this Sprint valuable?
The Product Owner proposes a direction for value. The Scrum Team agrees on a Sprint Goal before Planning ends.
Topic two: what can be Done this Sprint?
The Developers discuss the work with the Product Owner and select what they reasonably expect to finish. Consider capacity, earlier results, dependencies, and the Definition of Done. The team may clarify items as it plans.
Topic three: how will the chosen work get done?
The Developers decide how to turn the selected items into a usable Increment that meets the Definition of Done. Smaller tasks can help them plan, and the team chooses how to break up the work.
The outcome: the Sprint Backlog
The goal, selected items, and delivery plan together make the Sprint Backlog. Compare it with the other Scrum artifacts and their commitments.
Comparison: who does what in Sprint Planning
| Question | Who decides | Notes |
|---|---|---|
| Which value should this Sprint pursue? | Product Owner proposes, the Scrum Team agrees on the Sprint Goal | Collaborative, but the Product Owner brings the product perspective |
| How many items fit into the Sprint? | Developers | The Product Owner cannot push extra items in |
| How will the work be done? | Developers | Task breakdown is optional and is the Developers' choice |
| Who ensures the event takes place? | Scrum Master | The Scrum Master helps the team use the timebox effectively. The team can share facilitation. |
| Who may be invited? | The Scrum Team, for advice | Guests do not decide |
Example: forecasting with real numbers
The Product Owner of a travel app proposes the goal "customers can rebook a cancelled flight in one flow". The Developers know from the past three Sprints that they completed 7, 9 and 8 items of similar size. Two Developers will be on holiday for three days this Sprint. They select seven items and revisit the forecast once they understand the capacity impact and API dependency. They split each item into pieces of a day or less, and during the discussion discover that one item depends on an unreliable airline API. They agree with the Product Owner to replace it with a smaller item that still serves the Sprint Goal. This is exactly what the guide means by negotiating scope without endangering the Sprint Goal.
3. The Daily Scrum
The Daily Scrum gives the Developers 15 minutes each working day to check their progress toward the Sprint Goal and adapt their plan. Keeping the time and place consistent simplifies coordination. If the Product Owner or Scrum Master is working on a Sprint Backlog item, they take part as a Developer.
The Developers choose a format that helps them agree on actionable next steps. For instance, they can start with work closest to Done and identify where someone needs help. The familiar three questions are optional. The Developers can update their plan again during the day as new information arrives.
The Scrum Master ensures the event takes place and helps the Developers keep it effective and within the timebox. The Developers conduct it and coordinate their work.
Example: a Daily Scrum that drifted
Eight Developers hold a 40-minute standing meeting where each person talks to the Scrum Master about hours spent. The Scrum Master recognises two problems: the event is far beyond its timebox and has become a status report. The Scrum Master coaches the Developers to talk to each other, using the Sprint Backlog board and the Sprint Goal. Detailed technical discussions move to follow-up conversations right after the 15 minutes, between the people who need them. The meeting returns to 15 minutes and the team starts finding blockers earlier.
4. The Sprint Review
At the Sprint Review, the Scrum Team and key stakeholders inspect the Sprint outcome and discuss progress toward the Product Goal. They consider what changed for users, in the market, or in the organization, and decide what to do next. The Product Owner may adjust the Product Backlog after the discussion.
The Review is a working session. Give stakeholders something usable to inspect and time to discuss their observations. The Review takes place before the Retrospective and has a four-hour maximum for a one-month Sprint. A usable Increment can be delivered before the Review.
Example: from demonstration to decision
A Scrum Team building a hospital scheduling product invites two nurses, a hospital IT director and a compliance officer. After a short demonstration, nurses try the new shift-swap screen themselves. They report that the confirmation step hides the date. The Product Owner immediately creates a Product Backlog item and orders it high. The compliance officer points to a new national regulation affecting how overtime is recorded; the Product Owner reorders the backlog around it. Nothing in this meeting was a "sign-off". It was inspection followed by adaptation of the Product Backlog.
5. The Sprint Retrospective
At the Sprint Retrospective, the Scrum Team examines its work, including collaboration, tools, and the Definition of Done, to find changes that would improve quality and effectiveness. The team acts promptly on the most useful changes and may add one to its next Sprint Backlog.
The Retrospective closes the Sprint. Its timebox is up to three hours for a one-month Sprint. The whole Scrum Team takes part, including the Product Owner and Scrum Master.
Sprint Review and Sprint Retrospective compared
| Aspect | Sprint Review | Sprint Retrospective |
|---|---|---|
| Purpose | Inspect the Sprint outcome and decide what to do next | Inspect how the team worked and plan improvements |
| Participants | Scrum Team and key stakeholders | Scrum Team only |
| Focus | The product | The team and its system of work |
| Typical output | Updated Product Backlog, shared understanding of next steps | Concrete improvement actions, possibly in the next Sprint Backlog |
| Maximum length (one-month Sprint) | 4 hours | 3 hours |
| Position in the Sprint | Second to last event | Last event |
Example: a Retrospective that produced a real change
For three Sprints in a row, a payment product has had two items that remain "almost done" at the end of the Sprint. In the Retrospective, the Developers notice that all testing is concentrated in the last two days because code reviews wait for one senior colleague. They agree to pair on reviews, try a one-day review turnaround as a workflow experiment and put one of the improvements in the next Sprint Backlog. At the next Retrospective, they compare review waiting times and the number of Done items with earlier Sprints before deciding whether to keep the experiment.
6. Worked example: what should the Scrum Master do?
Statement. Day 6 of a ten-day Sprint. The Sprint Goal is "customers can pay with a saved card". The Developers learn that the card provider will retire the API they depend on after this Sprint. A stakeholder suggests cancelling the Sprint and starting over. The Product Owner is unsure. Three Developers would like to add two days to the Sprint to switch providers. What should the Scrum Team do?
Reasoning, step by step.
- Is the Sprint Goal obsolete? Not necessarily. The customer value (pay with a saved card) is still valid; only the technical route changes. Feasibility affects the plan. The value of the goal is what matters when considering cancellation.
- Only the Product Owner can cancel the Sprint, and only when the Sprint Goal is obsolete. Here it is not obsolete, so cancellation is not justified.
- Can the Sprint be extended? No. The Sprint is fixed-length. Extending would break the timebox and the regularity of events.
- What can be done? Scope can be renegotiated between the Developers and the Product Owner as more is learned, without endangering the Sprint Goal. The Developers re-plan their work, adjust the Sprint Backlog and, if needed, the Product Owner agrees to remove lower value items.
Solution. Keep the Sprint going, let the Developers adapt the Sprint Backlog, and renegotiate scope with the Product Owner to protect the Sprint Goal. Raise the API retirement as a high-priority item on the Product Backlog.
Why the other choices are worse. Cancelling is wasteful because the goal is still valid. Extending the Sprint breaks the fixed length. Asking stakeholders to decide takes decision rights from the Product Owner and Developers. Ignoring the problem until the Review leaves the information uninspected for the rest of the Sprint.
7. Common pitfalls and exam tips
- Sprint Planning topics. Remember "why, what, how". The Sprint Goal is created during Sprint Planning and the Sprint Backlog is the output.
- Daily Scrum participation. The Developers use it to inspect and adapt. A Product Owner or Scrum Master who is working on a Sprint Backlog item participates as a Developer. The Scrum Master helps the event serve its purpose and stay within 15 minutes.
- Timeboxes (one-month Sprint): Sprint Planning 8 h, Sprint Review 4 h, Sprint Retrospective 3 h, Daily Scrum 15 min. Planning, Review, and Retrospective are usually shorter for shorter Sprints. The Daily Scrum keeps its 15-minute timebox. The Sprint itself is one month or less.
- Stand-up questions. The three standard questions are optional in the current guide.
- Sprint Review is not a demo for approval. The Increment can be released earlier, during the Sprint, without waiting for the Review.
- Sprint Retrospective is not for stakeholders. It is for the Scrum Team to improve itself.
- Early end of an event. An event can end before the timebox if its purpose is achieved; the timebox is a maximum, not a target. Do not stretch events to fill time.
- Cancelling. Only the Product Owner can cancel and only if the Sprint Goal is obsolete.
- No "Sprint 0" or "hardening Sprint". These are not part of Scrum. Work in a Sprint should result in a Done Increment.
- Exam tip: when a question asks about "the best next step" and an answer says "change the length of the current Sprint" or "add a mandatory sign-off by management", it is almost always a distractor.
8. Mini case study
Situation. A Scrum Team of nine builds a mobile banking app with three-week Sprints. In the last three Sprints:
- Sprint Planning regularly lasts a full day, because the Product Owner arrives with 40 unrefined items and Developers estimate each one in detail.
- The Daily Scrum is held at 10:00, 10:20 or 11:00, depending on the Scrum Master's calendar, and takes 30 minutes. The department head attends to get a status update.
- The Sprint Review is a 90-minute slide show with no stakeholders other than the department head.
- The Retrospective is skipped when the Sprint is busy.
- The product has not been released in nine weeks because "the Review has to approve it first".
Questions. (1) Which problems do you identify? (2) What would you do as Scrum Master?
Commented solution.
- Sprint Planning problems: The Product Backlog is not refined, so planning takes far too long. The Product Owner is accountable for being ready to discuss the most important items; the Scrum Team should refine items during the Sprint and use Sprint Planning to forecast, not to estimate everything. The event has a maximum of 8 hours for a one-month Sprint and is usually shorter for a three-week Sprint; it ends when its purpose is reached.
- Daily Scrum problems: Same time and place reduce complexity, the Developers should own the event, and it should last 15 minutes. The department head is a spectator who turns the event into a status report. The Scrum Master teaches the Developers to hold it themselves and politely asks the head to use the Sprint Review or the Sprint Backlog for transparency.
- Sprint Review problems: It should be a working session with the relevant stakeholders (users, sponsors, compliance), where the working Increment is inspected and the Product Backlog adapted. Invite real users and replace slides with the running product.
- Retrospective problems: Skipping it removes the formal chance to improve. It is the Scrum Master's accountability to ensure it takes place. The busiest Sprints are exactly where improvement is needed.
- Release problem: An Increment that meets the Definition of Done can be delivered before the Sprint Review when the organization’s release requirements are met. The team can still discuss the release and its effects at the Review.
Scrum Master actions. Coach, do not command: share the Scrum Guide text, run a short workshop on the purpose of each event, ask the Product Owner to start a regular refinement cadence, invite stakeholders to the Review, and propose that the next Retrospective focuses on the team's own events.
Key terms
- Sprint: fixed-length event of one month or less that contains all other events and the work.
- Sprint Goal: the single objective for the Sprint; commitment of the Sprint Backlog.
- Sprint Planning: event that defines why, what and how for the Sprint.
- Daily Scrum: 15-minute event for Developers to inspect progress toward the Sprint Goal.
- Sprint Review: event to inspect the outcome of the Sprint with stakeholders and adapt the Product Backlog.
- Sprint Retrospective: event for the Scrum Team to improve quality and effectiveness.
- Timebox: maximum duration of an event.
- Cancellation: ending the Sprint early, allowed only when the Sprint Goal is obsolete, decided by the Product Owner.
Summary checklist
- Sprints are one month or less, fixed in length, and a new one starts immediately after the previous one.
- Nothing endangers the Sprint Goal; quality does not decrease; scope can be renegotiated.
- Only the Product Owner can cancel a Sprint, and only if the Sprint Goal is obsolete.
- Sprint Planning answers why, what and how; maximum 8 hours for a one-month Sprint.
- Developers select the work and decide how to do it.
- Daily Scrum: 15 minutes, Developers, same time and place, focus on the Sprint Goal.
- Sprint Review: working session with stakeholders. Maximum 4 hours for a one-month Sprint. The Product Backlog may change as a result.
- Sprint Retrospective: the Scrum Team plans improvements and closes the Sprint. Maximum 3 hours for a one-month Sprint.
- Events end when their purpose is achieved; the timebox is a maximum.
Sources
- The Scrum Guide (November 2020), Ken Schwaber and Jeff Sutherland, CC BY-SA 4.0: https://scrumguides.org/scrum-guide.html (opens in a new tab)
- Scrum.org, Professional Scrum Master I assessment: https://www.scrum.org/assessments/professional-scrum-master-i-certification (opens in a new tab)
- Scrum.org, which Scrum events are timeboxed: https://www.scrum.org/resources/blog/which-scrum-events-are-time-boxed (opens in a new tab)
