Walk into most delivery organisations and you will find the full set of agile ceremonies running on schedule: standups, sprint planning, retrospectives, sprint reviews, all present, all diligently facilitated. Ask the same organisation how predictable its delivery actually is, and the confidence disappears. The ceremonies have become the proxy for maturity rather than a mechanism for producing it.
This is not an argument against agile methods, which remain a sound way to organise work. It is an argument against mistaking the ritual for the outcome. A team can hold a perfect retrospective every fortnight and still ship late, ship broken, or ship the wrong thing, because none of those ceremonies, on their own, measure the things that actually determine whether delivery is reliable.
Flow tells you more than velocity ever will
Velocity, the number most teams report upward, measures how much a team said it would do compared with how much it claims to have done, using a unit the team invented itself. It is trivially gameable and tells a stakeholder almost nothing about whether the next commitment will hold.
Flow metrics: cycle time, the age of work in progress, the amount of work sitting blocked, tell a much harder story, because they describe what is actually happening to a piece of work as it moves through the system rather than what a team estimated it would take. A team whose cycle time is stable and short is predictable even if it never reports velocity at all.
A ceremony tells you a meeting happened. It does not tell you whether the work is any good, or whether the next promise will be kept.
Quality has to be measured, not assumed
Most organisations discover quality problems from customers, incidents or audits, which is the most expensive possible place to discover them. Defect escape rate, rework volume and the proportion of a team's capacity spent fixing its own recent output are all measurable well before that point, and all more informative than whether the team held a demo.
Teams that track rework as a first-class metric tend to behave differently: they slow down slightly to get things right the first time, and the apparent loss of speed is repaid many times over in the incidents and hotfixes that never happen.
- 路Track cycle time and work-in-progress age, not just velocity, as the primary flow signal
- 路Measure rework and defect escape rate as core quality indicators, not as incident post mortems
- 路Report predictability, the gap between what was committed and what was delivered, as a trend, not a single sprint snapshot
- 路Treat ceremony attendance as hygiene, not as evidence of maturity, in any delivery health assessment
Predictability is the metric that actually matters to sponsors
Nobody funding a programme cares primarily about story points; they care whether the thing they were told would arrive in March actually arrives close to March. Predictability, tracked honestly over several cycles, is the single number that answers the question sponsors are actually asking, and it is rarely reported because it is uncomfortable to report when it is bad.
Building the discipline to report predictability consistently, including when it is poor, is itself a signal of delivery maturity that no ceremony can fake. Organisations that hide a bad predictability trend behind a well-run sprint review are postponing a harder conversation, not avoiding it.
What maturity actually looks like
Mature delivery organisations still run ceremonies, but they treat them as one input among several, not as the entire operating system. They pair the ceremonies with flow data, quality data and honest predictability reporting, and they are willing to change the ceremonies, or drop ones that are not earning their time, when the data suggests something else would work better.
That willingness to treat process as a hypothesis rather than doctrine is the real differentiator. Teams that defend the ceremony because the manual says so are usually the ones whose underlying metrics nobody has looked at in a long time.
None of the metrics described here are exotic or expensive to collect; most delivery tools capture the raw data already, and the barrier is usually the will to report it honestly rather than the tooling to produce it. The organisations that make this shift stop asking whether the team is doing agile correctly and start asking whether delivery is actually predictable, which is the question that was always meant to matter.
Ceremonies are a means, not an end. Treated as an end, they become a comfortable performance of maturity that lets the underlying delivery problems go unexamined for years.