CMM and CMMI maturity models in Software Engineering - Step-by-Step Execution

Concept Flow - CMM and CMMI maturity models

Start: Organization wants to improve

↓

Assess current process maturity

↓

Identify maturity level (1 to 5)

↓

Implement improvements for next level

↓

Reassess maturity level

↓

Repeat until level 5 achieved

↓

Optimized processes

The flow shows how an organization assesses its current maturity, improves processes step-by-step, and moves through maturity levels from 1 to 5.

Execution Sample

Software Engineering

Level 1: Initial
Level 2: Managed
Level 3: Defined
Level 4: Quantitatively Managed
Level 5: Optimizing

This lists the five maturity levels organizations progress through in CMM and CMMI.

Analysis Table

Step	Action	Current Level	Improvement Focus	Next Level
1	Assess current processes	1 (Initial)	Identify basic project management	2 (Managed)
2	Implement project management processes	2 (Managed)	Standardize processes organization-wide	3 (Defined)
3	Define and document processes	3 (Defined)	Use metrics to control processes	4 (Quantitatively Managed)
4	Measure and control processes quantitatively	4 (Quantitatively Managed)	Focus on continuous process improvement	5 (Optimizing)
5	Continuously improve processes based on data	5 (Optimizing)	Maintain and innovate processes	5 (Optimizing)

💡 Reached highest maturity level 5; processes are optimized and continuously improved.

State Tracker

Maturity Level	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Organization Maturity	1 (Initial)	2 (Managed)	3 (Defined)	4 (Quantitatively Managed)	5 (Optimizing)	5 (Optimizing)

Key Insights - 3 Insights

Why does an organization start at Level 1 and not directly at Level 3?

Because Level 1 means processes are unpredictable and chaotic. The organization must first establish basic project management (Level 2) before standardizing and defining processes (Level 3), as shown in steps 1 and 2 of the execution_table.

What is the difference between Level 4 and Level 5?

Level 4 focuses on measuring and controlling processes with data, while Level 5 emphasizes continuous improvement and innovation of processes. This is clear in steps 4 and 5 where the focus shifts from control to optimization.

Can an organization skip levels in maturity?

No, the model is designed to be sequential. Each level builds on the previous one, as seen in the variable_tracker where maturity progresses step-by-step from 1 to 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the improvement focus at Step 3?

A Use metrics to control processes

B Standardize processes organization-wide

C Identify basic project management

D Focus on continuous process improvement

💡 Hint

Check the 'Improvement Focus' column in row for Step 3 in the execution_table.

At which step does the organization reach Level 4 maturity?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the 'Current Level' column in the execution_table to find when Level 4 is reached.

If an organization skips Step 2, what maturity level would it miss according to variable_tracker?

A Level 3 (Defined)

B Level 4 (Quantitatively Managed)

C Level 2 (Managed)

D Level 5 (Optimizing)

💡 Hint

Refer to the variable_tracker to see the progression of maturity levels after each step.

Concept Snapshot

CMM and CMMI maturity models guide organizations through 5 levels:
1. Initial - chaotic processes
2. Managed - basic project management
3. Defined - standardized processes
4. Quantitatively Managed - data-driven control
5. Optimizing - continuous improvement
Progress is sequential, improving process quality step-by-step.

Full Transcript

The Capability Maturity Model (CMM) and its successor CMMI describe how organizations improve their software processes. They start at Level 1 with unpredictable processes. By assessing current practices, organizations implement project management to reach Level 2. Then they standardize and document processes at Level 3. At Level 4, they use data to measure and control processes. Finally, Level 5 focuses on continuous process improvement. This step-by-step progression ensures stable, efficient, and improving software development practices.