The Agentic Agile Manifesto
Agile's four values, rewritten for teams where AI generates code. When the coding bottleneck collapses, ceremony overhead becomes the problem.
The efficiency bottleneck moved
The Agile Manifesto (2001) was a response to heavyweight waterfall processes where human coding speed was the constraint. Its values were calibrated for that bottleneck: working software over documentation, responding to change over following a plan.
AI changes the constraint. Mid-to-senior-level code now arrives in seconds, not days. AI is text-centric, stateless, runs without ego or fatigue. The coding bottleneck has collapsed. What remains is the coordination overhead Agile itself introduced: sprint planning, daily standups, retrospectives, backlog refinements. Ceremonies designed to synchronize human coders now consume the capacity that AI freed up.
The efficiency problem is no longer "how fast can engineers write code." It is: how precisely can teams specify what to build, and how fast can they validate what AI delivers.
Four values, rewritten
We are uncovering better ways of building software by doing it with AI systems as co-authors of engineering work. Through this practice, we have come to value:
Engineers unable to delegate work to AI become bottlenecks, regardless of process maturity. An AI-fluent engineer with a clear spec out-delivers a ten-person Scrum team with a vague backlog. Invest in the human's ability to specify, verify, and orchestrate, not in ceremony frameworks that assume coding is the constraint.
Machine-readable specifications (precise enough for AI to execute without reinterpretation) replace both vague user stories and exhaustive documentation. A seven-component Executable User Story (user story, prototype, NFR, architecture decision, Gherkin scenarios, test data, estimate) is not comprehensive documentation. It is the minimum sufficient spec. Anything beyond the minimum is waste; anything below it is ambiguity that AI ships as a bug.
AI enables rapid prototyping that produces tangible, testable artifacts, not wireframes or slide decks. Prototype-first delivery means the client validates intent before a line of production code is written. The feedback loop compresses from sprint-end to prototype-approval. Contract negotiation becomes obsolete when the client approves a working prototype at the start of each Stint.
AI enables real-time re-estimation and roadmap recalculation. A quarterly Executable Product Roadmap, Stint-projected with delivery costs per item, can be updated when priorities shift, without ceremony. Two-week sprint commitments made sense when re-planning cost days. When re-planning costs hours, fixed iterations become an artificial constraint on responsiveness.
That is, while there is value in the items on the right, the shift in engineering economics demands we weight the items on the left more, and recognize that Agile's original values remain valid. They were calibrated for a constraint that no longer dominates.
What Agentic Agile keeps
Agentic Agile does not discard Scrum's foundations. Three contributions remain intact:
- Iterative delivery. Ship working software at a defined cadence, not big-bang releases. RACE Programming keeps this as the Stint: a 1-week cycle by default, flexing to the client's release cadence, prototype-first.
- Cross-functional teams. One team owns delivery end-to-end without hand-off silos. RACE Programming keeps this: Pit Wall + Pit Crew is a single accountable unit.
- Visible backlog. Work is explicit and prioritized. RACE Programming extends this: the Executable Product Backlog requires every item to be a fully-specified Executable User Story before it enters Pit Crew.
What Agentic Agile eliminates: the ceremony overhead built to synchronize a 7-9 person team that a 2-3 person Pit Crew never needs, story points that cannot measure AI output, and sprint commitments that assume the coding bottleneck still dominates.
From writer of code to orchestrator of value
The central shift Agentic Agile names: the human engineer is moving from a writer of code to an orchestrator of valuable tasks. This is not a demotion. It is a concentration of leverage. One engineer now contributes more per hour than the engineer who types code faster: the one who specifies what AI cannot guess, verifies what AI cannot judge, and validates what the client cannot express on their own.
AI fluency, the ability to delegate work precisely to AI systems, becomes the primary professional competency. Teams that develop it compound their advantage. Teams that treat AI as a faster code editor do not.
From principles to practice
Agentic Agile is the bridge between the AI-First Manifesto (values for AI-native engineering) and RACE Programming (the prescriptive framework). It speaks the language of Scrum practitioners (sprints, ceremonies, velocity, story points) and names precisely what changes and why.
If your team uses Scrum, the From Scrum transition guide maps every Scrum artifact, role, and ceremony to its RACE Programming equivalent, with a 90-day transition plan and the metrics to validate it worked.
The Agentic Agile series is published on LinkedIn with post-by-post commentary, practitioner questions, and case evidence. Posts 1 and 2 introduced the problem and the four values. The series continues with AI fluency, machine-readable specs, prototype gates, team structure, and economics.