Capability Maturity Model Integration

Capability Maturity Model Integration
Name	Capability Maturity Model Integration
Acronym	CMMI
Developer	Carnegie Mellon University Software Engineering Institute
Initial release	2000
Latest release	CMMI V2.0
Website	SEI CMMI

Capability Maturity Model Integration

Capability Maturity Model Integration is a process improvement framework used to guide organizations toward better practices for development, acquisition, and service delivery. It originates from standards and best practices codified by the Software Engineering Institute at Carnegie Mellon University and has influenced governance and quality programs across industries including aerospace, defense, finance, healthcare, and telecommunications. The model integrates ideas from systems engineering, software engineering, and project management to provide staged and continuous process improvement approaches.

Overview

CMMI synthesizes concepts from the ISO 9001 family, the IEEE standards, the Project Management Institute's PMBOK Guide, and management practices exemplified by organizations like Lockheed Martin, Raytheon, Boeing, Northrop Grumman, and General Dynamics. The framework maps process areas to maturity levels influenced by earlier models such as the Capability Maturity Model for software and draws on work by researchers at Bell Labs, contributors from Boeing Phantom Works, and consultants from firms like Accenture and Deloitte. CMMI's guidance interacts with regulatory regimes exemplified by the Federal Aviation Administration and procurement rules used by the United States Department of Defense and multinational corporations such as Siemens AG and Thales Group.

History

CMMI evolved from the original Capability Maturity Model developed in the late 1980s and early 1990s by teams including staff from the Software Engineering Institute and contributors connected to DARPA programs and the National Institute of Standards and Technology. The integration effort that produced CMMI involved stakeholders from industry, academia, and government such as IBM, Microsoft, HP, NASA, and General Electric. Major versions were released in 2000, 2002, 2006, and the significant modernization to CMMI V2.0 published with input from consultants at KPMG and standards bodies like ANSI. Adoption accelerated after endorsements by agencies including the United States Department of Defense and validation by audit firms like Ernst & Young.

Model Structure and Levels

CMMI organizes practice areas into process areas and capability levels modeled after staged frameworks used in ISO/IEC 15504 and influenced by continuous improvement cycles associated with thinkers like W. Edwards Deming and Joseph M. Juran. Typical maturity levels include Initial, Managed, Defined, Quantitatively Managed, and Optimizing—terminology shared with frameworks adopted by firms such as Intel Corporation, Motorola, 3M, Procter & Gamble, and Ford Motor Company. Process areas cover disciplines related to systems engineering, software development, acquisition, and service management, with links to bodies of knowledge like the INCOSE handbook, IEEE 12207, and best practices taught at institutions such as Massachusetts Institute of Technology and Stanford University.

Implementation and Assessment

Implementation typically involves gap analysis, process definition, training, and measurement programs executed by internal teams or external consultants from companies like PwC and Capgemini. Formal appraisals use methods analogous to audits conducted under ISO/IEC 17021 conformity assessment and may be performed by lead appraisers credentialed through the CMMI Institute and partners such as ISACA-affiliated professionals. Organizations pursuing maturity levels often coordinate with procurement offices like those at NASA or the UK Ministry of Defence and engage change management practices from firms such as Boston Consulting Group and McKinsey & Company. Metrics and statistical process control measures derive from work by Shewhart and are applied using tools from vendors like IBM Rational, Atlassian, Microsoft Azure DevOps, and Siemens Polarion.

Criticisms and Limitations

Critics including academics from Carnegie Mellon University departments and commentators in journals like the Harvard Business Review argue that CMMI can be bureaucratic, costly, and misaligned with agile methods promoted by proponents such as Kent Beck, Mike Cohn, Jeff Sutherland, and organizations like Scrum Alliance and Agile Alliance. Case studies from companies such as Yahoo! and commentators referencing failures at Nokia and Kodak highlight risks of overemphasis on process compliance over innovation and speed to market. Others note interoperability challenges with standards like ISO/IEC 27001 and conflicts with lightweight frameworks used by startups in ecosystems represented by Y Combinator and Techstars.

Variants and Industry Applications

CMMI has been tailored into variants for services, acquisition, and development used in sectors including defense contracting with firms like BAE Systems and Thales Group, financial services at JPMorgan Chase and Goldman Sachs, healthcare systems at Mayo Clinic and Cleveland Clinic, and software product firms such as Adobe Systems and SAP SE. Hybrid approaches combine CMMI with ITIL for service management, COBIT for governance at enterprises like HSBC and Barclays, and agile scaling models exemplified by Scaled Agile Framework adopters including Spotify-like organizations. Academic programs at Carnegie Mellon University, University of California, Berkeley, and Georgia Institute of Technology include CMMI concepts in curricula for students entering roles at companies including Amazon, Google, and Facebook.

Category:Process improvement