0% found this document useful (0 votes)
40 views

What Is Capability Maturity Model

CMM was first introduced in late 80's in U.S Air Force to evaluate the work of subcontractors. Later on, with improved version, it was implemented to track the quality of the software development system. The entire CMM level is divided into five levels: Level 1 focuses on uncertain requirements and ad-hoc processes; Level 2 introduces estimating, planning, and standards; Level 3 ensures products meet requirements; Level 4 quantitatively manages processes and sub-processes; Level 5 identifies and deploys improvements to meet objectives.

Uploaded by

Umesh Kumar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
40 views

What Is Capability Maturity Model

CMM was first introduced in late 80's in U.S Air Force to evaluate the work of subcontractors. Later on, with improved version, it was implemented to track the quality of the software development system. The entire CMM level is divided into five levels: Level 1 focuses on uncertain requirements and ad-hoc processes; Level 2 introduces estimating, planning, and standards; Level 3 ensures products meet requirements; Level 4 quantitatively manages processes and sub-processes; Level 5 identifies and deploys improvements to meet objectives.

Uploaded by

Umesh Kumar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

What is Capability Maturity Model (CMM) Levels?

 A maturity level is a well-defined evolutionary plateau toward achieving a mature


software process. Each maturity level provides a layer in the foundation for
continuous process improvement.
 In CMMI models with a staged representation, there are five maturity levels
designated by the numbers 1 through 5
1. Initial
2. Repeatable/Managed
3. Defined
4. Quantitatively Managed
5. Optimizing

What happens at different levels of CMM?


Levels Activities Benefits
Level 1 Initial At level 1, the process is usually None. A project is Total Chaos
chaotic and ad hoc
A capability is characterized on the
basis of the individuals and not of
the organization
Progress not measured
Products developed are often
schedule and over budget
Wide variations in the schedule,
cost, functionality, and quality
targets

By Mr. UMESH KUMAR, MCA (GGU) Page | 1


NET/SET/GATE/JRF OTHER EXAM
Level 2 Managed Requirement Management Processes become easier to
Estimate project parameters like comprehend
cost, schedule, and functionality Managers and team members spend
Measure actual progress less time in explaining how things are
Develop plans and process done and more time in executing it
Software project standards are Projects are better estimated, better
defined planned and more flexible
Identify and control products, Quality is integrated into projects
problem reports changes, etc. Costing might be high initially but goes
Processes may differ between down overtime
projects Ask more paperwork and
documentation
Level-3 Defined Clarify customer requirements Process Improvement becomes the
Solve design requirements, develop standard
an implementation process Solution progresses from being
Makes sure that product meets the "coded" to being "engineered"
requirements and intended use Quality gates appear throughout the
Analyze decisions systematically project effort with the entire team
Rectify and control potential involved in the process
problems Risks are mitigated and don't take the
team by surprise
Level-4 Manages the project's processes Optimizes Process Performance
Quantitatively and sub-processes statistically across the organization
Managed Understand process performance, Fosters Quantitative Project
quantitatively manage the Management in an organization.
organization's project
Level-5 Detect and remove the cause of Fosters Organizational Innovation and
Optimizing defects early Deployment
Identify and deploy new tools and Gives impetus to Causal Analysis and
process improvements to meet Resolution
needs and business objectives
Summary
CMM was first introduced in late 80's in U.S Air Force to evaluate the work of
subcontractors. Later on, with improved version, it was implemented to track the quality
of the software development system.
The entire CMM level is divided into five levels.
 Level 1 (Initial): Where requirements for the system are usually uncertain,
misunderstood and uncontrolled. The process is usually chaotic and ad-hoc.
 Level 2 (Managed): Estimate project cost, schedule, and functionality. Software
standards are defined
 Level 3 (Defined): Makes sure that product meets the requirements and intended
use
 Level 4 (Quantitatively Managed): Manages the project's processes and sub-
processes statistically
 Level 5 (Maturity): Identify and deploy new tools and process improvements to
meet needs and business objectives

By Mr. UMESH KUMAR, MCA (GGU) Page | 2


NET/SET/GATE/JRF OTHER EXAM
By Mr. UMESH KUMAR, MCA (GGU) Page | 3
NET/SET/GATE/JRF OTHER EXAM

You might also like