The Capability Maturity Model

By Team #4

 

Overview

w  History

w  Description

w  Five Individual Levels

w  Statistics

w  Positive Aspects

w  Negative Aspects

 

History

w   Dept. of Defense established SEI in response to a perceived crisis in software development

w   Developed by the Software Engineering Institute (SEI) at CMU

w   Headed by Watts Humphrey, based on the earlier work of Phil Crosby

w   Introduced in 1991

 

What is the CMM !?!

w  Purpose:

w  A model for software companies to follow in order to “mature” and improve their software development processes.

w  A system for rating a software company’s process capabilities.  

 

Structure of the CMM

The 5 Levels of Maturity

w  Initial

w  Repeatable

w  Defined

w  Managed

w  Optimizing

 

Level 1 : Initial

w  Few defined processes

 

w  Ad hoc, chaotic

 

w  Focus on individual effort

 

Level 2 : Repeatable

w   Basic project management practices

w  Estimate size of project & resources required

w  Track progress

w  Implement software quality assurance

w  Planning & management of new projects

w  Ability to manage subcontractors

w   In a crisis, tend to revert to Level 1

 

Level 3 : Defined

w   Focus on the organization

w   Have established software development and maintenance practices

w   Also…

w  Set of coding standards, with training

w  Peer reviews evaluate quality

w  Integrated project management

w   In a crisis, level 3 practices are followed

 

Level 4 : Managed

w   Primary focus : process quality

 

w  Establish set of process measures

 

w  Establishment of quantitative quality goals

 

w  Quality and productivity are measured across all projects

 

w  Improve existing processes

 

w   Predictable. Software process operates within measurable limits.

 

Level 5 : Optimizing

w   Ability to create new processes

 

w   Help to introduce new technologies

 

w   Implement defect analysis & prevention

 

w   Goal : Strengthen the Process

 

Maturity Distribution

 

Trends in Maturity

 

Pros of CMM

w  Aids in the selection of contractors

 

w  Guides organizations towards improving the maturity of their software processes

 

w  Has been shown to be effective

 

Cons of CMM

w   No theoretical basis

w  a consensus among a group of theorists

w   Too much emphasis on the organization and less on individual effort

w   Can be very constrictive

w  Could prevent a company from reaching its full competitive potential