Why does a software consultancy name itself after battle formations?

It is a fair question, and the honest answer is that the imagery is doing real work. Cooper Agile's delivery model has an unusual property: every part of it has a plain operational meaning, and every part is easier to remember because of a slightly overwrought metaphor. This article explains the naming system in one narrative — what each term means operationally, and why the business argument underneath is serious even though the wordplay is not.

FORT: a fortnight, a fortification, a foray

The name of the delivery cycle is a deliberate triple meaning, and all three matter:

  • A fortnight. A FORT is a two-week delivery cycle: one bounded body of work, framed with acceptance criteria, realised with working evidence, transferred at the end. The timebox forces scope honesty.
  • A fortification. A business builds its fort over successive FORTs. Each cycle leaves something that works, is documented and is owned by your team. Dependability accumulates course by course, not in one heroic pour.
  • A foray. Each FORT is a bounded expedition: one defined objective, in and out, never an open-ended campaign. You always know what a FORT set out to do, and can inspect whether it did it.

Larger programmes are several linked FORTs, each with its own objective — a campaign of forays, if the register must be extended, though we will stop before anyone invents a siege metaphor.

The Foot Soldier

The person who executes a FORT is the Foot Soldier: a senior engineer who drops into any environment — your repositories, your tooling, your processes, your compliance landscape — and is productive within days. The role is named for the unglamorous truth of delivery: outcomes come from a capable person on the ground, not a process diagram. Foot Soldiers are senior by design; the model does not work with junior staff learning on your budget, a constraint we return to below.

The phalanx

When a FORT needs more than one soldier, they fight in formation — the phalanx. The image is interlocked shields: each person covers the gaps another leaves, and nobody fights alone. And the phalanx has a second, more deliberate echo: the agile methodology Scrum took its name from the rugby scrum, and a phalanx and a scrum are the same idea — coordinated strength, binding together, the individual amplified rather than exposed by the formation.

The five Cooper roles are the ranks of the formation:

  • Delivery Coordinator — owns the acceptance criteria and the cadence.
  • Capability Lead — the senior technical authority, accountable for what ships.
  • Specialist Engineers — the Foot Soldiers, doing the work in your environment.
  • Automation Engineer — builds the instrumentation that makes evidence automatic.
  • Quality & Evidence Lead — keeps the proof honest: tests, reviews, traceable decisions.

Formation assembly is what the ORCHESTRATE stage does; Transfer disbands it cleanly, with capability left in your hands.

PHAT: the discipline that keeps a formation set

A formation without measurement drifts — shields wander, gaps open, and the whole thing walks in a slow circle while looking busy. The discipline that keeps the phalanx set is PHAT: Precision (agree the exact numbers and acceptance criteria before work starts), Heuristic (fast weekly signals a human scans), Analytical (scheduled deep dives), Tracking (continuous instrumentation so evidence accumulates without heroics). A phalanx stays phat the way any disciplined formation stays tight: constant small corrections against a shared picture of where everyone actually is.

Illustrative example: a mid-sized logistics firm needs a fragile integration rebuilt without disrupting daily operations. One FORT is framed: acceptance criteria written with the firm's operations lead. The Delivery Coordinator runs the cadence; two Specialist Engineers work inside the firm's own systems; the Automation Engineer stands up telemetry so the new integration's health is visible from day one; the Quality & Evidence Lead keeps the test record. Two weeks later the integration ships, demonstrated against the acceptance criteria, with a runbook and a trained internal owner. The phalanx formed, fought, disbanded — and the fort is one wall stronger. Nobody fought alone, and nobody stayed.

The argument underneath the imagery

Strip the metaphor away and the claim is a business one: small coordinated senior teams, working to shared evidence, outperform both lone heroes and large layered teams for bounded engineering outcomes. The lone hero is fast until they leave, and then the knowledge leaves with them. The large layered team absorbs its own weight — account layers, blended rates, coordination costs — before it delivers anything. The formation is the third shape: enough people to cover the problem, senior enough to need little supervision, bound tightly enough that nobody fights alone, and honest enough about evidence that progress is visible rather than asserted. The metaphor exists to make that model memorable. We are aware of how it sounds. It has survived every attempt to sound more dignified, because everyone remembers it — which is, after all, the point.

Constraints and trade-offs

Two honest limits, in keeping with the house style:

  • Metaphors help until they obscure. The imagery is a memory device, not a licence to keep soldiers camped on your lawn. The formation disbands when the engagement ends — TRANSFER means your team holds the capability, and there is no dependency theatre with ranks that linger.
  • The model depends on genuinely senior people. Foot Soldiers who are productive in any environment in days are rare, and availability is the real constraint on the model — which is why engagements are bounded, scheduled, and taken on deliberately rather than sold by the hectare.

Your action checklist

  • Sketch your current problem as one bounded objective — a single FORT's worth of foray.
  • Ask whether your last engagement left a wall behind, or just a invoice.
  • Count the layers between you and the people actually doing your work.
  • Check whether your team fights alone anywhere — a single point of knowledge, a single pair of hands.
  • Agree the acceptance criteria before any work starts, and write them down.
  • Decide what evidence would prove a FORT succeeded, before it begins.

If the formation sounds like the shape your problem needs, our fractional capability page shows how FORTs, Foot Soldiers and phalanxes are actually engaged. For the short version, our one-pager covers the model on a single page. And to see the discipline that keeps a formation set, our reporting, analytics and monitoring practice is PHAT in operation — precision first, phalanx throughout.