Capability Maturity Model (CMM)

Purpose: To assess and help improve process in software development organizations.

A model for organizational improvement Benchmarks the process not the product

Special thanks to Software Productivity Consortium, Herndon, Virginia

What the CMM is not

Is not prescriptive; does not tell an organization how to improve
Does not limit the choice of life cycle Neither requires nor precludes specific software technologies, design method, coding, or testing practices Does not require that documentation conform to any particular set of standards (e.g., DOD-MIL-STD-498 or IEEE)

Structure of the CMM

Maturity Levels (1)

Maturity Levels (2)

The levels are well-defined evolutionary plateaus on a path to becoming a mature software organization. Each level is a layer in the foundation for continuous process improvement. There are five maturity levels. Achieving each level establishes a different component of the software process.

Maturity Levels (3)

Capability maturity levels:

Level 1: Level 2: Level 3: Level 4: Level 5: Initial Repeatable Defined Managed Optimizing Worst

Best

CMM Levels [1]

Initial The software process is characterized as ad hoc, and occasionally even as chaotic. Few processes are defined, and success depends on individual effort.

Lacks: Reasonable process

CMM Levels [1] (contd)

CMM Levels [2]

Repeatable Basic project management processes are established to track cost, schedule and functionality. The necessary process discipline is in place to repeat earlier successes on projects with similar applications. Lacks: Complete process

CMM Levels [2] (contd)

10

CMM Levels [3]

Defined The software process for both management and engineering activities is documented, standardized and integrated into a standard software process for the organization. All projects use an approved, tailored version of the organization's standard software process for developing and maintaining software. Lacks: Predictable outcomes

11

CMM Levels [3] (contd)

12

CMM Levels [4]

Managed Detailed measures of the software process and product quality are collected. Both the software process and products are quantitatively understood and controlled.

Lacks: Mechanism for process improvement

13

CMM Levels [4] (contd)

14

CMM Levels [5]

Optimized Continuous process improvement is enabled by quantitative feedback from the process and from piloting innovative ideas and technologies.

15

CMM Levels [5] (contd)

16

Improving Process Capability

17

Maturity Distribution
379 organizations in 1994

18

Key Process Areas (1)

19

Key Process Areas (2)

Identify a cluster of related activities that, when performed collectively, achieve a set of goals considered important for enhancing process capability. Are defined to reside at a single maturity level. Identify the issues that must be addressed to achieve a given maturity level. Eighteen KPAs in the CMM.

20

Focus & Key Process Area (1)

Initial (level 1)
Focus: Heroes

Repeatable (level 2)
Focus: Project management 6 KPAs:
Requirements management Software project planning Software project tracking Software quality assurance Software configuration management Software subcontract management

21

Focus & Key Process Area (2)

Defined (level 3)
Focus: Engineering process 7 KPAs:
Organization process focus Organization process definition Training programs Integrated software management Software product engineering Inter-group coordination Peer reviews

22

Focus & Key Process Area (3)

Managed (level 4)
Focus: Product and process quality 2 KPAs:
Quantitative process management Software quality management

23

Focus & Key Process Area (4)

Optimizing (level 5)
Focus: Continuous process improvement 3 KPAs:
Defect prevention Technology change management Process change management

24

KPA Goals (1)

25

KPA Goals (2)

Goals summarize the key practices for each of the KPAs Goals are important for enhancing process capability for that level of maturity Each key practice maps to one or more goals

26

Example of a KPA Goal

27

Common Features (1)

28

Common Features (2)

All KPAs have the same common features
Commitment to perform Ability to perform Activities performed Measurement and analysis Verifying implementation

Used to organize the key practices in each KPA Address implementation and institutionalization

29

Common Features (3)

Divided into two groups
Infrastructure
Commitment to perform Ability to perform Measurement and analysis Verifying implementation

Activities performed

30

Commitment to Perform
Describe the actions the organization must take to ensure that the process is established and will endure Typically include
Policies Sponsorship Responsibility

31

Ability to Perform
Describe the pre-conditions that must exist in the project or organization to implement the software process competently Typically include
Resources Structure and organization Delegation Training Orientation

32

Activities Performed
Describe the roles and procedures necessary to implement a KPA Typically include
Establishing plans and procedures Performing the tasks associated with the established plans and procedures Monitoring the progress of the tasks Taking corrective action when tasks deviate from plans

33

Measurement and Analysis

Describe the need to measure the process and analyze the measurements Typically include
Examples of measurements to determine the status and effectiveness of the activities performed

34

Verifying Implementation
Describe the steps to ensure that the activities are performed in compliance with the process that has been established Typically include
Review and audits with
Senior management Project management Software quality assurance

35

Importance of Institutionalization
The organization outlives those who leave it The organization culture must convey the process Management must nurture the culture Culture is conveyed with role models and rewards

36

Key Practices (1)

37

Key Practices (2)

State the fundamental policies, procedures, and activities associated with a KPA Describe what is done Organized by common features 316 key practices in the CMM

38

Example of a Commitment

39

Example of an Ability

40

Example of an Activity

41

Example of a Measurement

42

Example of a Verification

43

CMM Summary

44

CMM Documents

http://www.sei.cmu.edu/cmm/cmms/cmms.html

45