Extreme programming: Difference between revisions

Revision as of 21:50, 17 November 2023

Revision as of 17:29, 8 January 2024

Line 171:

* Requirements are defined incrementally, rather than trying to get them all in advance.

* Software developers are usually required to work in pairs.

* There is no [[Bigbig Designdesign Upup Frontfront]]. Most of the design activity takes place on the fly and incrementally, starting with <span id="SimplestThingThatCouldPossiblyWork"></span>"the simplest thing that could possibly work" and adding complexity only when it's required by failing tests. Critics characterize this as "[[debugging]] a system into appearance" and fear this will result in more re-design effort than only re-designing when requirements change.

* A [[customer representative]] is attached to the project. This role can become a single-point-of-failure for the project, and some people have found it to be a source of stress. Also, there is the danger of [[micro-management]] by a non-technical representative trying to dictate the use of technical software features and architecture.