READING NOTE · UPDATED 2026
Connect XP practices to a feedback loop
Extreme Programming practices need an engineering context. Small releases, automated checks, collaborative design and customer feedback work together; adopting a ceremony alone cannot establish quality. Choose the constraint you are trying to address and observe whether a practice shortens useful feedback while preserving reliability. The original article provides the background for that discussion.
A practical next step
- Describe one costly feedback delay.
- Choose a small engineering practice that addresses it.
- Review both lead time and defects after the trial.
This 2026 reading note is written by the Durnall editorial team. Richard Durnall’s original text follows below.
Historical references checked in 2026
The original words remain below. References without a verified useful destination are plain text rather than links to an error or unrelated website.
- Kent Beck: The old domain now serves unrelated content.
Original publication: .
Original WordPress feed timestamp, UTC; the old theme’s local date may differ. Check the date source ↗
The original words below retain their period and attribution. The reading note above is the current editorial addition.
Source capture · 2008-01-09 ↗The history of Agile XP really begins in the lean production movement inspired and led by Toyota. For more information on the history of lean I recommend you start with my previous post on Lean Software Development. If you got here by accident when you were looking for ‘the PRINCE2 operational handbook’ then I suggest you click here “I Can’t Handle the Truth”.
A Bit of History
Agile XP began with the work performed at Daimler Chrysler AG in 1996 by Kent Beck and his co-conspirators on the Chrysler Comprehensive Compensation System (C3). The C3 project was an attempt to replace a number of existing COBOL legacy payroll applications with a single shiny new application developed in Smalltalk. Kent and his team introduced some process innovations that were published to the world through Ward Cunninghams WikiWikiWeb. These process innovations formed the foundation of the Agile XP methodology and were picked up by other practioners and also spawned a number of other closely aligned methodologies such as Scrum, Crystal and DSDM. In 1999 Kent’s book Extreme Programming Explained was published.
The Agile Manifesto
In February 2001 a group of representatives from the agile community, including those involved with C3, gathered at the Snowbird Ski Resort in Utah and over the course of a few days drafted and signed The Agile Manifesto. The agile manifesto is an attempt to gain consensus on the principles of software development that are the most important to us and most likey to lead to successful outcomes. As a side note, my colleague Martin Fowler was one of the original signatories of the manifesto and was also involved in the C3 project on a part-time basis.
The Agile XP Values
The Agile XP methodology was founded on five values:
- Communication
- Simplicity
- Feedback
- Courage
- Respect
The Agile XP Practices
Coding Practices:
- Code & Design Simply
- Refactor Mercilessly
- Develop Coding Standards
- Develop a Common Vocabulary
Developer Practices:
- Adopt Test-Driven Development
- Practice Pair-Programming
- Adopt Collective Code Ownership
- Integrate Continually
Business Practices:
- Add a Customer to the Team
- Play the Planning Game
- Release Regulary
- Work at a Sustainable Pace
The name Agile XP means Agile eXtreme Programming as it is intended to take each of these practices to the extreme.
Current State
Over the last ten years agile methods and Agile XP have been rapidly growing in popularity as the IT and business communities started to lose faith with traditional heavy-weight methods that were leading to repeated failures. Agile methods are currently as popular as ever and the introduction of lean concepts to IT is fueling further growth. Many of the traditional IT consulting organisations have created agile practices and many traditional conservative organisations, such as banks, have adopted agile processes.
Over the coming months I intend to look at the values and practices of Agile XP, investigate them in the context of lean and look at some of the techniques that leading edge practitioners are applying in the field in this area. Stay tuned.