Extreme programming: Difference between revisions

Revision as of 14:53, 7 May 2003

Revision as of 17:02, 15 May 2003

Line 21:

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.

----

==Controversial aspects:Aspects==

See also: [[Crystal Light Methods]]

* Detailed specifications[[specification]]s are not written.

* A customer representative is attached to the project.

Reference:

* Programmers work in pairs.

* 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

-------

Controversial aspects:

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==

* 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