Scrum ceremonies explained: all five events

Scrum structures team collaboration through five recurring events, often called ceremonies. Each has a defined purpose, a recommended timebox, and a specific set of participants. Understanding all five helps teams run sprints predictably and improve continuously.

Create a free planning poker session Guides

1. Sprint Planning

Sprint Planning opens every sprint. The team selects backlog items from the top of the Product Backlog, defines a Sprint Goal, and breaks selected items into tasks. The Scrum Guide recommends a maximum of eight hours for a four-week sprint, scaling proportionally for shorter sprints.

Sprint Planning has two parts: what the team will deliver (selecting and committing to a Sprint Goal) and how the team will do the work (breaking stories into tasks and estimating effort). Story point estimation using planning poker is the most widely-used method for the first part.

Tip: Use ScrumVote's free planning poker tool to run story point estimation during Sprint Planning — simultaneous card reveals prevent anchoring bias and speed up consensus.

2. Daily Scrum

The Daily Scrum is a 15-minute event held every working day of the sprint. Its sole purpose is to inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours. The Scrum Guide no longer prescribes the classic three questions (what did I do, what will I do, what's blocking me) — the format is up to the Developers.

Common anti-patterns: running the Daily Scrum as a status report to the Scrum Master or manager; going over 15 minutes; including discussions that could happen asynchronously. The Daily Scrum is for the Developers, not the stakeholders.

3. Sprint Review

The Sprint Review is held at the end of the sprint. The team demonstrates completed work to stakeholders and collects feedback. The Product Owner updates the Product Backlog based on what was learned. The Scrum Guide recommends a maximum of four hours for a four-week sprint.

A Sprint Review is not a demo for approval. It is a working session where the team and stakeholders inspect the Increment and collaborate on what to do next. Items that were not completed should not be demonstrated — they return to the Product Backlog.

4. Sprint Retrospective

The Sprint Retrospective is the last event of the sprint. The team inspects their own process — how they worked together, what tools and practices helped, and what held them back. The output is a small set of actionable improvements to try in the next sprint.

The Scrum Guide recommends a maximum of three hours for a four-week sprint. Common formats include Start/Stop/Continue, the 4Ls (Liked, Learned, Lacked, Longed for), and Mad/Sad/Glad. The key quality metric is whether identified improvements are actually implemented.

Backlog Refinement is not a formal Scrum ceremony in the Scrum Guide, but it is a widely-adopted practice. The team reviews upcoming Product Backlog items, adds detail, estimates complexity, and reorders based on priority. Well-refined backlog items make Sprint Planning faster and more accurate.

Tip: See our full guide on Backlog Refinement best practices for a step-by-step process.

Scrum ceremony timebox reference (2-week sprint)

The Scrum Guide defines maximum timeboxes for a four-week sprint. For a two-week sprint — the most common length — the recommended timeboxes are:

Sprint Planning: up to 4 hours
Daily Scrum: 15 minutes (fixed)
Sprint Review: up to 2 hours
Sprint Retrospective: up to 1.5 hours
Backlog Refinement: typically 1–2 hours per sprint (team discretion)

These are maximums, not minimums. A well-prepared team often completes Sprint Planning in 90 minutes and a Sprint Review in 45.

Scrum ceremonies FAQ

What is the difference between Sprint Review and Sprint Retrospective?

The Sprint Review focuses on the product: what was built and what to build next. It involves stakeholders. The Sprint Retrospective focuses on the team's process: how the team worked and how to improve. It is an internal team event.

Are Scrum ceremonies mandatory?

According to the Scrum Guide, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective are all required events. Backlog Refinement is recommended but not formally required. Skipping formal ceremonies typically leads to uncoordinated work and slower improvement cycles.

How many Scrum ceremonies are there?

The Scrum Guide defines four official events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Backlog Refinement is a fifth widely-adopted practice. The Sprint itself is also considered an event — a container for the other four.

What tools can help run Scrum ceremonies more effectively?

For Sprint Planning, a planning poker tool like ScrumVote speeds up story point estimation with simultaneous reveals that prevent anchoring. For retrospectives, virtual whiteboard tools work well. For Daily Scrum, a simple task board (physical or digital) keeps the team focused on the Sprint Goal.

Run story point estimation in your next Sprint Planning — free, no account needed