Scrum Ceremonies: 4 Events, Order & Timeboxes

Scrum ceremonies are the recurring Scrum events that structure each sprint.

The Scrum ceremonies in order are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Together they create a repeating loop for planning work, inspecting progress, gathering product feedback, and improving the team's process.

The four core Scrum ceremonies are:

1. Sprint Planning - decide the sprint goal and sprint backlog.
2. Daily Scrum - inspect progress toward the sprint goal and adapt the plan.
3. Sprint Review - inspect the product increment with stakeholders.
4. Sprint Retrospective - improve how the Scrum team works together.

Use the Sprint Planning Checklist to prepare the first event, the Daily Standup Generator for daily updates, and the Retrospective Board to capture improvement actions.

They happen in this order:

Sprint Planning -> Daily Scrum -> Sprint Review -> Sprint Retrospective -> next Sprint Planning

Scrum Ceremonies at a Glance

Scrum calls them events. Many teams call them ceremonies or meetings. The useful question is not the label. The useful question is whether each event creates the decision or feedback loop it is supposed to create.

1. Sprint Planning

• When: At the start of each sprint.
• Timebox: Up to 2 hours per week of sprint length. A two-week sprint can use up to 4 hours.
• Who attends: Product Owner, Scrum Master, and developers.
• Main output: Sprint goal and sprint backlog.

Sprint Planning answers two questions:

1. Why is this sprint valuable?
2. What can the team realistically complete?

The Product Owner brings the highest-priority backlog items. The team discusses readiness, capacity, dependencies, and risk. The result is a shared sprint goal and selected backlog items the team believes it can complete.

Sprint Planning Agenda

Sprint Planning Example

Sprint goal:
Enable customers to reset passwords without support help.

Selected work:
- Create password reset request form
- Send reset email
- Validate reset token
- Add expired token error state
- Add basic reset flow tests

Use the Sprint Planning Checklist before closing planning. If estimates are still unclear, run the discussion in Planning Poker.

2. Daily Scrum

• When: Every day of the sprint, usually at the same time.
• Timebox: 15 minutes.
• Who attends: Developers. The Scrum Master and Product Owner may attend, but developers own the event.
• Main output: A clear daily plan and visible blockers.

The Daily Scrum is not a status report to a manager. It is a short inspection of progress toward the sprint goal.

The team should leave knowing:

• what changed since yesterday
• what work matters today
• what is blocked
• who needs follow-up after the meeting
• whether the sprint goal is at risk

Daily Scrum Format

The classic three questions are useful:

1. What did I complete yesterday?
2. What will I work on today?
3. What blockers do I have?

But the better version connects everything to the sprint goal:

Yesterday: Finished reset email template and reviewed token expiry logic.
Today: Implement reset token validation and pair with QA on test cases.
Blocker: Need security review on token lifetime.
Sprint goal risk: Low if review happens today.

Use the Daily Standup Generator to turn rough notes into a clean Yesterday/Today/Blockers update.

3. Sprint Review

• When: At the end of the sprint, before the retrospective.
• Timebox: Up to 1 hour per week of sprint length. A two-week sprint can use up to 2 hours.
• Who attends: Scrum Team and relevant stakeholders.
• Main output: Feedback on the product increment and updates to the product backlog.

The Sprint Review answers:

Did we build the right thing, and what should we learn from stakeholder feedback?

It is not only a demo. The demo is part of the review, but the real purpose is product inspection and adaptation.

Sprint Review Agenda

Use the Sprint Review Meeting Template if your review needs a clear agenda and stakeholder questions.

4. Sprint Retrospective

• When: After the Sprint Review and before the next Sprint Planning.
• Timebox: Up to 45 minutes per week of sprint length. A two-week sprint can use up to 1.5 hours.
• Who attends: Scrum Team.
• Main output: One or two specific improvement actions for the next sprint.

The retrospective answers:

How can we work better together next sprint?

The retrospective is about process, collaboration, quality, tools, communication, and team health. It is not a second sprint review and it is not a blame session.

Simple Retrospective Format

Good action items are specific and owned.

Weak action item:

Communicate better.

Better action item:

For the next sprint, any blocker older than 2 hours is posted in #blocked with owner, impact, and needed help. Review at next retro.

Use the Retrospective Board to collect notes, vote, and turn the discussion into action items.

Scrum Ceremonies Order

For a normal sprint, the order is:

1. Sprint Planning
2. Daily Scrum each working day
3. Sprint Review
4. Sprint Retrospective
5. Next Sprint Planning

For a two-week sprint, a simple rhythm looks like this:

Backlog refinement is important, but it is not one of the four core Scrum events. It is a useful recurring activity many teams use to prepare future work before sprint planning.

Scrum Ceremonies vs Scrum Artifacts

Teams often mix up events and artifacts.

Events create the rhythm. Artifacts hold the work and evidence. Commitments create clarity about what the team is trying to achieve.

Who Attends Each Scrum Ceremony?

The Product Owner is part of the Scrum Team, so they usually attend the retrospective. Some teams exclude the Product Owner when there is a trust problem, but that is a symptom to fix, not the normal pattern.

Common Scrum Ceremony Mistakes

Sprint Planning becomes backlog refinement

If stories are not ready, planning turns into requirements discovery. Fix this with regular refinement and a clear Definition of Ready.

Useful next step: AI Backlog Refinement Prompts.

Daily Scrum becomes a manager report

If everyone reports to one person, the team stops coordinating with each other. Re-center the meeting on blockers, sprint goal risk, and follow-up conversations.

Useful next step: Daily Standup Best Practices.

Sprint Review becomes a slide presentation

Stakeholders need to inspect working product. Slides can add context, but they should not replace a product demo and feedback discussion.

Useful next step: Sprint Review Meeting Template.

Retrospective creates vague action items

"Improve communication" is not an action item. Pick one specific behavior change, assign an owner, and review it at the next retro.

Useful next step: AI Retrospective Prompts.

Frequently Asked Questions

What are the 4 Scrum ceremonies?

The four Scrum ceremonies are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Scrum formally calls them events.

What is the correct order of Scrum ceremonies?

The normal order is Sprint Planning, Daily Scrum throughout the sprint, Sprint Review near the end, Sprint Retrospective after the review, then the next Sprint Planning.

Is backlog refinement a Scrum ceremony?

Backlog refinement is not one of the four core Scrum events, but many Scrum teams run it regularly so sprint planning is faster and clearer.

What is the difference between Sprint Review and Retrospective?

Sprint Review inspects the product increment with stakeholders. Sprint Retrospective inspects how the Scrum Team worked and chooses process improvements for the next sprint.

How long should Scrum ceremonies take?

For a two-week sprint, Sprint Planning can take up to 4 hours, Daily Scrum is 15 minutes, Sprint Review can take up to 2 hours, and Sprint Retrospective can take up to 1.5 hours.

Next Step

If you are setting up Scrum ceremonies for a team, start with:

1. Sprint Planning Checklist - confirm goal, capacity, scope, and risks.
2. Daily Standup Generator - turn rough notes into clear standup updates.
3. Retrospective Board - run a live team retro with action items.
4. Planning Poker - estimate stories with the team.