Capability Maturity Model (CMM)

An Capability Maturity Model (CMM) is a meta-model for capability maturity levels of different organizational capabilities (within an organizational discipline).

• Context:
  • It can (typically) apply to Organizational Processes.
  • It can (typically) provides a framework for identifying, understanding, and improving the processes that are used to create products and services.
  • It can (typically) be divided into levels of maturity, such as: Initial, Repeatable, Defined, Managed, and Optimizing.
  • It can describe how well (the behaviors, practices and processes of) an organization can reliably and sustainably produce required outcomes.
  • …
• Example(s):
  • a Software Development Capability Maturity Model, such as a CMMI or CMM-SW.
  • a Project Management Capability Maturity Model, such as CMMI-PM developed by the Project Management Institute.
  • a DevOps Capability Maturity Model, such as DCMM by the DevOps Institute.
  • a Data Management Capability Maturity Model.
  • a Data Analytics Capability Maturity Model, such as: a Data Science Capability Maturity Model.
  • an Open Information Security Maturity Model.
  • …
• Counter-Example(s):
  • A Quality Management System (QMS).
  • a Training Program, which can help people learn how to follow processes.
  • an Organizational Value Chain Model.
  • an Architecture.
• See: Process Improvement, Process Management, Software Engineering, Project Management.

---

---

References

2023

• (Wikipedia, 2023) ⇒ https://en.wikipedia.org/wiki/Capability_Maturity_Model Retrieved:2023-6-5.
  • The Capability Maturity Model (CMM) is a development model created in 1986 after a study of data collected from organizations that contracted with the U.S. Department of Defense, who funded the research. The term "maturity" relates to the degree of formality and optimization of processes, from ad hoc practices, to formally defined steps, to managed result metrics, to active optimization of the processes.

    The model's aim is to improve existing software development processes, but it can also be applied to other processes.

    In 2006, the Software Engineering Institute at Carnegie Mellon University developed the Capability Maturity Model Integration, which has largely superseded the CMM and addresses some of its drawbacks.

2017a

• (Wikipedia, 2017) ⇒ https://en.wikipedia.org/wiki/maturity_model Retrieved:2017-3-31.
  • Maturity is a measurement of the ability of an organisation for continuous improvement in a particular discipline (as defined in O-ISM3). The higher the maturity, the higher will be the chances that incidents or errors will lead to improvements either in the quality or in the use of the resources of the discipline as implemented by the organisation. Most maturity models assess qualitatively people/culture, processes/structures, and objects/technology. Two approaches for implementing maturity models exist. With a top-down approach, such as proposed by Becker et al., a fixed number of maturity stages or levels is specified first and further corroborated with characteristics (typically in form of specific assessment items) that support the initial assumptions about how maturity evolves. When using a bottom-up approach, such as suggested by Lahrmann et al., distinct characteristics or assessment items are determined first and clustered in a second step into maturity levels to induce a more general view of the different steps of maturity evolution. Topics that are covered in maturity models include:

2017b

• (Wikipedia, 2017) ⇒ https://en.wikipedia.org/wiki/Capability_Maturity_Model#Maturity_model Retrieved:2017-3-31.
  • A maturity model can be viewed as a set of structured levels that describe how well the behaviors, practices and processes of an organization can reliably and sustainably produce required outcomes.

    A maturity model can be used as a benchmark for comparison and as an aid to understanding - for example, for comparative assessment of different organizations where there is something in common that can be used as a basis for comparison. In the case of the CMM, for example, the basis for comparison would be the organizations' software development processes.

2017c

• https://en.wikipedia.org/wiki/Capability_Maturity_Model#Levels
  • There are five levels defined along the continuum of the model and, according to the SEI: "Predictability, effectiveness, and control of an organization's software processes are believed to improve as the organization moves up these five levels. While not rigorous, the empirical evidence to date supports this belief".
    1. Initial (chaotic, ad hoc, individual heroics) - the starting point for use of a new or undocumented repeat process.
    2. Repeatable - the process is at least documented sufficiently such that repeating the same steps may be attempted.
    3. Defined - the process is defined/confirmed as a standard business process
    4. Capable - the process is quantitatively managed in accordance with agreed-upon metrics.
    5. Efficient - process management includes deliberate process optimization/improvement.

2007

• (Crawfordent, 2007) ⇒ J. K . Crawfordent. (2007). “Project Management Maturity Model.” Boca Raton, FL: Auerbach Publications,

---