Professional Documents
Culture Documents
FOR
DEVELOPMENT VERSION 1.3
What is Process?
How do you define process?
INSTITUTIONALIZED
Defined, documented,
and continuously
AD HOC improved
Improvised by
practitioners and their
management
People develop their potential more fully and are more effective
within the organization.
Appraisal Appraisal
Methods Methods
Shared
PA
Appraisal
Team
Organizational Processes
Organization Projects
Lessons Learned/Improvements
Introduction to
CMMI-DEV, V1.3 CMMI, V1.3
Instructor
Training*
Understanding
CMMI Level 2 CMMI Level 3 CMMI High
for for
Maturity
Practitioners* Practitioners* Practices
COSTS BENEFITS
• Investments • Cost
Process
• Expenses Capability and • Schedule
IN Organizational OUT • Productivity
Maturity
• Quality
• Customer
Satisfaction
ROI
Return on
Investment
and Cost
Benefits
CMM-based improvements
Predictability – internal on-time delivery improved by 15%
Less Rework – first pass yield improved by 10%
Product Quality – reduction in error cases in the factory by one
order of magnitude
From Critical success factors for improvement in a large embedded systems organisation.
Wolfgang Stolz, Robert Bosch GmbH Gasoline Systems GSEC/ ESP and Hans-Jü rgen Kugler, Q-
Labs Software Engineering, ESEPG 2003.)
Note 1: Chapter 6 is in the Addison Wesley book. It does not appear in the technical report
form of the model.
Product Integration PI
Project Monitoring and Control PMC
Project Planning PP
Process and Product Quality Assurance PPQA
Quantitative Project Management QPM
Requirements Development RD
Requirements Management REQM
Risk Management RSKM
Supplier Agreement Management SAM
Technical Solution TS
Validation VAL
Verification VER
Integrated Project The purpose of IPM is to establish and manage the project
Management (IPM) and the involvement of relevant stakeholders according to
an integrated and defined process that is tailored from the
organization’s set of standard processes.
Process
Area (PA)
Specific Generic
Expected Practices Practices
(SP) (GP)
Purpose Statement
Introductory Notes
Related Process Areas
Specific Goal and Practice Summary
Specific Practices by Goal
Specific Goals and Specific Practices
Generic Practices by Goal In “Generic Goals and
Generic Practices”
Generic Goals and Generic Practices section in the model.
Process
Area (PA)
Specific Generic
Expected Practices Practices
(SP) (GP)
DESCRIPTION
Describes the purpose of the process area
EXAMPLE
Project Planning example
Purpose
The purpose of Project Planning (PP) is to establish and maintain plans
that define project activities.
DESCRIPTION
This section describes the major concepts covered in the
process area.
EXAMPLE
Project Planning example
Planning includes estimating the attributes of work products and
tasks, determining the resources needed, negotiating
commitments, producing a schedule, and identifying and
analyzing project risks.
DESCRIPTION
This section lists references to related process areas and
reflects the high-level relationships among the process areas.
EXAMPLE
Project Planning example
Refer to the Risk Management process area for more information
about identifying and analyzing risks and mitigating risks.
DESCRIPTION
The titles of the specific goals and specific practices for that
process area are summarized at the beginning of each process
area.
EXAMPLE
Project Planning example
SG 1 Establish Estimates
SP 1.1 Estimate the Scope of the Project
SP 1.2 Establish Estimates of Work Product and Task Attributes
SP 1.3 Define Project Lifecycle Phases
SP 1.4 Estimate Effort and Cost
Process
Area (PA)
Specific Generic
Expected Practices Practices
(SP) (GP)
DESCRIPTION
A specific goal is a required model component that describes
the unique characteristics that must be present to satisfy the
process area.
EXAMPLE
Project Planning example
SG 1: Estimates of project planning parameters are established and
maintained.
NUMBERING
Specific goals are numbered starting with the prefix SG (e.g., SG 1). The
number is only there to uniquely identify the goal.
DESCRIPTION
Specific practices are expected model components that are
considered important in achieving the associated specific goal.
EXAMPLE
Project Planning example
SP 1.4: Estimate the project’s effort and cost for work products
and tasks based on estimation rationale.
NUMBERING
Specific practices are of the form SP x.y where
x is the same number as the goal to which the specific practice maps.
y is the sequence number of the specific practice under the specific goal.
DESCRIPTION
Example work products are informative model components that
provide sample outputs from a specific practice.
EXAMPLE
For example, project cost estimates might be an example work
product for the Project Planning specific practice SP 1.4,
“Estimate the project’s effort and cost for work products and
tasks based on estimation rationale.”
DESCRIPTION
EXAMPLE
The following is an example of a subpractice from the “Identify
and analyze project risks” specific practice (SP 2.2) in the Project
Planning process area:
3. Review and obtain agreement with relevant stakeholders on
the completeness and correctness of documented risks.
Process
Area (PA)
Specific Generic
Expected Practices Practices
(SP) (GP)
DESCRIPTION
Generic goals are required model components that describe
characteristics that must be present to institutionalize
processes that implement a process area.
Achievement of a generic goal in a process area signifies
improved control in planning and implementing the processes
associated with that process area.
Generic goals are called generic because the same goal
statement applies to multiple process areas.
EXAMPLE
Generic goal example
The process is institutionalized as a defined process.
NUMBERING
Generic goals are numbered starting with the prefix GG (e.g., GG 2).
The number corresponds to the capability level of the GG.
DESCRIPTION
EXAMPLE
Generic practice example
GP 2.5: Train the people performing or supporting the process as
needed.
NUMBERING
Generic practices are of the form GP x.y where
x corresponds to the number of the generic goal.
y corresponds to the sequence number of the generic practice.
DESCRIPTION
Generic practice elaborations are informative model components
that appear after a generic practice to provide guidance on how
the generic practice could be applied uniquely to a process area.
EXAMPLE
Project Planning process area example
GP 2.8: Monitor and Control the Process
Examples of measures and work products used in monitoring
and controlling include the following:
- Number of revisions to the plan
- Cost, schedule, and effort variance per plan revision
- Schedule for development and maintenance of program
plans
DESCRIPTION
An example is a component comprising text and often a list of
items, usually in a box, that can accompany nearly any other
component and provides one or more examples to clarify a
concept or described activity.
EXAMPLE
Project Planning SP 1.2 example
Examples of attributes to estimate include the following:
• Number of functions
• Function points
• Source lines of code
• Number of pages
DESCRIPTION
A reference is a pointer to additional or more detailed
information in related process areas and can accompany
nearly any other model component. A reference is an
informative model component.
EXAMPLE
Project Planning SP 2.2 example
Refer to the Risk Management process area for more information
about identifying potential problems before they occur so that risk
handling activities can be planned and invoked as needed across
the life of the product or project to mitigate adverse impacts on
achieving objectives.
DESCRIPTION
A note is text that can accompany nearly any other model
component. It may provide detail, background, or rationale. A
note is an informative model component.
EXAMPLE
The example below shows a note that accompanies the specific
practice 1.3 in the Project Planning process area.
Project Planning SP 1.3 example
The determination of a project’s lifecycle phases provides for
planned periods of evaluation and decision making. . . .
Three
Categories
1 Required
2 Expected
3 Informative
Specific goals and generic goals are the required components in CMMI
models.
Process
Area (PA)
Specific Generic
Expected Practices Practices
(SP) (GP)
DESCRIPTION
The glossary defines the basic terms used in CMMI models.
It was designed to document the meaning of words and terms
that should have the widest use and understanding by users of
CMMI products.
Definitions of terms were selected based on recognized sources
that have a widespread readership (e.g., ISO, IEEE).
EXAMPLE
Glossary term example
Establish and maintain . . . Create, document, use, and revise work products as necessary to ensure they remain useful.
MODEL REPRESENTATIONS
DESCRIPTION
Staged
ML5
Continuous ML4
Process Area
ML3
Capability
ML2
ML 1
. . .for an established
set of process areas across an
organization
PA PA PA
. . .for a single process area
or a set of process areas
Each generic goal provides a foundation for the next. Therefore, the
following conclusions can be made:
GG 1 A performed process
The generic practices for managed processes are the same for
all process areas.
GP
2.1 Establish an Organizational Policy
Establish and maintain an organizational policy for planning
and performing the process.
GP
2.2
Plan the Process
Establish and maintain the plan for performing the process.
Provide Resources
GP
2.3 Provide adequate resources for performing the process,
developing the work products, and providing the services of the
process.
GP Assign Responsibility
2.4 Assign responsibility and authority for performing the process,
developing the work products, and providing the services of the
process.
Train People
GP
2.5 Train the people performing or supporting the process as
needed.
GP
3.1 Establish a Defined Process
Establish and maintain the description of a defined process
GP
3.2
Collect Process Related Experiences
Collect process related experiences derived from planning
and performing the process to support the future use and
improvement of the organization’s processes and process
assets.