CMMI Staged – Maturity Level 4
Lecture # 18A
1
1
Staged Representation
• The staged representation is the approach used in
the Software CMM. It is an approach that uses
predefined sets of process areas to define an
improvement path for an organization. This
improvement path is described by a model
component called a maturity level
• A maturity level is a welldefined evolutionary
plateau toward achieving improved organizational
processes
2
2
Following slide to be inserted
The Maturity Levels
3
3
The Maturity Levels
Optimizing
5 Focus on process
improvement
Quantitatively
Managed
4 Process measured
and controlled
3
Process characterized for
the organization and is
proactive
2
Process characterized for
projects and is often reactive
1 Process unpredictable, poorly
Defined
Managed
Performed
controlled and
reactive
4
4
Level 4
• Level 4 is all about numbers
• The projects are managed “by the
numbers.” Organizational decisions are
made “by the numbers”
• Processes, services, product quality are all
measured “by the numbers”
• At Level 4, the organization has achieved
all of the goals of Levels 2 and 3
5
5
Level 4
• Processes, although qualitatively stable and
predictable at Level 3, can be proved to be
quantitatively stable and predictable at
Level 4
6
6
Level 4
• Level 4 analyzes the data collected,
determines special causes of variation from
the norm, and supports quantitative
management and control
• This is done to make your processes
predictable
7
7
Level 4
• To get “good” data, an organization usually
has to collect data for several years, or at
least through several projects and several
life cycles of the projects. And when you
first begin collecting data, they will not be
consistent data
8
8
Level 4
• Measurement data are collected beginning with
Level 2 in the staged representation, and in most
organizations, actually begin being collected at
Level 1. The problem is the data are not clean and
consistent because the processes used on the
projects (where the data are collected and used)
are not yet stable and consistent. Data in and of
themselves are not magical. They simply reflect
what is going on in the projects
• The point is, an organization cannot go to Level 4
9
9
overnight
Level 4
• What problems do we see in organizations
when they decide to move from Level 3 to
Level 4?
• At Level 3, measures are collected and
preliminary thresholds are established,
usually relating to size and effort. If the
thresholds are exceeded, some sort of
corrective action is undertaken
10
10
Level 4
• At Level 4, the control limits are based on
years of historical data and trends analyses
done on those data. More data are collected,
and, therefore, more limits are established,
monitored, and refined as necessary
11
11
Level 4
• At Level 3, the data may be somewhat
inconsistent and “dirty.” Although in a
perfect world we would like to see “clean”
data at Level 3, the focus on Level 3 is on
organizational process, not necessarily on
stabilized, normalized, statistically accurate
data—which is exactly what Level 4
expects
12
12
Level 4
• One problem that we see in some
organizations that have barely met the
criteria for Level 3 is that the processes are
not always followed consistently across the
organization
13
13
Following slide to be inserted
Process Areas of Level 4
(Quantitatively Managed)
14
14
Process Areas at Level 4
• Organizational Process Performance
• Quantitative Project Management
15
15
• At level 4, there are no additions to the list
of generic goals at Level 4 from Level 3.
What makes this maturity level different are
the two process areas
• GG2 Institutionalize a Managed Process
• GG3 Institutionalize a Defined Process
16
16
• To satisfy the goals for Level 4, the goals
for Levels 2 and 3 must be satisfied as well.
This mandate holds true for both the
specific goals and the generic goals
17
17
Organizational Process
Performance
PA 1
18
18
Organizational Process Performance
• The purpose of Organizational Process
Performance (OPP) is to establish and
maintain a quantitative understanding of the
performance of the Organization’s Set of
Standard Processes (OSSP) in support of
quality and process–performance objectives,
and to provide the process–performance data,
baselines, and models to quantitatively manage
the organization’s projects
19
19
Specific Goal for Level 4
• SG1 Establish Performance Baselines and
Models
20
20
SG1 Establish Performance
Baselines and Models – Specific
Practices
• SP 1.1 Select Processes
• SP 1.2 Establish Process–performance
Measures
• SP 1.3 Establish Quality and Process–
performance Objectives
• SP 1.4 Establish Process–performance
Baselines
• SP 1.5 Establish Process–performance Models
21
21
Process Area
• This process area includes measurements
for both process and product. Additionally,
service has also been specifically presented
as an area appropriate for measurement.
This process area combines these measures
to determine both the quality of the process
and the product in quantitative terms
22
22
Process Performance Baselines
• Process performance baselines and process
performance models are included in goals
for this process area
• A process performance baseline (PPB)
documents the historical results achieved by
following a process. A PPB is used as a
benchmark for comparing actual process
performance against expected process
performance
23
23
Process Performance Model
• A process performance model (PPM)
describes the relationships among attributes
(for example, defects) of a process and its
work products
• A PPM is used to estimate or predict a
critical value that cannot be measured until
later in the project’s life—for example,
predicting the number of delivered defects
throughout the life cycle
24
24
• At Level 2, measures are collected, stored
in a database per project, bubble up to an
organizational database in Level 3, are
reviewed for consistency and accuracy at
Level 3, and then, at Level 4, have
statisticallybased controls applied to them
• The OSSP must be understood from a
statistical point of view
25
25