Extreme programming: Difference between revisions

Revision as of 16:48, 2 January 2003

Revision as of 22:08, 21 January 2003

Line 18:

#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);

#Testing code is good. Therefore, in XP, test suites 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 [[Rational Unified Process|RUP]] process is more appropriate in that case.