CMMI Introduction

CMMI Introduction
CMMI V1.2 Induction – Sep 2007
May 2007
Protection notice / Copyright notice
Version 2.1
Contents
History
Structure of CMMISM
Staged Representation
Continuous Representation

Page 2 Sep-07 P&Q For Internal Use Only
History of CMMI

Looking Back….
US Department of Defense set up the Software Engineering

Institute (SEI) in the 1984
An R & D organization only; custodian on behalf of the
software community for the Capability Maturity Models
Charter is to be the leader in advancing the state of the
practice of software engineering to improve the quality of
systems that depend on software
Is not a “Certification” body

History of CMMs
CMM for Software Systems Engineering

V1.1 (1993) INCOS SECAM
CMM V1.1 (1995)
(1996)
EIA 731 SECM Integrated Product

Software CMM
(1998) Development CMM
V2, draft C (1997)
(1997)
V1.02 (2001)
V1.1 (2002)
CMMI for Development
CMMI for Acquisition V1.2 (2006) CMMI for Services
V1.2 (2007) V1.2 (2007)

CMMI
•Process Improvement Maturity Model for development of products

and services
•Best Practices that address development and maintenance
activities
•Integrates bodies of knowledge essential for development and
maintenance like software, systems & design, and acquisition
•CMMI can be considered as a collection of “practices” that are
necessary to achieve high maturity and capability
•These have been structured and organized into Process Areas
•CMMI Dev V1.2: Continuation and update of CMMI V1.1

Structure of CMMI
Development

The CMMI Dev Document
Composed of Three Parts
Part 1 (About CMMI for development)

 Introduction
 Process Area components
 Tying it all together
 Relationship among Process Areas
 Using CMMI Models
Part 2 (Generic Goals, Generic Practices and Process Areas)

 23 sections
 1 section for generic practices
 22 sections each representing one of the PAs of CMMI Dev

The CMMI Dev Document
Part 3 (Appendices and Glossary)

 Appendix A - References
 Appendix B - Acronyms
 Appendix C – CMMI for Dev Project participants
 Glossary
There are two representations of the Model:

 Staged
 Continuous
The CMMI Development document is 573 pages

Source: CMU/SEI-2006-TR-008
Can be downloaded in .pdf or .doc format from SEI website


Maturity Levels
Improvement
institutionalized Continuously Optimizing
improving (5)
proces
s
Quantitatively Quantitative
Predictable Managed
process control
(4)
Defined Technical practices are

Standard,
consistent (3) integrated with management
process practices and institutionalized
Managed Project Management practices

Disciplined
process (2) are institutionalized
Initial Process in informal and adhoc

(1)
© Software Engineering Institute
“.. is a well-defined evolutionary plateau on the path to becoming a mature
organization”
A higher maturity level includes all lower maturity levels Protection notice / Copyright notice
Process Capability and the Prediction of
Performance
© Software Engineering Institute

Three results of
Probability
Target N-z
5 Performance continuously
increasing maturity - improves in Level 5

organizations
Difference between Time /$/...
Probability
targeted results and
Target N-y
Based on quantitative
4
understanding of process
actual results and product, performance

continues to improve in
Level 4 organizations
decreases across Time/$/...
Probability
projects
Target N-x
3 With well-defined processes,
performance improves in
Level 3 organizations
Variability of actual
results around Probability
Time/$/...
Target N+a
targeted results 2 Plans based on past
performance are more
realistic in Level 2
decreases organizations
Targeted results Time/$/...

Probability
improve 1 Target N Schedule and cost targets

are typically overrun by
Level 1 organizations.
Time/$/...

Staged Approach
Proven sequence of typical areas to focus on for

improvement
Permits comparison across organizations -

assessment results can be summarized into a single
rating

Model Structure – Staged V1.2

Process Area - Concept
A Process Area (PA) is a cluster of related practices

A set of practices need to be performed to satisfy goals of
a process area
In the staged representation, a process area resides at a
specific maturity level

The Process Areas
5 Organizational
Causal Analysis & Resolution 5
Innovation & Deployment
4 Organizational 4
Quantitative Project Management
Process Performance
3
Validation
3
Organizational Training
Verification Risk Management
Organizational Process Definition
Product Integration
Integrated Project Management Decision Analysis & Resolution
+ IPPD
Technical Solution + IPPD
Organizational Process Focus
Requirements Development
2 Supplier Agreement Management Configuration Management 2

Requirements Management
Project Monitoring and Control Process & Product QA
Project Planning Measurement & Analysis
Engineering Project Management Process Management Support

Goal - Concept
A Goal is a high-level outcome to be achieved by effective implementation of
practices
There are two kinds of goals in each PA

Specific goals
Generic goals
The concept of Goals is:

 all “institutionalization” related practices have been combined into “Generic
Goals”
If “institutionalization” has taken place, “Generic Goals” are satisfied
There are one to three “Specific Goals” per Process Area

