Definition: Scrum ceremonies (also called Scrum events) are the four recurring meetings that structure every sprint: Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective. Each one has a fixed purpose, a defined set of attendees, and a time box, so the team always knows what to plan, what to inspect, and what to improve next.
The four ceremonies turn a sprint from a stretch of busy work into a predictable rhythm. Planning sets the goal, the Daily Scrum keeps the team in sync, the Review shows real progress to stakeholders, and the Retrospective makes the next sprint better than the last. Skip one and the loop breaks: work drifts, surprises pile up at the deadline, and the same problems repeat.
TL;DR: Scrum runs on four ceremonies per sprint, Planning, Daily Scrum, Review, and Retrospective, each time-boxed to a fixed purpose and audience. Together they create a tight inspect-and-adapt loop. You can run all four on one Board so every event has a place, an owner, and a record. Build a sprint board free →
You are already doing a version of this. The standing 9 a.m. check-in, the Friday demo, the "what went wrong" thread after a launch, those are ceremonies without the labels. Scrum gives them names, a cadence, and a reason each one earns its place on the calendar.
What Are the Four Scrum Ceremonies?
The four Scrum ceremonies are Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective. Planning opens the sprint by agreeing on a goal and the work to reach it. The Daily Scrum re-syncs the team each day. The Review closes the sprint by showing the finished increment to stakeholders. The Retrospective closes the loop by improving how the team works.
Each ceremony maps to one job in the inspect-and-adapt cycle. Together they form a closed loop where the output of one sprint informs the input of the next.
The Daily Scrum repeats every working day inside the sprint. The other three each happen once: Planning at the start, Review and Retrospective at the end. The arrow from Retrospective back to the next Planning is the part most teams skip, and it is the one that compounds. A change you agree on in the Retro is only real once it shows up in the next sprint's plan.
Each Ceremony at a Glance
Each ceremony answers a different question: what should we build, are we on track, did we deliver, and how do we get better. The table below maps every event to its purpose, who attends, when it runs, and a typical time box for a two-week sprint. Time boxes scale with sprint length, so halve them for a one-week sprint.
| Ceremony | Purpose | Who attends | When | Time box (2-week sprint) |
|---|---|---|---|---|
| Sprint Planning | Agree on the sprint goal and pull work from the backlog | Product Owner, Scrum Master, Development Team | Start of sprint | Up to 4 hours |
| Daily Scrum | Re-sync progress, surface blockers, plan the next day | Development Team (Scrum Master facilitates) | Every working day | 15 minutes |
| Sprint Review | Demo the finished increment, gather stakeholder feedback | Scrum Team plus stakeholders | End of sprint | Up to 2 hours |
| Sprint Retrospective | Inspect how the team worked, agree on improvements | Product Owner, Scrum Master, Development Team | After the Review | Up to 1.5 hours |
The pattern is the same in every ceremony: inspect something real, then adapt. Planning inspects the backlog and adapts the plan. The Daily Scrum inspects yesterday and adapts today. The Review inspects the product and adapts the backlog. The Retrospective inspects the process and adapts the way of working.
Who Participates in Scrum Ceremonies?
The three Scrum roles attend ceremonies in different combinations. The Development Team is in all four. The Product Owner owns Planning and Review, where priorities and outcomes are decided. The Scrum Master facilitates every event, keeps each one inside its time box, and clears blockers so the team can focus.
- Sprint Planning: Product Owner, Scrum Master, and Development Team. The team decides what it can deliver and how.
- Daily Scrum: the Development Team owns it, the Scrum Master facilitates. Fifteen minutes to plan the day and name blockers.
- Sprint Review: the Scrum Team plus stakeholders. The increment is inspected and the backlog adapted in the open.
- Sprint Retrospective: Product Owner, Scrum Master, and Development Team. A private, blameless look at the process.
A useful rule of thumb: stakeholders join exactly one ceremony, the Review. Planning and the Retrospective belong to the team, so they stay candid. For the full breakdown of who does what, see the guide to Scrum roles.
Why Ceremonies Run on a Fixed Cadence
Ceremonies are time-boxed and recurring on purpose. A fixed cadence removes the question of when to meet, so the team spends its energy on what to decide. Predictable rhythm also makes progress visible: the same demo every two weeks, the same daily sync, the same retro turn drift into a signal you can read.
The time box is a forcing function, not a cage. Fifteen minutes for a Daily Scrum keeps it a sync, not a status report. Four hours for Planning keeps it focused on the goal, not a full backlog rewrite. When a ceremony consistently overruns, that is data: usually the backlog is unrefined or the sprint goal is unclear. Fix the input, and the meeting shrinks back to its box.
SPRINT CADENCE, 2-week sprint
┌──────────────────────────────────────────────────────────┐
│ Mon ── Tue ── Wed ── Thu ── Fri ── Mon ── Tue ── … ── Fri │
│ ▲ • • • • • • • │
│ Plan Daily Daily Daily Daily Daily Daily ... Review │
│ + Retro │
└──────────────────────────────────────────────────────────┘
▲ once • every working day end → Review then Retrospective
Types of Scrum Ceremonies
The four ceremonies fall into two groups by what they inspect. Planning and the Daily Scrum inspect the work: what to build and whether the team is on track. The Review and Retrospective inspect the outcome: what shipped and how the team performed building it.
- Sprint Planning: sets the sprint goal and the plan to reach it. Pulls items from the prioritized backlog into the sprint.
- Daily Scrum: a 15-minute daily sync to plan the day and surface blockers early, before they cost a sprint.
- Sprint Review: demos the working increment to stakeholders and adapts the backlog based on real feedback.
- Sprint Retrospective: reflects on the sprint process and commits to one or two concrete improvements for next time.
Some teams add a lightweight backlog refinement session mid-sprint to keep the next sprint's items ready. It is not one of the four formal events, but it makes Planning faster. See Scrum metrics for the velocity and burndown signals that tell you whether your cadence is healthy.
Related Terms and Concepts
- Sprint: the fixed-length time box, usually one to four weeks, that every ceremony is anchored to.
- Scrum Master: facilitates each ceremony, protects the time box, and removes impediments.
- Product Owner: owns the backlog and the sprint goal, leads Planning and the Review.
- Backlog: the prioritized list of work that feeds Sprint Planning.
- Scrum Board: the visual workspace where sprint work and ceremony notes live side by side.
- Agile: the broader set of principles that Scrum and its ceremonies put into practice.
Frequently Asked Questions About Scrum Ceremonies
How Often Are Scrum Ceremonies Conducted?
The Daily Scrum runs every working day of the sprint. Sprint Planning happens once at the start, and the Sprint Review and Retrospective happen once at the end, in that order. In a two-week sprint, that is roughly nine or ten Daily Scrums bookended by one Planning, one Review, and one Retrospective.
What Is the Role of the Scrum Master in Ceremonies?
The Scrum Master facilitates all four ceremonies. They keep each event inside its time box, make sure the right people attend, guide the team toward the purpose of each meeting, and remove blockers raised in the Daily Scrum. They lead the conversation, but the team owns the decisions.
Can Scrum Ceremonies Be Skipped?
Skipping a ceremony breaks the inspect-and-adapt loop the rest depend on. Drop Planning and the team works without a shared goal. Drop the Review and stakeholders lose visibility until it is too late to course-correct. Drop the Retrospective and the same problems repeat sprint after sprint. Shorten a ceremony when the sprint is short, but keep all four.
How Long Should Each Scrum Ceremony Last?
Time boxes scale with sprint length. For a two-week sprint, plan up to four hours for Sprint Planning, 15 minutes for each Daily Scrum, up to two hours for the Review, and up to 90 minutes for the Retrospective. Halve these for a one-week sprint. The numbers are ceilings, not targets.
Who Attends the Sprint Review Versus the Retrospective?
The Sprint Review is open: the whole Scrum Team plus stakeholders, so feedback comes from the people who use the product. The Retrospective is closed: only the Scrum Team. That privacy is what keeps the conversation honest, so the team can name real problems without an audience.
How Can Teams Improve the Effectiveness of Scrum Ceremonies?
Keep a single source of truth so no one walks in unprepared. Put the sprint goal, backlog, daily blockers, demo notes, and retro action items on one Scrum Board the whole team can see. When every ceremony has a place to write to and read from, the meetings get shorter and the decisions stick.
Do It in Taskade: A Sprint Board That Runs Every Ceremony
The fastest way to make ceremonies stick is to give all four a home on one Board. Describe your sprint to Taskade Genesis in plain English, and it builds a working sprint board where each column is a stage of the work and each ceremony has a place to write to and read from. No setup, no template hunting.
SPRINT 14 BOARD goal: ship the booking flow
┌────────────┬────────────┬────────────┬────────────┐
│ Backlog │ In Progress│ Review │ Done │
├────────────┼────────────┼────────────┼────────────┤
│ Booking UI │ Email API │ Calendar │ Login page │
│ Pay screen │ Reminder │ sync │ Settings │
│ ... │ ... │ ... │ ... │
└────────────┴────────────┴────────────┴────────────┘
Planning fills Backlog · Daily Scrum moves cards · Review demos "Done"
Here is what you would build. A pipeline Board where Planning fills the Backlog column, the Daily Scrum moves cards across the columns, the Review walks the Done column with stakeholders, and the Retrospective drops action items into a tracked list. A reliable automation posts the daily standup prompt and reminds the team when Review and Retro are due, so the cadence runs without anyone chasing it. The Scrum Master sees blockers the moment a card stalls; the Product Owner sees the goal and what shipped against it. Connect a second project for retro action items, and last sprint's improvements show up as cards in the next one, closing the loop on their own.
You are already tracking this in a spreadsheet, a chat thread, and your head. Put it in one place that updates itself. Build your sprint board in Taskade →