I noticed something odd this week. Without deciding to, I'd started running my own life as a scrum sprint — a one-week one. At the start there's a plan. Through the week there's a backlog of what's still open. At the end there's a review of what got done and what rolls forward into next week. Plan, backlog, retro, rollover. That's the ceremony calendar of a scrum team, running for a team of one.
Except I don't hold any of the ceremonies. No stand-up, no refinement session, no sprint demo. And nothing is missing. That absence is the whole point, and it took me a while to understand why it works.
What the rituals are actually for
Strip a scrum ritual down and ask what it produces. A stand-up produces shared awareness of state — who's doing what, what's blocked. A refinement produces a legible backlog. A demo produces a record of what shipped. A retro produces a comparison of plan against reality.
Notice that every one of those outputs is a piece of structure — a current, agreed picture of the work. The ritual is just the mechanism a team uses to manufacture that structure by hand, in a room, because it doesn't otherwise exist in a form everyone can trust. The meeting is a factory for context.
Every scrum ceremony produces a piece of structure. If the structure is already there, the ceremony is producing something you already have.
Put the structure in, and the factory goes quiet
Now suppose the structure exists on its own — captured as you work, not reconstructed in a meeting. Suppose the state of every open item lives in one place, kept current. Suppose the backlog is a standing list, grouped by urgency and area, not a thing you refine into being each fortnight. Suppose the record of what shipped is just what you noted as you shipped it, and the plan-versus-reality comparison falls out automatically because both are written down.
Then the stand-up has nothing to surface — you can already see it. The refinement has nothing to clean up — the list was never messy. The demo has nothing to reconstruct — it's already recorded. The retro writes itself from the gap between plan and result. The ceremonies don't get cancelled by decree. They quietly run out of work to do.
That's what I mean by the ceremony being compensation. It was never the value; it was the cost of not having the structure. Pay the cost once, in structure, and you stop paying it every week in meetings.
Why one week, not two
Teams stretch to two-week sprints for a specific reason: ceremony is expensive, so you amortise it by holding it half as often. But if you've removed the ceremony, that reason evaporates — and a shorter loop is strictly better, because the gap between what you planned and what you did is the most useful signal you get, and you want to read it while it's fresh.
A week is the natural unit for that. A day is too short to show a pattern; a month is too long to feel one. The week is where a shape appears and you can still do something about it. So I keep the loop at a week and let the long-running work — the projects that can't finish in seven days — simply roll over, carried forward on the standing list until they're done. You don't need a longer sprint to hold long work. You need a rollover.
The uncomfortable implication for teams
Here's the part that isn't really about me and my folders. If your team's rituals feel heavy — if the stand-ups drag, the refinements sprawl, the demos feel like theatre — the instinct is to run them better. Tighter facilitation, stricter timeboxes, a new board.
The thesis says the opposite. The heaviness is a symptom: your ceremonies are working that hard because the structure underneath them is thin, so the meeting has to manufacture all the context from scratch, every time. The fix isn't better meetings. It's structure that carries the context on its own — captured as the work happens, kept current, trustworthy enough that reading it beats asking about it. Do that, and the meeting shrinks to the only thing people are genuinely scarce for: judgement and decision. Everything else was compensation.
Structure beats ceremony
I didn't set out to critique agile. I set out to stop losing track of my own open tasks, and I ended up with a sprint that needs no ceremonies because the structure does what the ceremonies were faking. That's the thesis in one more disguise: the ritual was never the magic. The structure was. And once the structure is real, most of the ritual is just habit with a calendar invite.