Extreme Programming (XP) is a method in or approach to software engineering, formulated by Kent Beck, who wrote the first book on the topic, "Extreme Programming Explained: Embrace Change" (ISBN 0201616416). It is one 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:
- Interaction between developers and customers is good. Therefore, an XP team is supposed to have a customer on site, who can answer questions as soon as they arise.
- If learning is good, take it to extremes: Reduce the length of feedback cycles. Test early;
- Simple code is more likely to work. Therefore, extreme programmers only write code to meet actual needs in the present project;
- If simple code is good, re-write code when it becomes complex;
- 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;
- Testing code is good. Therefore, in XP, test are written before the code is written. The code is considered complete when it passes the tests. 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 10 persons. Some think it can be useful for larger teams while some consider the RUP process is more appropriate in that case.
- Detailed specifications are not written
- A customer representative is attached to the project
- Programmers work in pairs
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.
See also: Crystal Light Methods[?]
References & External Links
All Wikipedia text
is available under the
terms of the GNU Free Documentation License