WHEN AGILE BECOMES CARGO CULT

During World War II, allied forces landed on remote South Pacific islands, constructing airstrips and delivering canned goods, radios, and medicine. When the war ended and the soldiers left, indigenous islanders built mock airstrips out of bamboo, carved wooden headphones, and marched with carved rifles, waiting for airplanes to land again.

This is cargo cult thinking: faithfully replicating the outward ceremonies of a system in the belief that the artifacts will conjure the underlying result.

In many corporate transformation, Agile has largely become a cargo cult.

The Symptoms of Cargo Cult Agile

Walk into an organisation undergoing an "Agile transformation", and you will observe:

• Daily standups that have turned into 45-minute status interrogations where 15 people recount their calendars while staring at their phones.
• Scrum masters acting as administrative Jira scribes.
• Massive "Scaled Agile" release trains that synchronize 30 squads to deliver the same monolithic, delayed scope as a traditional waterfall programme, but with 400 new sticky notes.
• A refusal to maintain architectural blueprints, strategic roadmaps or multi-month dependencies because "we're agile and responding to change."

Where Agile Breaks in Complex Transformation

Agile originated in small, co-located software teams with autonomous codebases and immediate customer feedback loops. But in enterprise transformations — where you are integrating legacy mainframes, complying with strict regulatory rules across multiple jurisdictions, and managing vendor contracts — squads are never truly autonomous.

If Squad A cannot release until Squad B refactors a 30-year-old database table, and Squad B is scheduled three sprints later, you do not have an agile flow. You have a critical path problem masquerading as a sprint backlog.

Pragmatism Over Dogma

True agility is not religious compliance with Scrum rituals. It is the organizational ability to discover truth rapidly and change direction without institutional panic:

1. Acknowledge hard architecture constraints: Stop pretending dependencies don't exist. Map them explicitly.
2. Focus on working software over sprint velocity: Velocity is easily gamed by splitting stories. What matters is working value delivered into production.
3. Blend governance with autonomy: Give teams freedom on execution while retaining tight, objective governance over milestones and regulatory stage gates.