Minimum XP process Requirements
Extreme Programming (a la C3 project) requires 4 things:
You deliver an increment every three weeks.
You have a user on the team full time.
You have regression unit tests that pass 100% of the time.
Notes:
Mark Paulk states, “Since XP focuses on the software engineering process rather than the organizational infrastructure issues, this and other organization-level processes are areas that need to be addressed by organizations adopting XP, whether in a CMM-based context or not.” He explains, “Many of the key process areas partially covered or not addressed in XP are undoubtedly addressed in real projects.” XP encourages the methodology be used in whole and in spirit but does allow for additions, modifications and deletions when appropriate. Certainly additions will be necessary, with any hope, no deletions will be and if any modifications are, that they will be in the spirit of XP.
The XP methodology covers the process of software development but is weak in describing the management and organizational processes necessary to support the software development process. XP’s weakness in formalizing management and organizational processes can be shored up by using a quality framework such as the CMMI to define solid processes in these areas. As an approach to researching a CMMI compliant XP process the following topics were examined: a set of minimum XP processes, CMMI versions, specific examples of compliance problems, almost XP syndrome, and XP documentation philosophy.
Alistair Cockburn relates that, “Extreme Programming a la the C3 project requires 4 things...