"Cargo Cult Agile – When Rituals Matter More Than Results"

November 2025 9 min read Opinion + Academic Reference

After World War II, indigenous peoples of the Pacific Islands built wooden airplanes, constructed bamboo control towers, and marched in military formation – faithfully mimicking the behaviours of Western military personnel, in the belief that the rituals would summon the cargo planes and their valuable goods. The planes did not come. The rituals continued. This is Cargo Cult Agile. And it is everywhere.

---

The Hook: When the Map Becomes the Territory

The anthropological phenomenon of cargo cults is well documented. What makes it a useful lens for understanding modern Agile adoption is the precision of the analogy. The Pacific islanders had observed a genuine causal relationship – military activity preceded the arrival of valuable goods – but had misidentified which elements of that activity were actually causal. They reproduced the observable surface behaviours while missing the underlying mechanism entirely.

This is exactly what most organisations do with Agile. They observe that high-performing software teams do daily standups, use sprint boards, write user stories, and hold retrospectives. They implement daily standups, sprint boards, user stories, and retrospectives. They wait for the high performance to arrive. It does not. The rituals continue.

---

The Reality: Symptoms of Cargo Cult Agile

Cargo Cult Agile is not always obvious from the inside. The ceremonies feel purposeful. The vocabulary is correct. The tools are configured. From a distance – from a management dashboard, from a consultant’s assessment report, from an Agile maturity model – everything looks fine. The dysfunction is in the gap between what the ceremonies are supposed to produce and what they actually produce.

The Diagnostic Checklist

Here are the most reliable indicators that you are observing Cargo Cult Agile rather than genuine Agile practice:

• Ceremonies happen on schedule regardless of their value. The retrospective runs every sprint even when the team has nothing meaningful to discuss. The sprint review happens even when there is nothing to demo. The daily standup happens even when the whole team is working on a single, well-understood task that requires no coordination.
• The ceremonies produce artefacts but not decisions. Retrospective action items that nobody acts on. Sprint reviews that generate feedback that never reaches the backlog. Daily standups that identify blockers that remain unresolved for weeks.
• The vocabulary is adopted without the concepts. “We are being Agile” used to mean “we changed our plans without telling anyone.” “We are iterating” used to mean “we did not finish the feature.” “We are self-organising” used to mean “nobody is accountable for this.”
• Agile practices are used to avoid difficult conversations. “The backlog will prioritise that” instead of “we have decided not to do that.” “We will revisit in the next sprint” instead of “this is not valuable enough to build.”
• The Sprint Goal is a list, not a goal. “Complete the login feature, fix three bugs, and refactor the payment module” is not a Sprint Goal. It is a to-do list. A Sprint Goal describes an outcome, not a set of tasks.

The clearest single indicator: Ask a team what would happen if they skipped a ceremony this sprint. If the answer is “we would get in trouble” rather than “we would lose something valuable” – the ceremony exists to satisfy an external requirement, not to serve the team. That is Cargo Cult Agile.

---

The Checksum: The Academic Evidence

The phenomenon of Cargo Cult Agile is not just anecdotal. Academic research on Agile adoption has consistently identified the gap between Agile practices and Agile values as a primary driver of failed transformations.

What the Research Shows

A study published in the Journal of Systems and Software examining Agile adoption across multiple organisations found that the most common failure mode was what the researchers called “ceremonial compliance” – teams following Agile practices without understanding or internalising the values behind them. The study found that ceremonial compliance was associated with all the surface indicators of successful Agile adoption – regular ceremonies, Agile tooling, certified practitioners – and none of the outcome indicators – improved delivery frequency, reduced defect rates, higher team satisfaction.

The State of Agile Report provides supporting evidence at scale. Year after year, organisations report high rates of Agile practice adoption alongside persistent challenges that those practices are supposed to address: inability to manage changing priorities, lack of management support, inconsistent practices across teams. The practices are running. The outcomes are not improving. This is Cargo Cult Agile at industry scale.

The Psychology Behind the Cult

Why does Cargo Cult Agile persist? The psychological mechanisms are well understood.

Sunk cost and commitment escalation: Once an organisation has invested in an Agile transformation – the training, the tools, the restructuring, the consultant fees – there is enormous pressure to declare it successful regardless of outcomes. Admitting that the ceremonies are not producing results would mean admitting that the investment was misallocated. So the ceremonies continue, and the definition of success shifts from “improved outcomes” to “consistent practice.”

Social proof and isomorphism: Organisations adopt practices because other organisations adopt them, not because the evidence supports them. If your competitors are doing SAFe, if your industry peers are running PI Planning events, there is social and reputational pressure to do the same – regardless of whether it is working for anyone.

Measurement substitution: Organisations are good at measuring activity and poor at measuring outcomes. It is easy to track whether standups happen daily, whether retrospectives occur each sprint, whether story points are being estimated. It is hard to measure whether customers are getting more value, whether teams are genuinely improving, whether the organisation is becoming more adaptive. So organisations measure what they can measure and call it success.

“Cargo Cult Agile is not a failure of intelligence. It is a failure of courage – the courage to ask whether the ceremonies are actually working, and to change them if they are not.” Markus – agile-checksum.com

---

Real-World Examples: Three Cults in Practice

The Retrospective That Never Changed Anything

