Scrum Ceremonies Explained

A clear breakdown of the four core Scrum ceremonies — Sprint Planning, Daily Standup, Sprint Review, and Sprint Retrospective — with tips for running them effectively.

Scrum defines four ceremonies (also called "events") that give a sprint its structure. Each has a clear purpose, a recommended duration, and a defined set of participants.

1. Sprint Planning

When: At the start of each sprint.
Duration: Up to 2 hours per week of sprint length (e.g. 4 hours for a 2-week sprint).
Who: Scrum Master, Product Owner, Development Team.

The team selects items from the top of the product backlog and commits to completing them by the end of the sprint. The output is a sprint goal and a sprint backlog.

Key questions answered:

What can we deliver this sprint?
How will we get the work done?

2. Daily Standup (Daily Scrum)

When: Every day of the sprint, same time and place.
Duration: 15 minutes maximum.
Who: Development Team (Scrum Master and PO may attend but don't drive it).

A short synchronisation meeting for the team to inspect progress toward the sprint goal and adapt the plan.

Classic format:

What did I do yesterday?
What will I do today?
Are there any blockers?

Tip: Keep it to 15 minutes. Any detailed problem-solving should happen in a separate follow-up conversation.

3. Sprint Review

When: At the end of the sprint.
Duration: Up to 1 hour per week of sprint length.
Who: Scrum Team + key stakeholders.

The team demonstrates what was completed during the sprint. Stakeholders provide feedback and the Product Owner updates the backlog accordingly.

Key outcomes:

Stakeholders see working software.
The backlog is revised based on feedback.
Clarity on what comes next.

4. Sprint Retrospective

When: After the Sprint Review, before the next Sprint Planning.
Duration: Up to 45 minutes per week of sprint length.
Who: Scrum Team (Scrum Master facilitates).

The team reflects on how they worked together and identifies improvements for the next sprint.

Classic format:

What went well? — Practices to keep.
What didn't go well? — Problems to address.
Action items — Specific, owned improvements for next sprint.

Summary

| Ceremony | Purpose | Max Duration (2-week sprint) | |---|---|---| | Sprint Planning | Plan the sprint | 4 hours | | Daily Standup | Sync daily progress | 15 minutes | | Sprint Review | Demo to stakeholders | 2 hours | | Sprint Retrospective | Improve the team process | 1.5 hours |