CMMI for Development
GG3
Institutionalize 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.
The purpose of this generic practice is to collect process related
experiences, including information and artifacts derived from planning
and performing the process. Examples of process related experiences
include work products, measures, measurement results, lessons learned,
and process improvement suggestions. The information and artifacts are
collected so that they can be included in the organizational process
assets and made available to those who are (or who will be) planning and
performing the same or similar processes. The information and artifacts
are stored in the organization’s measurement repository and the
organization’s process asset library.
|
| Examples of relevant information include the effort expended
for the various activities, defects injected or removed in a
particular activity, and lessons learned. |
|
Refer to the Integrated Work Management
process area for more information about contributing to organizational
process assets.
Refer to the Organizational Process Definition
process area for more information about establishing organizational
process assets.
Subpractices
1. Store process and product
measures in the organization’s measurement repository.
The process
and product measures are primarily those measures that are defined in
the common set of measures for the organization’s set of standard
processes.
2. Submit documentation for inclusion in the
organization’s process asset library.
3. Document lessons learned
from the process for inclusion in the organization’s process asset
library.
4. Propose improvements to the organizational process
assets.
|
| CAR Elaboration |
Examples of process related experiences include the
following:
• Action proposals
• Number of action proposals
that are open and for how long
• Action proposal status
reports |
|
CM Elaboration |
Examples of process related experiences include the
following:
• Trends in the status of configuration items
•
Configuration audit results
• Change request aging reports |
|
DAR Elaboration |
Examples of process related experiences include the
following:
• Number of alternatives considered
•
Evaluation results
• Recommended solutions to address
significant issues |
|
IPM Elaboration |
Examples of
process related experiences include the following:
•
Project’s defined process
• Number of tailoring options
exercised by the project to create its defined process
•
Interface coordination issue trends (i.e., number identified,
number closed)
• Number of times the process asset library is
accessed for assets related to project planning by project
members
• Records of expenses related to holding face-to-face
meetings versus holding meetings using collaborative equipment
such as teleconferencing and videoconferencing
• Project
shared vision
• Team charters |
|
MA Elaboration |
Examples of process related
experiences include the following:
• Data currency status
• Results of data integrity tests
• Data analysis reports |
|
OPD Elaboration |
Examples of process related experiences include the
following:
• Submission of lessons learned to the
organization’s process asset library
• Submission of
measurement data to the organization’s measurement repository
• Status of the change requests submitted to modify the
organization’s standard process
• Record of non-standard
tailoring requests |
|
OPF Elaboration |
Examples of work process related experiences include the
following:
• Criteria used to prioritize candidate process
improvements
• Appraisal findings that address strengths and
weaknesses of the organization’s processes
• Status of
improvement activities against the schedule
• Records of
tailoring the organization’s set of standard processes and
implementing them on identified work activities |
|
OPM Elaboration |
Examples of process related experiences include the
following:
• Lessons learned captured from analysis of
process performance data compared to business objectives
•
Documented measures of the costs and benefits resulting from
implementing and deploying improvements
• Report of a
comparison of similar development processes to identify the
potential for improving efficiency |
|
OPP Elaboration |
Examples of work process related experiences include the
following:
• Process performance baselines
• Percentage of
measurement data that is rejected because of inconsistencies
with the process performance measurement definitions |
|
OT Elaboration |
Examples of process related experiences include the
following:
• Results of training effectiveness surveys
•
Training program performance assessment results
• Course
evaluations
• Training requirements from an advisory group |
|
PI Elaboration |
Examples of process related
experiences include the following:
• Records of the receipt
of product components, exception reports, confirmation of
configuration status, and results of readiness checking
•
Percentage of total development effort spent in product
integration (actual to date plus estimate to complete)
•
Defects found in the product and test environment during product
integration
• Problem reports resulting from product
integration |
|
PMC Elaboration |
Examples of process related
experiences include the following:
• Records of significant
deviations
• Criteria for what constitutes a deviation
•
Corrective action results |
|
PP Elaboration |
Examples of process related
experiences include the following:
• Project data library
structure
• Project attribute estimates
• Risk impacts and
probability of occurrence |
|
PPQA Elaboration |
Examples of process related experiences include the
following:
• Evaluation logs
• Quality trends
•
Noncompliance reports
• Status reports of corrective actions
• Cost of quality reports for the work |
|
QPM Elaboration |
Examples of process related experiences include the
following:
• Records of quantitative management data from the
project, including results from the periodic review of the
process performance of the subprocesses selected for management
against established interim objectives of the project
•
Suggested improvements to process performance models |
|
RD Elaboration |
Examples of process related
experiences include the following:
• List of the requirements
for a product that are found to be ambiguous
• Number of
requirements introduced at each phase of the project lifecycle
• Lessons learned from the requirements allocation process |
|
REQM Elaboration |
Examples of process related experiences include the
following:
• Requirements traceability matrix
• Number of
unfunded requirements changes after baselining
• Lessons
learned in resolving ambiguous requirements |
|
RSKM Elaboration |
Examples of process related experiences include the
following:
• Risk parameters
• Risk categories
• Risk
status reports |
|
SAM Elaboration |
Examples of process related experiences include the
following:
• Results of supplier reviews
• Trade studies
used to select suppliers
• Revision history of supplier
agreements
• Supplier performance reports |
|
TS Elaboration |
Examples of process related experiences include the
following:
• Results of the make, buy, or reuse analysis
•
Design defect density
• Results of applying new methods and
tools |
|
VAL Elaboration |
Examples of process related experiences include the
following:
• Product component prototype
• Percentage of
time the validation environment is available
• Number of
product defects found through validation per development phase
• Validation analysis report |
|
VER Elaboration |
Examples of process related experiences include the
following:
• Peer review records that include conduct time
and average preparation time
• Number of product defects
found through verification per development phase
•
Verification and analysis report |
|
