---
title: "CMM key process areas and continuous improvement"
subject: "Software Engineering"
chapter: 9
key: "semester_5/software_engineering:cmm-continuous-improvement"
source: https://www.bctengineer.com/q/semester_5/software_engineering/cmm-continuous-improvement
site: BCT Engineering
---

# CMM key process areas and continuous improvement

Software Engineering · Chapter 9: Quality management

- Asked in: 2067 Ashadh (old course), 12 marks
- Video: [Capability Maturity Model ( CMM )](https://www.youtube.com/watch?v=xKqkwyq1D98) — Perfect Computer Engineer
- Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14
- Page: https://www.bctengineer.com/q/semester_5/software_engineering/cmm-continuous-improvement
- Whole chapter: https://www.bctengineer.com/md/semester_5/software_engineering/chapter-9

## Question

Explain how CMM encourages continuous improvement of software process. Describe various key process areas of CMM at various maturity levels.

## Short answer

CMM encourages continuous improvement through staged levels, clear next targets, KPA goals, cross-project learning, measurement feedback, and improvement at level 5. KPAs include level 2 project management, level 3 standard process and peer reviews, level 4 quantitative management, level 5 defect prevention and change management.

## Answer

The **Capability Maturity Model (CMM)** of the Software Engineering Institute (SEI) describes five levels of software process maturity: Initial, Repeatable, Defined, Managed and Optimizing. Each level is defined by a set of **key process areas (KPAs)** that an organization must perform well to reach it.

#### How CMM encourages continuous improvement

1. **Evolutionary, staged path:** CMM does not expect an organization to become excellent at once. It gives a ladder of small, achievable steps. Each level stabilizes some part of the process and becomes the foundation for the next level.
2. **Clear next target:** an assessment shows the current level and which KPAs are missing. The organization knows exactly what to improve next (for example, a level 2 company works on process definition, training and peer reviews to reach level 3).
3. **Goals for every KPA:** each KPA states goals and the practices needed to meet them, under five common features: commitment to perform, ability to perform, activities performed, measurement and analysis, and verifying implementation. Progress can therefore be checked objectively.
4. **Learning across projects:** at level 3 an organization-wide process is defined and kept in a process asset library. Lessons from each project are fed back into this standard process.
5. **Measurement-based feedback:** at level 4 process and product data are collected and analysed statistically, so problems are seen in numbers rather than opinions.
6. **Improvement built into the process:** at level 5 improvement itself becomes a normal, ongoing activity. Defect causes are analysed and removed, and new methods and tools are piloted and adopted in a controlled way.
7. **Repeated assessments:** organizations are reassessed periodically, which creates an improvement cycle: assess, plan, improve, measure, reassess.

```text
 Assess current level --> Identify weak KPAs
        ^                         |
        |                         v
 Measure results  <--  Improve practices
```

#### Key process areas at each maturity level

**Level 1: Initial**
- The process is ad hoc; success depends on individuals.
- No KPAs are defined.

**Level 2: Repeatable** (focus: basic project management)
- **Requirements management:** keep a shared understanding of requirements between customer and team, and control changes to them.
- **Software project planning:** make realistic estimates and plans for the work.
- **Software project tracking and oversight:** compare actual progress with the plan and take corrective action.
- **Software subcontract management:** select and manage qualified subcontractors.
- **Software quality assurance:** give management visibility into the process and products.
- **Software configuration management:** keep the integrity of work products throughout the life cycle.

**Level 3: Defined** (focus: organization-wide standard process)
- **Organization process focus:** set responsibility for process improvement activities.
- **Organization process definition:** develop and maintain the standard software process.
- **Training program:** develop the skills and knowledge of staff.
- **Integrated software management:** tailor the standard process for each project and manage the project with it.
- **Software product engineering:** carry out engineering tasks (requirements, design, code, test) consistently.
- **Intergroup coordination:** ensure groups such as development, testing and hardware cooperate.
- **Peer reviews:** remove defects early through reviews and inspections.

**Level 4: Managed** (focus: quantitative control)
- **Quantitative process management:** control process performance using measured data.
- **Software quality management:** set measurable quality goals for products and track them.

**Level 5: Optimizing** (focus: continuous improvement)
- **Defect prevention:** find root causes of defects and remove them so they do not happen again.
- **Technology change management:** identify, evaluate and introduce new tools and technologies in an orderly way.
- **Process change management:** continuously improve the organization's processes to raise quality and productivity and shorten development time.

**Summary of KPAs**

| Level | Number of KPAs | Main theme |
|---|---|---|
| 1 Initial | 0 | Individual heroics |
| 2 Repeatable | 6 | Project management |
| 3 Defined | 7 | Process definition |
| 4 Managed | 2 | Measurement |
| 5 Optimizing | 3 | Continuous improvement |

**Example:** a company at level 2 completes projects on time when they are similar to earlier ones, but each team works differently. By defining a common process, training staff and holding peer reviews, it reaches level 3. It then collects defect density and productivity data (level 4) and finally uses this data to find the main causes of defects and change its process (level 5). Each step makes the next one possible, which is how CMM drives continuous improvement.

## Check yourself

The answer's key points as multiple-choice questions, with the correct option and why.

1. How does CMM's staged structure encourage continuous improvement?
   A. It expects excellence at once
   B. It gives a ladder of achievable steps, each level being the foundation for the next
   C. It removes the need for assessment
   D. It fixes the process permanently
   Answer: B. CMM provides an evolutionary path where each level stabilizes part of the process and supports the next. (Key point: Staged path)

2. Why are repeated assessments useful?
   A. They rank employees
   B. They replace KPAs
   C. They create an improvement cycle: assess, plan, improve, measure, reassess
   D. They only produce certificates
   Answer: C. Assessment shows the current level and missing KPAs, giving a clear next target and a repeating improvement cycle. (Key point: Role of assessment)

3. Which set are the Level 5 (Optimizing) KPAs?
   A. Defect prevention, technology change management, process change management
   B. Quantitative process management, software quality management
   C. Training program, peer reviews, intergroup coordination
   D. Project planning, tracking, subcontract management
   Answer: A. Level 5 KPAs are defect prevention, technology change management and process change management. (Key point: Level 5 KPAs)

## Related in Software Engineering

- [Levels of CMM](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Acmm-levels) — Software Engineering, chapter 9
- [SEI CMM and quality; ISO versus CMM](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Acmm-vs-iso) — Software Engineering, chapter 9
- [Short note: Capability Maturity Model](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Acmm-note) — Software Engineering, chapter 9
- [CMMI levels and the top two levels](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Acmmi-levels) — Software Engineering, chapter 9
- [Why software development is complex; man-month myth](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Acomplex-development) — Software Engineering, chapter 1

## Related in other subjects

- [Software process models and effort estimation](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Asw-process-models) — Instrumentation II, chapter 9, asked 2×
- [Embedded software development process](https://www.bctengineer.com/question.md?key=semester_6%2Fembedded_system%3Asoftware-development-flow) — Embedded System, chapter 3, asked 3×
- [Spiral model of software development](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Aspiral-model) — Instrumentation II, chapter 9, asked 3×