Agile, CMMI®, RUP®, ISO/IEC 12207...
Francisco José López-Lira Hinojo · ACM SIGSOFT Software Engineering Notes · 2014
Sometimes, a new software development project requires selecting or proposing a particular model, methodology, or method, called generically a Set of Practices (SoP). In this paper, we provide a two-dimensional model for classifying and thus better understanding where the different SoPs fit in for software development. The model is applied to 27 different SoPs and the results are used to generate basic guidelines for decision support. SoPs vary in both complexity (height) and specialization (width). The larger the area (height x width) the more time needed for implementation of the SoP. We suggest the following advice: Make sure to establish a well-planned implementation project. Make sure the SoP contains everything you need. Combining SoPs can lead to success or failure, so be careful. Consider quality, productivity and volatility of requirements in your decision. Decide whether you need an SoP for one project or permanently. Don't design an SoP yourself, at least not for the first time.