Skip to content
Tutorials Center
My learning

Topics

Lesson 7 of 29 ยท The Scrum Framework

Scrum Events

Learn the five Scrum events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review and Retrospective, with time-boxes, goals and common mistakes.

Scrum events are the scheduled moments where the team and its stakeholders inspect what has happened and adapt what comes next. There are five: the Sprint itself, which contains the other four, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. Every event is a formal opportunity to inspect and adapt something specific, and every event is time-boxed, meaning it has a maximum length that cannot be exceeded.

Time-boxes matter for a practical reason. They make the rhythm regular, so everyone can plan around it, and they force a conversation to focus. A meeting with no end time expands to fill the day. This lesson explains the purpose of each event, how long it should last, who attends and the typical mistakes. It builds on Scrum at a Glance and Scrum Roles.

The Sprint and its four events

Sprint Planning Choose why, what and how.
Daily Scrum Plan the next 24 hours.
Sprint Review Show the Increment, gather feedback.
Retrospective Improve how the team works.

All of them happen inside one Sprint of a month or less.

1 / 2

The Sprint

The Sprint is the heartbeat of Scrum, a fixed length of one month or less during which an Increment of value is made. A new Sprint starts right after the previous one ends, so there are no gaps. Choose a length that lets you learn quickly without too much overhead; two weeks is the most common, and a shorter Sprint is a good choice when there is much uncertainty because it limits cost and risk.

During the Sprint:

  • No change is made that would endanger the Sprint Goal.
  • Quality does not decrease; the Definition of Done is respected.
  • The Product Backlog is refined as needed, which means breaking items down and clarifying them.
  • Scope may be clarified and renegotiated with the Product Owner as more is learned.

A Sprint can be cancelled before its time-box ends, but only by the Product Owner, and only if the Sprint Goal becomes obsolete (for example, the company changes direction). Cancellations are rare and disruptive.

Sprint Planning

Sprint Planning starts the Sprint. The whole Scrum Team collaborates on the plan for the Sprint, and it addresses three topics.

  1. Why is this Sprint valuable? The Product Owner proposes how the product could increase its value in this Sprint, and the whole team collaborates to define a Sprint Goal: one sentence that explains the purpose of the Sprint and that must be finalized before the end of Planning.
  2. What can be done this Sprint? The Developers select items from the Product Backlog, talking with the Product Owner. They use what they know about their past performance, the capacity they expect and the Definition of Done to judge how much they can take.
  3. How will the chosen work get done? The Developers plan the work needed to create an Increment for each selected item. How they do this is entirely up to them. The items plus the Sprint Goal plus this plan make up the Sprint Backlog.

The maximum length is eight hours for a one-month Sprint, and usually shorter for shorter Sprints. The Scrum Team may invite others to give advice.

A good Sprint Goal is a single, coherent objective: "Customers can find products by name and price" is better than "Do tickets 101 to 117". It gives the team flexibility, because they can renegotiate which items to deliver while still serving the goal.

Daily Scrum

The Daily Scrum is a 15-minute event for the Developers, held at the same time and place every working day of the Sprint to reduce complexity. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.

How it is run is up to the Developers, as long as it focuses on progress toward the Sprint Goal and produces an actionable plan for the next day. Some teams go through each person's yesterday, today and blockers; others walk the board from right to left to see what can be pulled over the line; others ask "what is the most important thing we can do today to move toward the goal?". Any of these can work.

Benefits include better communication, quicker identification of impediments, faster decisions and less need for other meetings. If a longer discussion is required, it takes place right after the Daily Scrum, with only the people involved.

Common mistakes:

  • A status report to the Scrum Master or a manager. The Daily Scrum is for the Developers themselves.
  • Going over 15 minutes. The time-box exists for a reason; take detailed discussion offline.
  • No link to the Sprint Goal. Reciting tasks without asking whether the goal is still on track misses the point.

The Scrum Master ensures that the event happens and stays in the time-box but does not need to attend unless they are also working on Sprint Backlog items. The Product Owner is welcome to attend, but Scrum does not make them part of it.

Sprint Review

At the end of the Sprint comes the Sprint Review. The purpose is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of its work to key stakeholders and progress toward the Product Goal is discussed.

During the event, the team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may be adjusted to meet new opportunities. The Review is a working session, not a one-way presentation or a formal sign-off, and the Scrum Guide discourages limiting it to a slide show.

