What Is a Scrum Ceremony? Full List Explained
A Scrum ceremony (officially called a "Scrum event" in the current Scrum Guide) is one of four recurring, structured meetings that give a Scrum team's work its rhythm: sprint planning, the daily standup, the sprint review, and the sprint retrospective — plus the sprint itself, which contains all of them.
Quick facts
- There are four core Scrum ceremonies, each with a specific purpose and typical timebox.
- "Ceremony" is the more commonly used everyday term; the official Scrum Guide now uses "event."
- See related: What Is a Sprint Retrospective and How to Run One for a deep dive on that specific ceremony.
The four Scrum ceremonies
| Ceremony | Purpose | Typical timebox (for a 2-week sprint) |
|---|---|---|
| Sprint Planning | The team selects and commits to backlog items for the upcoming sprint | Up to 4 hours |
| Daily Standup (Daily Scrum) | A short daily sync on progress and blockers | 15 minutes |
| Sprint Review | The team demonstrates completed work to stakeholders and gathers feedback | Up to 2 hours |
| Sprint Retrospective | The team reflects on their process and identifies improvements | Up to 1.5 hours |
Why these four ceremonies exist
Each ceremony serves a distinct purpose within the sprint cycle: sprint planning creates a shared commitment before work begins, the daily standup maintains ongoing visibility and quick blocker resolution during the sprint, the sprint review closes the loop with stakeholders on what was actually delivered, and the retrospective closes the loop internally on how the team worked together. Skipping any one of these tends to create a specific, predictable gap — skipping planning leads to unclear commitments, skipping standups loses daily visibility, skipping review loses stakeholder feedback, and skipping retrospectives loses continuous process improvement.
A closer look at each ceremony
Sprint Planning happens at the start of each sprint, where the team reviews the prioritized backlog and commits to what they'll deliver, informed by their capacity and the items' readiness (see Definition of Ready).
Daily Standup is a brief, focused sync — traditionally structured around "what did I do yesterday, what will I do today, any blockers" — kept short specifically to maintain daily alignment without becoming a lengthy status meeting.
Sprint Review brings stakeholders in to see completed work firsthand, gathering real feedback that can inform the backlog going forward — distinct from the retrospective, which focuses inward on team process rather than the product itself.
Sprint Retrospective is the team's dedicated time to reflect on how they worked together during the sprint and commit to specific process improvements for the next one (see the dedicated guide).
Common mistakes with Scrum ceremonies
- Skipping ceremonies when the team feels busy, losing the specific value each one provides — a skipped retrospective, for example, means recurring issues go unaddressed.
- Letting ceremonies run over their timebox habitually, turning focused, efficient meetings into lengthy, unfocused ones.
- Combining ceremonies that serve different purposes, like merging the sprint review and retrospective, which can dilute both the stakeholder-facing and internal-process-facing goals each is meant to serve.
- Treating ceremonies as pure formality rather than genuinely using them for their intended purpose — a standup that's just a status report to a manager misses the team-coordination value it's meant to provide.
FAQ
Are Scrum ceremonies mandatory? Within a strict Scrum framework, yes — the four events are considered core to how Scrum functions; teams practicing a looser or hybrid agile approach sometimes adapt or skip certain ceremonies, though this moves away from formal Scrum.
How long should each ceremony last? Timeboxes typically scale with sprint length — for a two-week sprint, sprint planning is up to 4 hours, the daily standup is 15 minutes, the sprint review up to 2 hours, and the retrospective up to 1.5 hours, per general Scrum Guide recommendations.
Who facilitates Scrum ceremonies? The Scrum Master typically facilitates most ceremonies, ensuring they stay focused and within their timebox, though the Product Owner leads key portions of sprint planning and the sprint review specifically.
What's the difference between a "ceremony" and an "event" in Scrum? They refer to the same four meetings — "ceremony" is the more commonly used informal term in everyday conversation, while the official Scrum Guide uses "event" as the more precise term.