What are the five events of Scrum, and what is each one for?
answer
- Five events, and one contains the rest
- Each pairs an inspection with an adaptation
- One opens the Sprint, one repeats daily
- Two close it: outcome first, then process
basics
~20 sScrum defines five events: the Sprint, which contains the other four, plus Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. Each is a fixed opportunity to inspect something and adapt something as a result.
solid answer
~50 sScrum has five events. The **Sprint** is a fixed-length container of one month or less; the other four happen inside it, and a new Sprint starts as soon as the previous one ends. **Sprint Planning** opens the Sprint by answering three questions - why this Sprint is valuable, what can be finished, and how the work will get done - producing the Sprint Goal and the Sprint Backlog. The **Daily Scrum** is a fifteen-minute event in which the Developers inspect progress toward the Sprint Goal and re-plan the next working day. The **Sprint Review** inspects the outcome with stakeholders and adapts the Product Backlog. The **Sprint Retrospective** closes the Sprint by inspecting how the team worked and choosing improvements. Every one of the four pairs an inspection with an adaptation, and that pairing is the point of holding it.
code
pseudocode · 6 linesSPRINT (fixed length, one month or less)
day 1 Sprint Planning -> Sprint Goal + Sprint Backlog
every day Daily Scrum -> plan for the next working day
last day Sprint Review -> adapted Product Backlog
last day Sprint Retrospective -> improvements for next Sprint
next day the following Sprint starts, with no gapgo deeper
Be ready to name all five events without hesitation, the Sprint included, and give one sentence on the purpose of each. Getting the count wrong is the fastest way to lose a screening question you had otherwise answered.
Explain what each event inspects and what it adapts, and give the caps for a one-month Sprint. An interviewer at this level expects you to separate the Sprint Review from the Sprint Retrospective without being prompted.
Show what you do when an event stops producing its adaptation: a Review that changes no Product Backlog item, Planning that ends with no Sprint Goal. Describe the diagnosis and the repair, not the definition.
Own Sprint length as a first-class decision. Be ready to argue what a shorter Sprint buys in learning and in limiting risk, what fraction of the Sprint its own events then consume, and how you would tell which length fits a given product.
## Five events, one of which contains the rest Scrum defines five events and no others. Four of them - Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective - happen inside the fifth, the **Sprint**, which is a fixed-length period of one month or less. Candidates who list four have usually forgotten that the Sprint is itself an event, and the omission matters: it is the Sprint's fixed boundary that makes the other four recur on a predictable rhythm instead of happening whenever somebody books a room. A new Sprint begins immediately after the previous one concludes. There is no gap, no cool-down week and no planning interval between them, so the Retrospective of one Sprint and the Planning of the next sit back to back. ## What each event is for | Event | Purpose | It inspects | It adapts | Cap for a one-month Sprint | | --- | --- | --- | --- | --- | | Sprint | Contain everything needed to produce a usable Increment | - | - | One month or less, fixed | | Sprint Planning | Open the Sprint with a goal and a plan | The Product Backlog and the team's capacity | The Sprint Backlog | Eight hours | | Daily Scrum | Produce the next working day's plan | Progress toward the Sprint Goal | The Sprint Backlog | Fifteen minutes | | Sprint Review | Inspect the outcome with stakeholders | The Increment and what changed outside the team | The Product Backlog | Four hours | | Sprint Retrospective | Improve how the team works | People, interactions, processes and tools | The team's own way of working | Three hours | For Sprints shorter than a month, the Planning, Review and Retrospective caps are usually shorter in proportion. The Daily Scrum stays at fifteen minutes whatever the Sprint length, because its subject is one day of work either way. ## Sprint Planning answers three questions 1. **Why is this Sprint valuable?** The Product Owner proposes how the product could increase in value, and the whole Scrum Team agrees a **Sprint Goal** - a single statement of the outcome the Sprint is pursuing. 2. **What can be Done this Sprint?** The Developers select items from the Product Backlog that they believe they can finish, in conversation with the Product Owner. 3. **How will the chosen work get done?** The Developers decompose the selected items far enough to be confident they can start. The combined output is the **Sprint Backlog**: the goal, the selected items, and the plan for delivering them. ## Every event is an inspect-and-adapt pair The framework rests on empirical process control, and each event exists because something must be looked at and something must change as a result: - Sprint Planning inspects the ordered Product Backlog and adapts it into a Sprint Backlog with a goal attached. - The Daily Scrum inspects progress toward the Sprint Goal and adapts the Sprint Backlog, often re-ordering who does what before anyone starts the day. - The Sprint Review inspects the Increment plus everything that changed outside the team during the Sprint, and adapts the Product Backlog. - The Sprint Retrospective inspects how the team worked and adapts the way it will work next Sprint. - The Sprint itself is the outer loop: it guarantees all four happen at least once a month. If you can name the pair for an event, you can reconstruct its purpose without memorising a definition. An event that produces no adaptation did not do its job, however tidily it ran. ## What is not one of the five - **A separate demo meeting.** The Sprint Review already includes showing the work; a second showcase splits the audience from the people who order the Product Backlog. - **Backlog refinement.** It is an ongoing activity that runs through the Sprint, not a sixth event with a defined slot. - **A sprint zero, or a hardening sprint.** Neither exists in the framework; every Sprint is expected to produce a usable Increment. - **Release planning, or a status meeting with management.** Teams may hold these, but they are local inventions and Scrum makes no claims about them. ## The confusions interviewers listen for The most common is collapsing the **Sprint Review** and the **Sprint Retrospective** into one meeting. They inspect different subjects: the Review looks outward at the product with stakeholders present, while the Retrospective looks inward at the team's own way of working. The second is describing the Daily Scrum as a status round for a manager, when it belongs to the Developers and its output is a plan. The third is believing the Sprint ends when the selected items are finished - the Sprint ends on its date, and whatever is unfinished returns to the Product Backlog to be re-ordered.
- What is the difference between the Sprint Review and the Sprint Retrospective?The Sprint Review inspects the product: the Scrum Team and stakeholders look at what was built, discuss what changed outside the team, and adapt the Product Backlog together. The Sprint Retrospective inspects the team: how people, interactions, processes and tools worked during the Sprint, and which changes would make the next Sprint better. Different subject, different attendees, different output.
- Scrum caps each event. What are those limits for a one-month Sprint?Sprint Planning is capped at eight hours, the Sprint Review at four and the Sprint Retrospective at three, while the Daily Scrum is fifteen minutes on every working day. For shorter Sprints the first three are usually shorter in proportion; the Daily Scrum stays at fifteen minutes. Each cap is a maximum rather than a duration to fill.
- A Sprint has just ended. When does the next one begin?Immediately. Scrum runs a continuous cadence with no gap between Sprints, so the Retrospective of one Sprint and the Planning of the next sit back to back. Teams that leave a slack week between Sprints lose the fixed rhythm that makes one Sprint comparable with the last, which is most of what the cadence was buying them.
The Sprint is the box the work ships in, and the other four events are the moments the lid comes off: once to pack it, daily to shift the load, once to show what is inside, and once to improve the packing.
saying these in an interview costs you the question
- Cannot name the Sprint itself as one of the five events
- Counts backlog refinement as a sixth Scrum event
- Treats the Sprint Review and the Sprint Retrospective as one meeting
- Calls the Daily Scrum a status meeting held for a manager
- Says a Sprint ends once the selected work is finished