Extreme programming: Difference between revisions

Revision as of 13:56, 19 December 2002

Revision as of 13:58, 19 December 2002

Line 18:

#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 has programmers program in pairs, sharing one screen and keyboard; (this 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.

Line 27:

1. Requirements are addressed by having a customer on-site, available to the programmers. If this is not possible, the customer may describe use cases on cards, that are periodically photocopied for the engineering staff.

See also: [[Crystal Light Methods]]

Reference:

* Kent Beck, ''Extreme programming explained'', Addison Wesley, 2000

-------