Agile as Maneuver Warfare is Richards' structural parallel between Agile software development practices and military maneuver warfare doctrine — the approach to conflict that substitutes tempo, initiative, and disorientation for attrition-based firepower. The parallel is not merely analogical: Richards argues that Agile practices are effective for the same structural reasons that maneuver warfare is effective, because both instantiate john-boyd's organizational climate and OODA loop principles.
Maneuver Warfare vs. Attrition Warfare
Boyd's Patterns of Conflict traces the contrast between two fundamental approaches to military conflict:
Attrition warfare wins by consuming the opponent's resources faster than they can be replaced — more firepower, more soldiers, more materiel. It is fundamentally a resource competition, and the side with greater resources wins if they remain in contact long enough. World War I is the canonical example.
Maneuver warfare wins by disrupting the opponent's ability to act coherently — creating confusion, disordering the opponent's command, and generating situations faster than the opponent can reorient. It does not require resource superiority; it requires faster OODA cycling and the organizational climate that makes rapid maneuvering possible. The German Blitzkrieg and the Israeli performance in the 1967 Six-Day War are cited examples.
The Agile-Waterfall Parallel
Richards maps this contrast onto software development:
Waterfall as attrition: Large-batch software development — comprehensive upfront requirements, extended development cycles, late integration and testing — resembles attrition warfare's logic. The project succeeds by staying in contact with the original specification long enough to deliver it. Resource sufficiency and process adherence determine outcome. Like attrition warfare, it is vulnerable to any significant change in the environment (requirements change, market shift, technical discovery) that invalidates the original resource calculation.
Agile as maneuver: Iterative, incremental development — short sprint cycles, early feedback, continuous reorientation based on new information — resembles maneuver warfare's logic. Success comes from cycling through the observation-orientation-decision-action loop faster than requirements can become obsolete, delivering working software before the context changes, and using each sprint to reorient before the next. Like maneuver warfare, it does not require perfect upfront planning because it compensates with faster reorientation.
Specific Practice Parallels
Richards draws specific correspondences in certain-to-win and boyd-and-agile-talk:
Sprint cycles as rapid OODA cycling: Each sprint is a complete OODA loop — the team observes customer feedback and sprint review outputs, orients (planning), decides (sprint goal and backlog commitment), and acts (execution). Shorter sprints mean faster cycling and faster reorientation to changing requirements.
Cross-functional teams as mission-type orders: An Agile team with all disciplines represented (development, design, testing, product) can execute a sprint goal without waiting for external specialists — the team equivalent of Auftragstaktik (mission-type orders), where units have the capabilities to execute their mission without constant coordination with the hierarchy.
Sprint goals as Schwerpunkt: See schwerpunkt-as-focus. The sprint goal provides focusing intent that guides autonomous team decisions without specifying method.
Retrospectives as orientation update: The sprint retrospective is the organizational equivalent of reorienting after a OODA cycle — updating the team's understanding of its own process before the next cycle. This is the mechanism by which Agile teams improve their OODA cycling capability over time.
Why the Analogy is More Than an Analogy
Richards is explicit that this is a structural argument, not a marketing metaphor. The parallel holds because both maneuver warfare and Agile development are responses to the same structural problem: how do organizations operating in complex, fast-changing, uncertain environments maintain the ability to act coherently and adapt faster than the environment changes?
Boyd's answer — organizational climate that enables fast OODA cycling — applies in both domains because the structural problem is the same. The military practices and Agile practices differ in surface form but converge on the same solution because they address the same underlying challenge.
This is documented most fully through boyd-agile-bridge, which traces the intellectual lineage from Boyd to Agile through jeff-sutherland's explicit citations, and certain-to-win-framework, which provides the theoretical architecture connecting organizational climate, operating tempo, and competitive advantage across domains including software development and manufacturing.