Scrum Ceremonies: Purpose, Timebox and Agenda

"Ceremonies" is the everyday word for what the Scrum Guide calls events: sprint planning, the daily scrum, the sprint review, the sprint retrospective, and the sprint itself as the container holding the rest. Backlog refinement is not an official event but is an ongoing activity most teams schedule as one.

Each event exists to create a decision point and to make inspection possible without adding extra meetings. Run them without knowing which decision each one produces and you get four hours a week of narration.

The events at a glance

Sprint planning

Planning answers why this sprint is valuable, what can be done, and how the work will start. Do it in that order: agree the goal before selecting items, or the sprint becomes a shopping list with no theme.

1. 1Capacity first — days available x hours per day x a focus factor of 0.6 to 0.8.
2. 2Reference velocity — the three-sprint average delivered, not the best sprint ever.
3. 3Sprint goal — one outcome, stated before any item is pulled in.
4. 4Walk candidate items, confirm acceptance criteria exist, and defer anything unready.
5. 5Stop committing when net capacity is full, then name the risks and dependencies with owners.

Daily scrum

Fifteen minutes, same time, same place, for the developers to re-plan the next day's work against the sprint goal. It is not a status report to a manager: the moment it becomes one, people start reporting activity instead of raising blockers.

• Walk the board right to left, so the closest-to-done work is unblocked first.
• Raise blockers, do not solve them — take the debugging conversation afterwards with the two people who need it.
• If someone has nothing to say three days running, their work is either invisible or too large.

Sprint review

A working session, not a presentation. Stakeholders see the increment running, ask questions and influence what comes next. Slides about work rather than the work itself are the clearest sign the increment is not actually done.

• Demonstrate only items meeting the Definition of Done — partly finished work is not reviewable.
• Restate the sprint goal first, then show whether it was met.
• Capture backlog changes live, so the review actually feeds the next planning session.

Sprint retrospective

Bring data — committed versus delivered, carry-over, unplanned work added, escaped defects — then gather observations in silence before discussing anything. Group into themes, find a cause you can change, and agree at most three actions with owners and due dates.

Backlog refinement

Refinement is the pressure valve for everything else. Around 10% of capacity spent adding acceptance criteria, splitting oversized stories and answering open questions is what lets planning finish in two hours instead of four.

PMI standard templates for each ceremony

• Sprint planning template and capacity calculator — /templates/sprint-planning
• User story template with Given/When/Then acceptance criteria — /templates/user-story
• Sprint retrospective facilitation sheet and action log — /templates/sprint-retrospective