Capability Maturity Model

A capability maturity model gives organizations a way to measure how well they do something and what improvement looks like. It replaces general impressions with shared, specific descriptions. It describes a series of levels, typically five, from ad hoc and unpredictable at the bottom to measured and continuously improving at the top. By comparing current practices with the descriptions at each level, an organization can see where it stands and what it needs to change to move up.

The original Capability Maturity Model was developed at Carnegie Mellon University's Software Engineering Institute for the US Department of Defense and published in 1991, to assess the reliability of software contractors. Its structure has since been adapted for many other areas, from project management and data management to enterprise architecture and FinOps. For enterprise architecture and IT finance, maturity models provide a practical way to assess capabilities, prioritize improvement and explain to leaders why investment is needed.

Definition of Capability Maturity Model

A capability maturity model is a structured description of how an activity or capability develops from informal to optimized practice. Each level describes characteristics, practices and outcomes that indicate a given level of maturity.

The original model focused on software development processes and was later succeeded by CMMI, Capability Maturity Model Integration. The general approach is widely used in capability-based planning to rate the maturity of business capabilities.

The Five Levels

At level 1, initial, processes are ad hoc and success depends on individual effort. Results are unpredictable. Much depends on a few experienced people, and results suffer when they leave.

At level 2, repeatable or managed, basic processes are established for individual projects or teams, so similar work can be repeated with similar results. Practices may still differ between teams.

At level 3, defined, processes are documented and standardized across the organization, and staff are trained to follow them. Many organizations treat level 3 as the target for most capabilities.

At level 4, quantitatively managed, processes are measured and controlled using data. At level 5, optimizing, the organization continuously improves processes based on measurement and new ideas.

Adaptations Beyond Software

Many fields use maturity models based on the same idea. The FinOps maturity model, for example, uses crawl, walk and run stages.

Enterprise architecture maturity models assess practices such as governance, information quality, stakeholder engagement and influence on decisions. They are often used as part of enterprise architecture management.

Business capability maturity models rate each capability on dimensions such as people, process, information and technology, often on a one-to-five scale. These ratings are usually recorded against the business capability model so they can be shown as heat maps.

Importance of Capability Maturity Models in Enterprise Architecture

Maturity models provide a common language for discussing capability. Instead of vague statements that a function is weak, leaders can agree on a specific level and its characteristics. This makes discussions about improvement more precise and less personal.

They help prioritize improvement. Comparing current and target maturity across capabilities shows where the largest and most important gaps lie. Gaps in capabilities central to the strategy usually deserve attention first.

They also make progress visible, since moving from one level to the next is a concrete, measurable goal. Teams can see what they need to do to reach the next level, which helps motivate improvement.

Linking Maturity to Investment

Maturity assessments help justify investment by showing the gap between current and required performance for capabilities that matter to the strategy.

Not every capability needs the highest maturity. Setting targets based on strategic importance prevents overinvestment in capabilities that are good enough. Moving up each level usually costs more than the one before, so targets should be chosen carefully.

Mapping technology spending to capabilities alongside their maturity shows whether money is going to the capabilities that most need improvement, which supports better budget decisions.

Repeating assessments after investments are made shows whether the spending improved capability as expected.

Limitations

Maturity ratings can be subjective. Different assessors may rate the same capability differently without clear criteria and evidence. Calibration sessions, where assessors compare ratings, improve consistency.

Higher maturity is not always better. Highly formal processes can slow down areas that need flexibility and speed. Innovation activities, for example, may perform best with lighter processes.

Models focused on process may overlook outcomes. A capability can follow well-defined processes and still deliver poor results for customers.