The maximum length is four hours for a one-month Sprint. A typical flow: the Product Owner states what is done and what is not; Developers demonstrate the working Increment and talk about problems and how they were solved; stakeholders give feedback; the group discusses the market, budget and timeline for upcoming releases and what the best next items might be.

Sprint Retrospective

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 the Definition of Done. Inspected elements often differ by domain. Assumptions that led the team astray are identified and their origins explored. The team discusses what went well, what problems it ran into and how those were (or were not) solved.

The team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible and may even be added to the Sprint Backlog for the next Sprint.

The maximum length is three hours for a one-month Sprint. Because it concerns the team itself, it is typically a safe space: the same openness that Scrum values demands that a retrospective not be used to assign blame or to evaluate individuals. Many teams use a structured format, such as "start, stop, continue" or "what went well, what to improve, what puzzles us", and rotate the format now and then to keep it fresh.

A retrospective that ends with a list of complaints and no concrete action has not done its job. A strong sign of a useful retrospective is one or two small, specific changes the team agrees to try next Sprint and checks at the next retrospective.

Time-boxes at a glance

Event Who attends Maximum for a one-month Sprint
Sprint The Scrum Team 1 month or less
Sprint Planning Scrum Team (others by invitation) 8 hours
Daily Scrum Developers 15 minutes per day
Sprint Review Scrum Team and stakeholders 4 hours
Sprint Retrospective Scrum Team 3 hours

For shorter Sprints, the events are usually shorter. The calculator below applies a simple rule, scaling the one-month maxima by the Sprint length, and adds up how much time each person spends in events. The 15-minute Daily Scrum is the same on every day. The scaling is a convention many teams use, not a rule in the Scrum Guide.

JS Time-box calculator

Press Run (or Ctrl + Enter) to see the console output here.

No output.

In this model the events use at most about an eighth of a person's time whatever the Sprint length. That is the maximum, and many teams use less. The numbers also show why very short Sprints are not free: the Daily Scrum cost per day is constant, and a one-week Sprint spends the same share on ceremonies as a month-long one, so the overhead needs to be worth the feedback it buys.

A two-week Sprint calendar

Where do the events fall in a typical two-week Sprint? The second model builds a calendar from a start date, places Planning on day one, a Daily Scrum on every working day, and the Review and Retrospective on the last day. It skips weekends. The dates and the day order are examples; teams choose their own schedule, for instance starting on a Wednesday so that Planning does not land on a Monday morning after a weekend.

JS A two-week Sprint calendar

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notice that the next Sprint starts on the next working day after the last one ends. There is no break for "planning week" and no gap for releases. Anything that needs to happen between Sprints belongs inside a Sprint.

A frequent anti-pattern is to treat the Review as a demo for management to "accept" the work, and the Retrospective as a place to avoid saying uncomfortable things. Both events lose their value. The Review is for gathering feedback to steer the product, and the Retrospective is for the team to change itself.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. What is the maximum length of the Daily Scrum?

    The Daily Scrum is time-boxed to 15 minutes, regardless of the Sprint length. Longer discussions happen afterward with the people who need them.
  2. 2. Which event's purpose is to inspect the outcome of the Sprint with stakeholders and decide what to adapt?

    The Sprint Review is where the team and stakeholders inspect the outcome and discuss future adaptations. The Retrospective is about the team's own way of working.
  3. 3. Who may cancel a Sprint, and when?

    Only the Product Owner has the authority to cancel a Sprint, and normally only when the Sprint Goal no longer makes sense.
  4. 4. Which of the three topics is NOT part of Sprint Planning?

    Planning covers why (the Sprint Goal), what (selected items) and how (the plan). Blame has no place in Scrum, and reflection belongs to the Retrospective.
  5. 5. A Retrospective ends with a long list of complaints and no action. What is missing?

    The purpose of the Retrospective is to plan ways to increase quality and effectiveness, so it should produce specific changes to try and check.

Summary

  • The Sprint (one month or less) is the container; Planning, Daily Scrum, Review and Retrospective happen inside it, and each is time-boxed.
  • Sprint Planning covers why (Sprint Goal), what (selected items) and how (the plan); the maximum is 8 hours for a month.
  • The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the plan.
  • The Sprint Review is a working session with stakeholders (max 4 hours); the Retrospective is the team's chance to improve (max 3 hours).
  • Shorter Sprints usually have shorter events, and a new Sprint begins right after the previous one ends.
  • Common mistakes: status-report Dailies, demo-only Reviews and Retrospectives with no concrete action.

Next, learn what the team produces and commits to in Scrum Artifacts and Commitments.