Extreme programming: Difference between revisions

Revision as of 14:03, 19 December 2002

Revision as of 01:52, 2 January 2003

Line 2:

'''Extreme Programming''' (XP) is a new [[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]].

For more information on this and related topics, see the definition at [[Ward Cunningham]]'s website, http://www.c2.com/cgi/wiki?ExtremeProgramming

Fundamental characteristics of the method are:

*short incremental and iterative [[programming]] steps

*continuous, often repeated automated [[unit test]], [[regression testing]]. See [[JUnit]].

*[[pair programming]]

*user interaction in the programming team

*fixing all known [[computer bug|bugs]] before adding functionality

*[[refactoring]]

*shaing ownership

These characteristics are only derivatives of principles that are known to be good, and are taken into extreme:

Line 32 ⟶ 31:

Reference:

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

*[[Ward Cunningham]]'s website, http://www.c2.com/cgi/wiki?ExtremeProgramming - For more information on this and related topics

-------