A team I worked with had been running retrospectives every two weeks for two years. They used a different format each time – Start/Stop/Continue, the 4Ls, Mad/Sad/Glad, sailboat, timeline. The Scrum Master was creative and well-intentioned. The retrospectives were well-facilitated and psychologically safe.

When I reviewed the retrospective output from the previous twelve months, I found forty-seven action items. Six had been completed. The other forty-one had either been carried forward to subsequent retrospectives, quietly dropped, or never assigned to anyone in the first place. The top three issues raised in the most recent retrospective were identical to the top three issues raised twelve months earlier.

The retrospective ceremony was functioning perfectly. The continuous improvement it was designed to produce was not happening at all. The team had learned to express their frustrations in a retrospective and then accept that nothing would change. That is not a retrospective. It is a complaints forum with good facilitation.

The Sprint Review Nobody Attended

A software team at a large insurance company ran a sprint review every two weeks. They prepared demonstrations, updated their release notes, and set up the meeting room. Consistently, between zero and two stakeholders attended. The team presented to each other, noted that no external feedback had been received, and closed the meeting.

This had been happening for eight months. Nobody had questioned whether the sprint review was serving its purpose. Nobody had investigated why stakeholders were not attending. Nobody had considered cancelling the ceremony or replacing it with something that would actually produce stakeholder feedback. The ceremony was on the calendar. The ceremony happened. That was sufficient.

When I asked the Scrum Master why stakeholders did not attend, the answer was: “They’re busy.” When I asked what had been done to make attendance easier or more compelling, the answer was: “We send a calendar invite.” The ceremony existed. The purpose it was designed to serve did not.

The Definition of Done That Nobody Enforced

A development team had a Definition of Done that covered twelve criteria: unit tests written and passing, code reviewed, documentation updated, accessibility checked, performance benchmarks met, and six others. It was thorough, well-considered, and prominently displayed on the team’s Confluence page.

In practice, items were regularly marked as done with three or four of the twelve criteria unmet. This was acknowledged in retrospectives. Action items were created. The situation did not improve. When I asked why, the answer was consistent: the sprint commitment could not be met if the full Definition of Done was enforced, and the team felt pressure to meet the commitment. So the Definition of Done existed as an artefact while not existing as a practice.

This is the most insidious form of Cargo Cult Agile: the artefact is present, the ceremony of maintaining it occurs, and the purpose it serves is silently abandoned.

---

How to Break the Cult

Breaking out of Cargo Cult Agile requires doing something that feels deeply counterintuitive in most organisational cultures: stopping ceremonies that are not working and asking honestly why they are not working before resuming them.

Cargo Cult Behaviour	Genuine Alternative
Run every ceremony on schedule regardless of value	Cancel or adapt ceremonies that are not producing their intended outcome
Create retrospective action items and forget them	One action item per retrospective, owned by a named person, reviewed at the next retrospective
Enforce the Definition of Done as a checkbox exercise	Enforce the Definition of Done as a non-negotiable – reduce scope rather than reduce quality
Hold sprint reviews regardless of stakeholder attendance	Fix the stakeholder attendance problem or replace the sprint review with something that produces genuine feedback
Measure ceremony completion as a success indicator	Measure outcomes – delivery frequency, defect rates, team satisfaction, customer value

The most powerful question in Agile: “What would we lose if we stopped doing this?” Ask it about every ceremony, every artefact, every practice. If the honest answer is “nothing of substance” – stop doing it. If the honest answer reveals genuine value – make sure the ceremony is actually producing that value, not just going through the motions of it.

---

The Takeaway: Rituals Are Not Results

Agile ceremonies are not valuable in themselves. They are valuable insofar as they produce the outcomes they were designed to produce: team alignment, continuous improvement, stakeholder feedback, adaptive planning. When they stop producing those outcomes – or when they never started – continuing to perform them is not Agile practice. It is ritual for its own sake.

The Pacific islanders eventually stopped building wooden airplanes. Not because they were told to, but because the evidence accumulated over time that the airplanes were not bringing the cargo. Evidence accumulation requires looking honestly at outcomes rather than activities.

Run the checksum on your Agile practice:

1. For each ceremony your team runs – what outcome is it designed to produce? Is it producing that outcome?
2. Name one concrete improvement that resulted directly from your last three retrospectives.
3. When did a ceremony last change your team’s plan or behaviour in a meaningful way?

If the answers are vague, the ceremonies are decorative. Decorative ceremonies are not Agile. They are the wooden airplanes of software development – built with care, maintained with diligence, and completely disconnected from the outcomes they were meant to produce.

“The checksum for any Agile practice is simple: what changed because of it? If the honest answer is nothing – the practice is cargo, not capability.” Markus – agile-checksum.com

---

Glossary Terms Used in This Article

• Cargo Cult Agile – The adoption of Agile rituals without understanding the underlying principles.
• Agile Manifesto – The 2001 document defining the values and principles of Agile software development.
• Retrospective – A Scrum ceremony for inspecting the sprint and identifying improvements.
• Definition of Done – The shared agreement on what “complete” means for a product increment.
• Sprint – A fixed time-box of 1-4 weeks in which a Scrum team delivers a potentially releasable increment.
• Sprint Review – A Scrum event where the team and stakeholders inspect the Increment and adapt the Product Backlog.