I have long considered the case for ExtremeProgramming is made best by considering its connection and its dependency upon eXPert, eXperiencedProgrammers. XP works best when people "already" know what is a better way to approach a programming task, having "already" experienced similar processing problems and having arrived at satisfactory solutions. In my view, XP's successful results are more dependent upon that skill than upon the approach or method used. Teams have always worked best when work is carried out in an atmosphere of Cooperation, Concentration, and Consistency.
----
Consider this marketing paragraph from a company (here called Xp Company) using such processes:
* ''Xp company recognizes that each development project is different. It therefore does not believe that a sole methodology should be applied to all projects.''
* ''The key is to choose the parts of methodologies that are relevant and applicable to the individual project.''
* ''Saying that, there are some principles, techniques and best practices that Xp Company applies to all projects: H''''''ireTheBestPeople
** ''The '''number one factor''' effecting success is the people on the team. Waiting for and hiring the best people is key.''

''the above was extracted from http://www.byte-vision.com/Approach.aspx''

Factors mentioned:
* Hire The Best People
* Attack Risk Early
* Manage Project Goals and Requirements
* Test Early and Often
* Automated The Testing
* Keep It Simple
* Do not Overwork

-- DonaldNoyes.20080720.2201.m06

----
CategorySuccess