EXtreme Programming (XP) as a ‘minimum’ software process : a grounded theory

Abstract

Within the body of literature, much emphasis has been placed on the use of process models to support software development [1, 2, 3]. Despite this, there is significant variation in the software processes used by software companies. Analysis shows that many companies are deploying proprietary, tailored “good enough” or “minimum” process in their software development activity. But what is “minimum” process? What factors influence the composition of minimum process in software companies and why are these companies choosing to reject standard process models in favour of a tailored minimum?