Agile guide · Agile practices
Agile Meetings and Ceremonies: A Practical Guide
Agile teams use a small set of recurring meetings, often called ceremonies or events, to plan, coordinate, review and improve. Each has a clear purpose and a strict time-box. Run well, they replace most other meetings.
Key takeaways
- Five core meetings cover planning, coordination, review and improvement.
- Every meeting has a purpose and a time-box.
- Retrospectives should always end with concrete actions.
Overview
| Meeting | When | Time-box (2-week sprint) | Purpose |
|---|---|---|---|
| Sprint Planning | Start of sprint | Up to 4 hours | Agree the Sprint Goal and plan |
| Daily Scrum / stand-up | Every day | 15 minutes | Coordinate towards the goal |
| Backlog refinement | Ongoing | Typically a few hours per sprint | Prepare upcoming items |
| Sprint Review | End of sprint | Up to 2 hours | Inspect the result with stakeholders |
| Sprint Retrospective | After the review | Up to 1.5 hours | Improve how the team works |
Scrum's maximums are 8, 4 and 3 hours for planning, review and retrospective in a one-month sprint; shorter sprints usually need proportionally less.
Sprint Planning
Inputs: an ordered, refined Product Backlog, the team's recent velocity and availability.
- Why: the Product Owner proposes how the sprint can add value; the team agrees a Sprint Goal.
- What: the team selects backlog items it can complete.
- How: the team breaks items into tasks and plans the first days.
Output: a Sprint Backlog and a Sprint Goal everyone understands.
Daily Scrum (stand-up)
A 15-minute meeting for the people doing the work, held at the same time and place each day. The aim is to inspect progress towards the Sprint Goal and adjust the plan. Many teams walk the board from right to left (closest to done first) instead of going round the room.
Backlog refinement
An ongoing activity in which the Product Owner and team clarify, split and estimate upcoming items so they are ready for planning. Aim to keep about two sprints' worth of items ready.
Sprint Review
A working session, not a slideshow. The team demonstrates what was done, stakeholders give feedback, and everyone discusses what to do next. The Product Backlog is updated as a result.
Sprint Retrospective
The team reflects on people, processes, tools and its Definition of Done. Simple formats include:
- Start, stop, continue.
- Mad, sad, glad.
- 4Ls: liked, learned, lacked, longed for.
End with one or two concrete improvements, each with an owner, and check them at the next retrospective.
Keeping meetings effective
- Respect the time-boxes.
- Invite only the people needed.
- Keep the same time and place to build a rhythm.
- Cancel status meetings that these events make unnecessary.
Free templates for this topic
Frequently asked questions
Who attends the Daily Scrum, one of the Agile ceremonies?
The people doing the work. The Scrum Master and Product Owner attend if they are actively working on sprint items.
Are Agile ceremonies mandatory?
In Scrum, all five events are required. Other Agile methods use similar meetings with more flexibility.
What are the Agile ceremonies?
In Scrum, Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective, all within the Sprint. Most teams also hold regular backlog refinement.
How long should the Sprint Planning Agile ceremony take?
Up to eight hours for a one-month sprint, and proportionally less for shorter ones; up to about four hours for a two-week sprint.
How long is the Daily Scrum Agile meeting?
Fifteen minutes, held at the same time and place every day.
What are the three questions in the stand-up Agile meeting?
Traditionally: what did I do yesterday, what will I do today and what is blocking me. The 2020 Scrum Guide no longer requires them, and many teams instead walk the board focusing on the Sprint Goal.
What is the difference between the Sprint Review and Retrospective Agile ceremonies?
The Review inspects the product with stakeholders and adapts the backlog; the Retrospective inspects how the team worked and agrees improvements.
Is backlog refinement one of the Agile ceremonies?
No. The Scrum Guide describes refinement as an ongoing activity, not an event. Many teams still schedule regular refinement sessions.
Who facilitates Agile meetings?
Often the Scrum Master, but anyone on the team can. The Scrum Master ensures events happen and stay within their time-box.
Can Agile meetings be held remotely?
Yes. Use a shared digital board, video and a clear agenda, and rotate meeting times fairly if the team spans time zones.
What if our Agile meetings take too long?
Stick to time-boxes, prepare refined backlog items in advance and move detailed problem-solving out of the stand-up into smaller follow-up conversations.