Appendix C: ImplementationOperations Plan Template

8. CMMI was the result of overwhelming demand across the industry.

While there were some requests that we personally knew about (from DoD aerospace contractors), most organizations were busy using the CMM for Software, with a lesser number of organizations implementing the Systems Engineering Maturity Model. However, some organizations wishing to expand the sphere of influence of the CMM for Software to a more enterprisewide application simply took the word "software" out of the CMM, and used the CMM across their enterprise. After all, the CMM was touted as being based on project management principles that could be expanded to include almost any type of project. Several presentations from organizations at the 2002 European SEPG Conference in Amsterdam described their efforts tailoring the CMM for more than software tasks , and these organizations seemed to have been quite effective in this deployment. While there may have been a DoD mandate for the generation of this model and the integration of all existing models, we know of no large outpouring of grief that an integrated model had not been created.

And is the CMMI really one integrated model? Well, if you can select the disciplines, and you can divide it up into systems engineering, software engineering, IPPD, and supplier sourcing, then ” no. While the areas are interrelated, they are not really integrated into one seamless model.