Slide 3 of 17
Notes:
Dangers abound with XP but the following points are highlighted to give the reader a preview of the problems: Project Restrictions, Process versus Process Improvements, Local Optimization, and Magic.
There is a small set of project environments that the XP methodology can successfully be applied to- software only, small teams, and a clearly definable cooperative customer. It is a non-scalable process as a whole and claims it needs to be whole to reap the most benefit.
The Capability Maturity Model Integration (CMMI) models emphasize complete coverage of the “what” of the model but the “how” is left to the organization or project and needs to make business sense. XP emphasizes complete coverage of the process specifying the “how” and it does not fit non-detrimentally within as many business environments.
Ian Alexander states in The Limits of eXtreme Programming, "Maxims like, do the simplest thing that could possibly work, do not necessarily lead to optimal solutions."
As Stephen J Mellor refers to the problem, “Why shouldn’t we write it down? Is something else going on? I think the answer to that is Yes. That something else is, bear with me here, the mysticism of creation. If you write it down, the (witch doctor’s) magic will go away and it won’t work any more. If you really examine it, and (again write it down, it won’t be “special” and it won’t work.”
