Generative AI removes the natural constraint that expensive engineers imposed on software development. When building costs almost nothing, the question shifts from “can we build it?” to “should we build it?” The Agile Manifesto’s principles provide the discipline that these costs used to enforce. Ignore them at your peril when Ralph Wiggum meets Agile.
AI agents have long promised productivity gains, but until now, they demanded coding skills that most agile practitioners lack or are uncomfortable with. In this article, I share my first impressions on how Claude Cowork removes that barrier, why it is a watershed moment, and how you could integrate AI Agents into your work as an agile practitioner.
The A3 Framework categorizes AI delegation before you prompt: Assist (AI drafts, you actively review and decide), Automate (AI executes under explicit rules and audit cadences), or Avoid (stays entirely human when failure would damage trust or relationships). Most AI training teaches better prompting. The A3 Framework teaches the prior question: Should you be prompting at all? Categorize first, then prompt.
Without a decision system, every task you delegate to AI is a gamble on your credibility and your place in your organization’s product model. AI4Agile’s A3 Framework addresses this with three categories: what to delegate, what to supervise, and what to keep human.
Learn more about what is coming in Q1 of 2026.
Organizations resist change through immune responses: encapsulation, assimilation, exhaustion, redefinition, and expulsion. But immune systems attack what they recognize. Hence, if you are in the business of change and expect push-back, stop announcing transformations. Instead, to overcome the immunity response, start solving problems: The principles spread through practice, through demonstrations of value, not by proclamation.
This article is Part 3 of a three-part series. In Part 1, Agile Is Dead, Long Live Agility, we saw how the Agile brand became toxic while the principles spread faster than ever under different names. In Part 2, The Reformation That Became the Church, we traced how every disruptive movement hardens into the orthodoxy it opposed.
This final part answers the question we left open: Can you practice the principles without the apparatus? Yes. But only if you understand why organizations reject change and how to stop triggering that rejection.
The Agile Manifesto followed Luther’s Reformation arc: radical simplicity hardened into scaling frameworks, transformation programs, and debates about what counts as “real Agile.” Learn to recognize when you’re inside the orthodoxy and how to practice the principles without the apparatus.
This is Part 2 of a three-part series; check out Part 1: Agile Is Dead, Long Live Agility.
