The XP renaissance
A reading list on Extreme Programming in the AI-assisted coding era. Eleven pieces written between early 2025 and early 2026, ordered by how central the voice is to the conversation rather than by date.
This tool ports the Pivotal Tracker workflow to plain markdown. The Pivotal way was always a port of Extreme Programming. The pieces below explain why XP practices that were once dismissed as expensive (pair programming, small batches, working agreements, real refactoring, short feedback loops) suddenly look essential when an AI agent is in the dev-pair seat.
Test-driven development is the practice these pieces most often cite. This project does not opine on testing, so TDD is the lens through which several of the entries below frame their case; pull the practice you care about and ignore the framing where it does not apply.
-
Augmented Coding: Beyond the Vibes
The creator of XP introduces the working term "augmented coding": pairing with an AI assistant while keeping XP discipline (vision, strategy, task breakdown, feedback loops). Distinguishes augmented coding from vibe coding, where there is no plan and no acceptance. The framing this project leans on.
-
The Future of Software Engineering with AI: Six Predictions
Gergely Orosz reports from Martin Fowler's invite-only "Future of Software Development" retreat. Names the return of Extreme Programming, which predates Agile, as one of the six major trends shaping the next phase.
-
Martin Fowler interview
Fowler on why LLM output has to be tested with deterministic checks, why refactoring matters more than ever now that the cost of producing code is near zero, and how AI tools combined with classical engineering technique are what teams actually need.
-
eXtreme Programming with Artificial Intelligence
From the XP 2025 conference itself: if you want to craft excellent software using AI, follow XP's values and practices. The official XP community's position.
-
The AI-Ready Software Developer #16: A Token of Our eXtreme
Names the phenomenon directly: in the age of AI-assisted programming, XP is experiencing a renaissance, though many of the people rediscovering it do not realise that the practices already have a name.
-
XP 3.0: AI Validates What Extreme Programming Got Right
The economics-flipped argument. XP practitioners had the discipline. The industry called the practices too expensive and ignored them for two decades. AI removed the cost objection.
-
Does AI + XP Make the Myth of Better, Faster AND Cheaper a Reality?
Among the Agile methodologies, XP practitioners are best positioned to use AI well: the principles XP runs on (collaboration, adaptability, rapid feedback) line up exactly with what AI agents need.
-
Should we revisit Extreme Programming in the age of AI?
Output creation is no longer the constraint. XP provides discipline and empathy, centering the team and elevating shared understanding above raw speed.
-
Extreme Programming Revisited
AI is dragging us, kicking and screaming, back to a purer form of XP. The list of practices that work well with AI-assisted development reads like a greatest-hits compilation from 1999.
-
Extreme Programming Revised with Generative AI Agents
Walks through the XP practices that teams have historically struggled to adopt and shows how generative AI lowers the barrier to entry on each one.
-
AI and Agile Software Development: A Research Roadmap from the XP2025 Workshop
Academic synthesis of the third consecutive year of AI-and-Agile sessions at the XP conference. Useful as a survey of what the research community considers worth studying about the AI-XP intersection.
How we got Scrum instead
The XP authors mostly chose authenticity over scale: they built no certification business and ran no marketing engine for it. Scrum took the opposite bet, packaged the process for managers, and won the decade. The pieces below are the XP authors' record of what that cost the industry, and why they think the bet aged badly.
-
Extreme Programming 20 Years Later
Beck's own retrospective on the XP journey at the fifth Lean IT Summit, covering what he got right, what he got wrong, and what he is still working on. Includes the admission that calling it "Extreme Programming" was itself a branding misstep that helped Scrum's friendlier wrapper win.
-
Dark Scrum
An XP author writing for four years about what Scrum became after marketing success: a version of Agile that is oppressive to developers because it ships the process without the engineering discipline. The page collects the full series.
-
The Land that Scrum Forgot
Uncle Bob's foundational talk on why Scrum-without-XP produces rotting code: speed without technical quality is not speed, and a project manager retitled as a scrum master is not engineering leadership. Cited everywhere; the case still holds.