Agile ceremonies guide
Sprint Planning, Standups, Retros, and Reviews explained
Agile ceremonies are the recurring meetings that keep product teams aligned and moving. Learn what each one is for, who attends, and how to participate effectively as a new team member.
Why Agile ceremonies matter
Ceremonies are not just meetings — they are structured moments for alignment, feedback, and course correction. Teams that skip them tend to accumulate misalignment until something breaks. Teams that run them well move faster with less confusion.
The five core ceremonies
Most Agile teams run five recurring ceremonies. Each has a fixed cadence, a defined attendee list, and a specific output.
Each ceremony in depth
A breakdown of every ceremony — what happens, who is there, and what new team members should know before their first one.
Sprint Planning
When
Start of every sprint (1–2 week cycle)
Who attends
Entire team (PM, engineers, designer, QA)
Duration
1–2 hours for a 2-week sprint
Decide what the team will build this sprint. Pull from the backlog, estimate effort, commit to a sprint goal.
Good sprint planning means the team understands why they are building each item, not just what. The Product Owner brings prioritized backlog items and explains the business value. The team selects what they can realistically deliver and the meeting ends with a committed sprint backlog and a clear sprint goal.
New team member tip
Come with questions about the 'why', not just the 'what'.
Daily Standup
When
Every working day, same time
Who attends
Development team + PM
Duration
15 minutes maximum
Quick status sync. Identify blockers. Keep everyone aware without a long meeting.
Three questions drive the standup: What did I do yesterday? What am I doing today? Any blockers? This is not a problem-solving meeting — take discussions offline. Keep it tight so everyone's time is respected.
New team member tip
Be brief and specific. If you are blocked, say so clearly.
Sprint Review / Demo
When
End of every sprint
Who attends
Team + stakeholders
Duration
30–60 minutes
Show what was completed this sprint. Get feedback from stakeholders.
Demo what is done (accepted), not what is in progress. This is the team's chance to show real working software to people outside the immediate team and collect feedback that shapes the next sprint.
New team member tip
Ask questions in reviews — curiosity is welcomed.
Sprint Retrospective
When
End of every sprint, after the review
Who attends
Core team only (no stakeholders)
Duration
45–60 minutes
Continuous improvement. What worked well? What did not? What will we try differently?
Common formats include Start/Stop/Continue; Mad/Sad/Glad; and 4 Ls (Liked, Learned, Lacked, Longed for). The retrospective is a safe space for honesty — teams that surface problems in retros fix them before they become crises.
New team member tip
Be honest. The retro is a safe space — use it.
Backlog Refinement
When
Mid-sprint, 1–2 times per sprint
Who attends
PM + engineering team
Duration
30–60 minutes
Review upcoming backlog items. Add detail, estimate, prioritize.
Backlog refinement (sometimes called grooming) ensures items are ready before they reach sprint planning. The team reviews upcoming work, asks clarifying questions, adds acceptance criteria, and assigns rough estimates so nothing arrives to sprint planning half-baked.
New team member tip
This is where you learn what is coming next — ask about the rationale for each item's priority.
Go deeper
Learn Agile fundamentals
Ceremonies are one part of the Agile system. Understand Scrum, Kanban, the backlog, velocity, and everything else in the full guide.
Learn Agile fundamentals