The Four Scrum Ceremonies Explained

Scrum has four ceremonies (now called events): Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective. Learn the purpose, timebox, and attendees of each.

The four Scrum ceremonies are Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective. Each one has a clear purpose, a fixed timebox, and a defined set of attendees, and together they give a Scrum team its regular rhythm of planning, coordinating, demonstrating, and improving.

A quick note on names: the current Scrum Guide calls these meetings events rather than ceremonies, and it counts five — because the Sprint itself is the container that holds the other four. Most teams still say “ceremonies” out of habit, and this chapter uses the two words interchangeably. What matters is not the label but understanding what each meeting is for.

What is a Scrum ceremony?

A Scrum ceremony is a regular, timeboxed meeting that gives a Scrum team a predictable structure for its work. Rather than calling meetings ad hoc, the team agrees a fixed set of ceremonies that recur every Sprint. This consistency is the point: it removes the overhead of deciding when to meet, it makes sure the important conversations actually happen, and it creates the cadence of inspect and adapt that Scrum is built on.

The Sprint is a fixed-length period of work — usually one to four weeks, most often two — and the four ceremonies bookend and punctuate it. Planning opens the Sprint, the Daily Scrum keeps it on track, and the Review and Retrospective close it.

The four Scrum ceremonies

1. Sprint Planning

Purpose: to agree what the team will deliver in the coming Sprint and how. The team selects items from the Product Backlog, shapes a Sprint Goal, and forms an initial plan for the work.

Timebox: up to about four hours for a two-week Sprint (longer for a longer Sprint).

Who attends: the whole Scrum Team — the Developers, the Product Owner, and the Scrum Master.

Sprint Planning answers three questions: why is this Sprint valuable (the Sprint Goal), what can be done this Sprint, and how will the chosen work get done. Sizing the selected items is part of this conversation — many teams use Planning Poker, a free agile estimation tool, to reach a shared estimate quickly.

2. The Daily Scrum

Purpose: a short daily check-in for the Developers to inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours. It is about coordination, not status reporting to a manager.

Timebox: 15 minutes, every working day, regardless of Sprint length.

Who attends: the Developers. The Product Owner and Scrum Master attend if they are working on Sprint Backlog items.

The Daily Scrum is also known as the daily stand-up, a name that comes from the habit of holding it standing up to keep it short.

3. The Sprint Review

Purpose: to inspect the outcome of the Sprint and decide what to do next. The team demonstrates the work it has completed and gathers feedback from stakeholders, which may lead to adjusting the Product Backlog.

Timebox: up to about two hours for a two-week Sprint.

Who attends: the Scrum Team plus key stakeholders invited by the Product Owner.

The Sprint Review is a working session, not a one-way presentation — its value is the conversation and feedback it produces.

4. The Sprint Retrospective

Purpose: to inspect how the last Sprint went in terms of people, relationships, process, and tools, and to plan improvements for the next Sprint. Where the Review looks at the product, the retrospective looks at the way the team works.

Timebox: up to about 90 minutes for a two-week Sprint.

Who attends: the Scrum Team.

The retrospective is the team’s main engine of continuous improvement — it is where the team turns reflection into a short list of concrete actions. The rest of this guide is dedicated to running it well; start with Chapter 1 — What is a sprint retrospective? for a full breakdown, and see how to choose a retrospective template when you are ready to run one.

How the ceremonies fit together

The four ceremonies form a loop. Sprint Planning sets the direction, the Daily Scrum keeps the team coordinated day to day, the Sprint Review checks the product against stakeholder needs, and the Sprint Retrospective improves the team itself — feeding directly back into the next round of planning. Run consistently, this loop is what lets a Scrum team inspect and adapt rather than repeat the same mistakes Sprint after Sprint.

Frequently asked questions about Scrum ceremonies

What are the four Scrum ceremonies?

The four Scrum ceremonies are Sprint Planning, the Daily Scrum (or daily stand-up), the Sprint Review, and the Sprint Retrospective. Together they create a regular rhythm of planning, coordinating, demonstrating, and improving across every Sprint. The Sprint itself is sometimes counted as a fifth event because it is the container that holds the other four.

Are Scrum ceremonies the same as Scrum events?

Yes. “Ceremony” is the older, informal word and “event” is the term used in the current Scrum Guide, but they refer to the same set of meetings. You will hear teams use both interchangeably for Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective.

How long should each Scrum ceremony take?

Timeboxes scale with the length of the Sprint. For a typical two-week Sprint, Sprint Planning runs up to about four hours, the Daily Scrum is 15 minutes, the Sprint Review runs up to about two hours, and the Sprint Retrospective runs up to about 90 minutes. A one-month Sprint roughly doubles the planning, review, and retrospective timeboxes; the Daily Scrum stays at 15 minutes regardless of Sprint length.

Is the Sprint Retrospective a Scrum ceremony?

Yes. The Sprint Retrospective is one of the four Scrum ceremonies and the last event of each Sprint. It is the team’s dedicated opportunity to inspect how the last Sprint went — people, process, and tools — and to agree on concrete improvements for the next one. The other three ceremonies focus on the work; the retrospective focuses on the way the team works.