Outcome-Driven Development

From Death Marches & Story Points to Sovereign Fleets & Outcome Contracts

“The story does not die in the AI era; it evolves from a labor estimation into an outcome contract.”

The Manifesto

Before Agile, the software industry was dominated by the “Death March.” Executives would promise clients impossible deadlines in December, arbitrarily rewrite the scope in October, and force engineering teams to sleep under desks.

Story points, the Definition of Done (DoD), and edge-case mapping were originally engineered as a shield against management abuse:

  1. Feasibility & Negotiation: Forcing stakeholders to reckon with the physics of time and complexity.
  2. Clarity for Quality Engineering: Providing legally binding contracts of verified behavior.
  3. Resilience via Tests: Bounded scope verified by test suites that survive pivots.

Over the last decade, middle management co-opted that shield and forged it into a surveillance whip. Velocity was weaponized; ticket sizing became a compliance tax rather than an engineering safeguard.

The Machine Shift

When executing with an autonomous AI fleet, the constraints invert:

  • Zero Biological Fatigue: Machine fleets do not sleep, burn out, or require psychological padding.
  • Obsolescence of Labor Sizing: Sizing a ticket (1, 3, 5, 8 points) to measure human sweat becomes irrational when orchestrating tireless compute.
  • Hyper-Inflation of the Definition of Done: Vague instructions generate garbage at the speed of light. Scope must be defined not by hours, but by The Brake Check: explicit quality vectors, deterministic edge-case tests, and an unyielding Definition of Done.

The human engineer ceases to be the physical RAM and labor of the factory. The Sovereign Architect operates as the Reviewing Authority—verifying the test contracts, setting the boundary vectors, and delivering finality.

The Volumes

Below is the architectural map of the book. Read through the volumes or follow the chapter navigation in the left sidebar: