What are the four main Scrum ceremonies?

Sprint Planning starts the sprint by setting a goal and selecting work. The Daily Scrum is a 15-minute daily sync. The Sprint Review inspects the increment with stakeholders. The Sprint Retrospective reflects on how to improve. Backlog refinement is ongoing rather than a fixed event.

How long should each ceremony last?

The Scrum Guide gives maximums for a one-month sprint: Sprint Planning up to 8 hours, Sprint Review up to 4, Retrospective up to 3, and the Daily Scrum fixed at 15 minutes. Shorter sprints get proportionally shorter events, except the Daily Scrum which stays at 15 minutes.

Why does the Daily Scrum stay 15 minutes for any sprint length?

The Daily Scrum is a daily cadence tied to a single day of work, not to the sprint length. Whether your sprint is one week or four, the team still meets once a day for at most 15 minutes to inspect progress and re-plan the day.

Is backlog refinement a ceremony?

Not formally. Refinement is an ongoing activity in which the Product Owner and Developers add detail, estimates and order to backlog items so they are ready for future sprints. Teams typically spend around 10% of their capacity on it across the sprint.

Does this tool send my sprint settings anywhere?

No. The timeboxes are scaled entirely in your browser. Nothing is uploaded, logged or stored.

Agile Ceremony Reference

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

The rhythm of a Scrum sprint

Scrum runs on a fixed set of events that create transparency and regular chances to inspect and adapt. This reference lays out each ceremony — its cadence, who attends, its purpose and its timebox — and scales the recommended lengths to the sprint length you actually run.

How it works

The Scrum Guide expresses event timeboxes as maximums for a one-month sprint and scales them down for shorter sprints:

Sprint Planning  → up to 8 hours for a 1-month sprint (scales)
Daily Scrum      → 15 minutes, fixed every working day
Sprint Review    → up to 4 hours (scales)
Retrospective    → up to 3 hours (scales)
Refinement       → ongoing, ~10% of Developers' capacity

A two-week sprint therefore caps Planning at about 4 hours, the Review at 2 hours and the Retrospective at 1.5 hours, while the Daily Scrum stays fixed at 15 minutes. Treat every figure as a ceiling: a well-run team often finishes earlier.

Tips and notes

Timeboxes are maximums, not targets — protect focus by ending early when the goal is met.
Keep the Daily Scrum to the Developers and tied to the Sprint Goal; it is a re-planning event, not a status report to managers.
Hold the Retrospective after the Review so feedback from stakeholders can feed improvement actions.
Budget refinement continuously rather than as one big meeting, so the next sprint’s items are always ready.