Capability Maturity model for software development programmes

1. The Essence of
Capability Maturity
Model (CMM)
Professor &Professor &
LawyerLawyer
Puttu Guru PrasadPuttu Guru Prasad
VVIT-Nambur
93 94 96 98 98

2. What is Capability Maturity
Model (CMM)?
 Definition:
” A framework that describes the key
elements of an effective software
process. It's an evolutionary
improvement path from an immature
process to a mature, disciplined
process. “

3. CMM (Cont.)
 CMM for Software (SW-CMM)
 CMM for Management of Human resources
(P-CMM)
 CMM for Systems engineering (SE-CMM)
 CMM for Integrated product development
(IPD-CMM)
 CMM for Software Acquisition (SA-CMM)

4. CMM (Cont.)
 History of CMM
 Introduced by SEI fellow, Watts Humphrey
from IBM in 1986.
 Introduced on the demand from Department
of Defense.

5. Internal Structure of CMM

6. Maturity Levels
 Initial Level – Adhoc, Unpredictable , Lack of
Management.
 Repeatable Level- Encourages repetition of
successful practices
 Defined Level- Identifies best practices
 Managed Level- Sets quantitative and quality
goals
 Optimizing Level- Removal of waste,
continuous improvement.

7. Benefits of Capability
Maturity Model
 At level 2 : Avoid “Death Marches” experienced
in Level 1.
 At Level 3: View historical data to come up with
best measures.
 At Level 4 : Identify the root causes and make
improvements with predictable efforts.
 At Level 5: Continuous Improvement.

9. Case Study for Raytheon
 When their processes were immature,
between 30 percent and 50 percent of their
development effort was spent on fixing
mistakes.
 It took six years for Raytheon to move from
Level 1 to level 4
 After applying CMM Raytheon was able to
save $9.2 million from their software
development cost of $115 million.

10. Raytheon (Cont.)
 At each level, they continued to reduce rework
and increase the percentage of effort involved in
the original development activity.
 After reaching Level 3, their productivity
increased by 230% from their starting baseline.
 By the time they moved to Level 4, they were
producing software for 40 % of their original
costs.

11. Raytheon (Cont.)

12. What CMM does not address
 Address expertise in a particular application
domain.
 Advocate specific tools, methods or software
technologies, or address issues related to
human resources.
 Address issues related to concurrent
engineering, team work change management, or
systems engineering.

13. Conclusion
 Capability Maturity Model applies to new
product development as well as software
development.
 CMM identifies practices for a mature
software process and provides examples of
the state of the practice (in some cases state
of the art)
 It is not meant to be either exhaustive or
dictatorial.