Main Page | See live article | Alphabetical index

Extreme Programming

Extreme Programming (XP) is a method in or approach to software engineering, formulated by Kent Beck, Ward Cunningham, and Ron Jeffries. Kent Beck wrote the first book on the topic, "Extreme Programming Explained: Embrace Change" (ISBN 0201616416). It is the most popular of several agile processes.

Fundamental characteristics of the method are:

These characteristics are only derivatives of principles that are known to be good, and are taken into extreme:
  1. Interaction between developers and customers is good. Therefore, an XP team is supposed to have a customer on site, who specifies and prioritises work for the team, and who can answer questions as soon as they arise.
  2. If learning is good, take it to extremes: Reduce the length of development and feedback cycles. Test early;
  3. Simple code is more likely to work. Therefore, extreme programmers only write code to meet actual needs at the present time in a project, and go to some lengths to reduce complexity and duplication in their code.
  4. If simple code is good, re-write code when it becomes complex;
  5. Code reviews are good. Therefore XP programmers work in pairs, sharing one screen and keyboard (which also improves communication) so that all code is reviewed as it is written;
  6. Testing code is good. Therefore, in XP, tests are written before the code is written. The code is considered complete when it passes the tests (but then it needs refactoring to remove complexity). The system is periodically, or immediately tested using all pre-existing automated tests to assure that it works. (See test-driven development)

In general, Extreme Programming is believed to be useful for small teams under 12 persons. Some think it can be useful for larger teams while some consider the Rational Unified Process more appropriate in that case. However, XP has been demonstrated successfully on a team of over a hundred developers. It's not that XP doesn't scale, just that few people have tried to scale it, and XPers refuse to speculate on this facet of the process.

Table of contents
1 Controversial Aspects
2 References
3 External links

Controversial Aspects

Most of the design activity takes place on the fly and incrementally, starting with "the simplest thing that could possibly work" and adding complexity only when it's required by failing tests. Unit-testing is a design discipline.

See also: Crystal Light Methods from Alistair Cockburn


External links