There is one “Generic Goal” (related to institutionalization) per Process Area
Practice - Concept
A Practice is an action to be performed in order to achieve the goals of

a Process Area
CMMISM contains 2 types of practices:

Specific practices
these differ across Process Areas
Generic practices
these are common across all Process Areas

Generic Practices
Generic Practices support the Generic Goal of each PA

For a Generic Goal, the Generic Practices are the same

Discussion
Discussion on Process Area
Participants to be taken through a Process Area like Configuration

Management or Coding
Discussion on:
- Some Specific Practices for the PA
- Example of direct and indirect evidences
- Implementation level concepts
- Generic Practices for the PA – e.g. policy, resources, training,
stakeholders, levels of control, corrective actions, adherence to
process, etc
- Institutionalization of the PA


Page 22
Requirements Management
Validation
Verification
Product Integration
Technical Solution
Engineering
Requirements Development
Sep-07
Supplier Agreement Management
Project Monitoring and Control
P&Q
Project Planning
Risk Management
Integrated Project Management + IPPD
Project Management
Continuous View of PAs
Quantitative Project Management
Organizational Training
Organizational Process Definition + IPPD
Organizational Process Focus
Organizational Process Performance
Organizational Innovation & Deployment
Process Management
Configuration Management
Process & Product QA
Measurement & Analysis
Decision Analysis & Resolution
Support
Causal Analysis & Resolution

For Internal Use Only
Capability Levels
 A capability level is a well-defined evolutionary

plateau describing the organization’s capability
relative to a process area.
 There are six capability levels.
 For capability levels 1-5, there is an associated
generic goal.
 Each level is a layer in the foundation for continuous
process improvement.
 Thus, capability levels are cumulative, i.e., a higher
capability level includes the attributes of the lower
levels.
The Capability Levels
5 Optimizing
4 Quantitatively Managed
3 Defined
2 Managed
1 Performed
0 Incomplete

Capability Levels
5-Optimizing
4-Quantitatively
Managed
3-Defined
2-Managed
1-Performed
0-Incomplete
CL/ PA RM RD TS PI VER VAL

Continuous Approach
Allows selection of process areas to focus on for

process improvement - based on those areas that
impact organization’s business objectives and risks
Does not allow easy comparison across

organizations - however capability levels of individual
PAs can be compared

Quiz
Q1 Level 5 Process Area focuses on:
b) Process Improvement
c) Measurement and analysis
d) Planning and Tracking
Q2 CMMI requires that the processes are:

 Defined in the QMS
 Defined and practiced in a project
 Defined and practiced in most of the projects
Q3 Organizational Innovation and deployment fulfils one of the requirements of

which Maturity Level:
 Level 2
 Level 5
 Level 4

Recap…
History
Structure of CMMISM

Any Questions?

Thank You


CMMI Introduction

Uploaded by

Copyright:

Available Formats

You might also like

CMMI Introduction

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CMMI Introduction

Uploaded by

Copyright:

Available Formats

CMMI Introduction

CMMI V1.2 Induction – Sep 2007

Protection notice / Copyright notice

Protection notice / Copyright notice

US Department of Defense set up the Software Engineering

Protection notice / Copyright notice

CMM for Software Systems Engineering

EIA 731 SECM Integrated Product

Protection notice / Copyright notice

•Process Improvement Maturity Model for development of products

Protection notice / Copyright notice

Protection notice / Copyright notice

Composed of Three Parts

Part 1 (About CMMI for development)

Part 2 (Generic Goals, Generic Practices and Process Areas)

Protection notice / Copyright notice

Part 3 (Appendices and Glossary)

There are two representations of the Model:

The CMMI Development document is 573 pages

Protection notice / Copyright notice

Protection notice / Copyright notice

Defined Technical practices are

Managed Project Management practices

Initial Process in informal and adhoc

© Software Engineering Institute

increasing maturity - improves in Level 5

Difference between Time /$/...

actual results and product, performance

decreases across Time/$/...

Targeted results Time/$/...

improve 1 Target N Schedule and cost targets

Protection notice / Copyright notice

Proven sequence of typical areas to focus on for

Permits comparison across organizations -

Protection notice / Copyright notice

Protection notice / Copyright notice

A Process Area (PA) is a cluster of related practices

Protection notice / Copyright notice

2 Supplier Agreement Management Configuration Management 2

Engineering Project Management Process Management Support

There are two kinds of goals in each PA

The concept of Goals is:

There are one to three “Specific Goals” per Process Area

A Practice is an action to be performed in order to achieve the goals of

CMMISM contains 2 types of practices:

Protection notice / Copyright notice

Generic Practices support the Generic Goal of each PA

Protection notice / Copyright notice

Discussion on Process Area

Participants to be taken through a Process Area like Configuration

Protection notice / Copyright notice

Protection notice / Copyright notice

Quantitative Project Management

Causal Analysis & Resolution

 A capability level is a well-defined evolutionary

Protection notice / Copyright notice

CL/ PA RM RD TS PI VER VAL

Allows selection of process areas to focus on for