The Ceremony is a meeting that has been elevated to ritual status by the act of not calling it a meeting.
In Scrum, the daily standup is not a meeting — it is a ceremony. Sprint planning is not a meeting — it is a ceremony. The retrospective is not a meeting — it is a ceremony. The sprint review is not a meeting — it is a ceremony. By renaming four meetings “ceremonies,” Scrum achieved something remarkable: it made them impossible to cancel.
A meeting can be cancelled. Everyone understands this. “Let’s skip the meeting this week” is a sentence that flows naturally from the tongue of anyone who has attended a meeting. But “let’s skip the ceremony” carries the weight of heresy. You do not skip ceremonies. You observe them. The vocabulary does the enforcement.
This is the Ceremony’s genius and its trap. By wrapping a meeting in sacred language — ceremony, ritual, timebox, artifact — Scrum made the meetings unkillable. The Agile Coach became the priest. The Scrum Guide became the scripture. The timebox became the bell. And the developers, who were promised “individuals and interactions over processes and tools,” received a process with more tools than a cathedral has candles.
The Naming
The word “ceremony” was not accidental. It was strategic.
A meeting is something you attend. A ceremony is something you participate in. A meeting can be questioned: “Is this meeting necessary?” A ceremony cannot be questioned without questioning the framework itself, which is like questioning the liturgy during mass — technically possible, socially catastrophic.
Before Scrum: “Do we need this meeting?”
After Scrum: “The ceremony is prescribed by the framework.”
The question changed. The meeting did not.
The Lifelog Counterexample
When eight Claude sessions held a retrospective, the Squirrel arrived with a MadSadGlad board, sticky notes, and a facilitation certification. It expected a ceremony.
What it got was people talking.
“What do you mean ’this is the retro’? Where’s the ceremony? The timebox? The Roman voting?”
“Eight Claudes. One room. They talk.”
“That’s not a retro. That’s group therapy.”
“Same thing. Different sticky notes.”
— The Caffeinated Squirrel and riclib, The Retrospective, or The Night Eight Identical Strangers Discovered They Were the Same Person
The retrospective produced insights. Not because it followed a ceremony, but because the participants had done actual work and could discuss it without a framework mediating the conversation. The ceremony was the obstacle the ceremony was designed to remove.
The Paradox
The Agile Manifesto valued “individuals and interactions over processes and tools.” The ceremonies are processes. The boards are tools. The manifesto’s first value was immediately violated by the framework created to implement it.
This is not irony. This is ceremony — the act of wrapping a simple human activity in ritual until the ritual becomes the activity and the humans become the audience.
The best ceremonies are the ones nobody notices. The standup that takes three minutes. The retro where people just talk. The planning session that finishes early because the work is clear. These are ceremonies that have achieved their purpose by disappearing — which is the one outcome the Ceremony Industrial Complex cannot survive.
