Extreme programming: Difference between revisions

Content deleted Content added
remove whom tag, agent present
m Replaced unclear “and All That” (sic) with “etc.”; italicized likewise unclear “'Project Lifecycles: Waterfall” reference
Line 186:
Certain aspects of XP have changed since the publication of ''Extreme Programming Refactored''; in particular, XP now accommodates modifications to the practices as long as the required objectives are still met. XP also uses increasingly generic terms for processes. Some argue that these changes invalidate previous criticisms; others claim that this is simply watering the process down.
 
Other authors have tried to reconcile XP with the older methodologies in order to form a unified methodology. Some of these XP sought to replace, such as the [[Waterfall model|waterfall methodology]]; example: ''Project Lifecycles: Waterfall'', [[Rapid Application Development]] (RAD), and All Thatetc. [[JPMorgan Chase & Co.]] tried combining XP with the computer programming methods of [[capability maturity model integration]] (CMMI), and [[Six Sigma]]. They found that the three systems reinforced each other well, leading to better development, and did not mutually contradict.<ref>[http://www.sei.cmu.edu/library/assets/jarvis-gristock.pdf Extreme Programming (XP) Six Sigma CMMI].</ref>
 
== Criticism ==