CMM vs CMMI: Understanding both ends

Both CMM (Capability Maturity Model) and CMMI (Capability Maturity Model Integrated) are Software Engineering Institute’s (SEI) most popular examples of a process improvement approach. These two model-based approaches are found distinct from each other. Specifically, CMM is found to be restricted to management and software engineering applications or practices only, whereas CMMI magnifies the CMM to work on both systems engineering and an integrated product development. In addition, CMMI is essentially established based on some identified set of process areas (PAs). These identified PAs are separated into groups, which are related to the maturity levels.

Particularly in CMMI, part of this approach’s maturity level 2 or the Managed phase, is considered as the most fundamental management applications. In addition, CMMI’s Level 3 or the Define phase focuses on software engineering practices; Level 4 or Quantitatively-managed phase concentrates on the quality management of company process and product; and Level 5 or Optimizing phase, which involves certain procedures for optimizing process and managing technology changes.

However, whether it is CMMI or CMM, still both manifest that any organization noted to climb up the ladder of maturity increases its chance to improving both its organization and business objectives and process. Similarly, this holds true in producing high quality products and services. So the higher the level is accomplished, the greater opportunity for the organization to achieve an increase in quality productivity and with shorter product cycle time.

Regardless of CMMI and CMM having distinct differences, still both models compliments each other in some aspects or areas. With both models having numerical level of measurement, any organization that may consider carrying out either of this would have an opportunity to develop and improve both organizational and business processes, products, and services.