The History of CMMI
In the 1930s, Walter Shewhart began work in process improvement with his principles of statistical quality control [Shewhart 1931]. These principles were refined by W. Edwards Deming [Deming 1986], Phillip Crosby [Crosby 1979], and Joseph Juran [Juran 1988].
Watts Humphrey, Ron Radice, and others extended these principles even further and began applying them to software in their work at IBM and the SEI [Humphrey 1989]. Humphrey's book, Managing the Software Process, provides a description of the basic principles and concepts on which many of the Capability Maturity Models (CMMs) are based.
The SEI created the first CMM designed for software organizations and published it in a book, The Capability Maturity Model: Guidelines for Improving the Software Process [SEI 1995].
Figure 1.2 illustrates the models that were integrated into CMMI, Version 1.2. Developing the CMMI Product Suite involved more than simply combining some existing model materials. Using processes that promote consensus, the CMMI Product Team built a framework that accommodates multiple constellations and benefits multiple industries and areas of interest.
Some service providers attempted to use the CMMI-DEV model to address their process improvement needs, but the fit required some difficult interpretations.
Then, in 2006, Northrop Grumman approached the CMMI Steering Group with the idea of a distinct CMMI for Services model. The Steering Group approved the idea, and as a result, Northrop Grumman sponsored and led a volunteer industry team. This team eventually joined with the SEI to finish developing a pilot draft of a CMMI for Services model.
After collecting piloting results and feedback from the draft's use, the CMMI-SVC development team updated and improved the draft to be what it is today, CMMI-SVC, V1.2, the model contained in this book.