CMMI Staged – Maturity Level 3
1
Lecture # 16
1
Following slide to be inserted
The Maturity Levels
2
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
controlled and
reactive
3
Defined
Managed
Performed
Maturity Level
• Maturity Level 3 differs from Level 2 in
that now an organizational way of doing
business has been developed. What that
means is that the best practices and lessons
learned from the projects have bubbled up
to the organizational level to create an
organizational identity
4
Maturity Level
• There are common, shared approaches for
performing daily tasks on each project. For
example, estimating the size of a project
may be done using the Delphi Technique
(basically subject matter experts discussing
bestcase and worstcase estimates), a
standard metric may have been
institutionalized (such as using function
points instead of lines of code), and a
5
standard tool may be in use
Maturity Level
• This organizational way of doing business
is documented in the Organization’s Set of
Standard Processes (OSSP)
• However, should a project need to tailor
this OSSP to more adequately fit its needs,
then that tailoring request is bought to a
decisionmaking body (usually the
Engineering Process Group [EPG]), and if
appropriate, the request is granted
6
Maturity Level
• An example may be a legacy system that
calculates size by lines of code instead of
by function point. Rather than reengineer
the millions of lines of code in the system in
order to use a tool to count function points,
and rather than do it manually, the project is
simply allowed to continue calculating size
by lines of code. The Delphi Technique is
still used, but lines of code is the
7
measurement
Maturity Level
• To perform at Level 3, an organization must
have satisfied all of the goals for all of the
process areas (PAs) in both Level 2 and
Level 3
• Sometimes exceptions may be made.
Caution should be exercised however
8
Maturity Level
• Entire process areas are generally not
allowed to be tailored out of consideration.
Practices may be tailored out if replaced by
sufficient alternative practices. Remember:
the more tailoring done, the less likely an
organization is to achieve improvement,
and the less likely the organization is to
achieve a maturity level through an
appraisal
9
Attributes of a Process suggested
by CMMI
10
Attributes of a Process 1
• Purpose—Purpose of the process.
• Inputs—Work products, plans, approval
memoranda (usually nouns).
• Entry criteria—What must be triggered
before this process can start? (Usually the
exit criteria of the previous step or process.
Usually stated as a verb.)
11
Attributes of a Process 2
• Activities—Tasks that must be performed.
These tasks are usually later broken down
into the detailed procedures for how to
perform the tasks
• Roles—Who does what? (Usually by
position.)
• Measures—What measures does this
process produce?
12
Attributes of a Process 3
• Verification steps—What reviews are
performed to determine that this process is
followed and is producing the correct
results? (Usually management and quality
assurance reviews, but sometimes can
include customer, peer, and project team
reviews.)
13
Attributes of a Process 4
• Outputs—Work products, plans, approved
products (can be the completed inputs)
• Exit criteria—How do we know when it is
time to stop this process? (Usually
expressed in verbs, and usually becomes the
entry criteria for the next process step or
next process.)
14
Managed Process
• Another distinction is made concerning
processes. A managed process is a process
that tackles project management efforts, is
planned and executed according to a policy,
is monitored, and reviewed to ensure
adherence to its process description
• This is the type of process expected at
Maturity Level 2
15
Defined Process
• A defined process builds upon a managed
process by creating an organizational
process that is then tailored to fit the needs
of a particular project and involves
gathering information related to
improvement efforts undertaken by the
organization in order to improve both the
organizationlevel process and the project
level process
16
Following two slides to be
inserted
11 Process Areas for Level 3
(Defined)
17
Process Areas for Maturity Level 3 1
•
•
•
•
•
•
Requirements Development
Technical Solution
Product Integration
Verification
Validation
Organizational Process Focus
18
Process Areas for Maturity Level 3 2
• Organizational Process Definition (with
IPPD)
• Organizational Training
• Integrated Project Management (with IPPD)
• Risk Management
• Decision Analysis and Resolution
19
Maturity Level
• To satisfy the goals for Level 3, the goals
for Level 2 must be satisfied as well
• This mandate holds true for both the
specific goals (listed in each process area
below) and the generic goals
• There are two generic goals for levels 2 and
3
20
Generic Goals for Levels 2 & 3
• GG2 Institutionalize a Managed Process
• GG3 Institutionalize a Defined Process
21
GG2 Institutionalize a Managed
Process – Generic Practices
•
•
•
•
•
•
•
•
•
•
GP 2.1 Establish an Organizational Policy
GP 2.2 Plan the Process
GP 2.3 Provide Resources
GP 2.4 Assign Responsibility
GP 2.5 Train People
GP 2.6 Manage Configurations
GP 2.7 Identify and Involve Relevant Stakeholders
GP 2.8 Monitor and Control the Process
GP 2.9 Objectively Evaluate Adherence
GP 2.10 Review Status with Higher Level Management
22
Following slide to be inserted
Generic Practices for Institutionalize
a Defined Process
23
GG3 Institutionalize a Defined
Process – Generic Practices
• GP 3.1 Establish a Defined Process
• GP 3.2 Collect Improvement Information
24
Requirements Development
PA 1
25