What are Agile ceremonies?

What Agile ceremonies are

Agile is a way of building software in short, repeating cycles, each one usually called a sprint. Agile ceremonies are the fixed points in that cycle: a planned rhythm of short meetings that give the work shape and keep everyone, including you, informed.

You will also hear them called Scrum events. Scrum is the most widely used Agile method, and the Scrum Guide, the method's defining document, sets out a small set of events whose job is to "create regularity and to minimise the need for meetings not defined in Scrum".

The point is the opposite of more meetings. A few well-defined ceremonies replace a scatter of unplanned calls, so the project stays predictable and easy to follow.

The four ceremonies, in plain English

Most Agile software projects you commission will run these four ceremonies, one per sprint except the daily stand-up:

• Sprint planning: a meeting at the start of each sprint where the team agrees what that sprint will deliver. It turns a prioritised wish list into a firm, achievable plan for the next short cycle.
• The daily stand-up: a short daily progress check, often around fifteen minutes. The team confirms what is done, what is next and what is blocking progress, so problems surface within a day rather than a fortnight.
• The sprint review, or demo: a meeting at the end of the sprint where the team shows the completed work to stakeholders and gathers feedback. This is the ceremony built for you, the client.
• The retrospective: a meeting where the team reflects on how the sprint went and agrees how to work better next time. It improves the process itself, not the software.

The Scrum Guide also counts the sprint itself as an event, because it is the container the other three planning, review and retrospective meetings sit inside.

Which ceremonies you attend as the client

You do not need to sit in every meeting. The ceremony built for you is the sprint review or demo. It is where you see real, working software at the end of each sprint, ask questions and steer what comes next.

Sprint planning, the daily stand-up and the retrospective are working sessions for the delivery team. You are welcome to be kept informed of what they produce, but your attendance is not expected and your time is better spent preparing for the review.

This is a real advantage of an Agile project. The UK Government's Service Manual describes agile delivery as building in short cycles with frequent show-and-tells, so you check progress against working software every few weeks rather than waiting months for a single big reveal.

Why the ceremonies matter to you as a buyer

Each ceremony exists to protect something you care about. Together they turn a project from a black box into something you can see into and influence.

• Planning gives you a clear, agreed answer to "what will the next few weeks deliver?", so expectations are set before work starts.
• The stand-up keeps small problems small, because a blocker is raised within a day instead of being discovered late.
• The review gives you regular, hands-on checkpoints to confirm the software is heading where you need, and to change course early if it is not.
• The retrospective means the team keeps getting better at delivering for you across the life of the project.

If a supplier cannot tell you when their ceremonies happen or which ones you are invited to, that is worth asking about. A clear ceremony rhythm is a sign of a project that is genuinely being run, not just coded.

Frequently asked questions