CMMI Staged Representation (Maturity Levels)

The staged representation for CMMI-DEV introduces maturity levels (1-5):

Maturity Level 2 (ML2)

Requirements Management (RM)
Project Planning (PP)
Project Monitoring and Control (PMC)
Supplier Agreement Management (SAM)
Measurement and Analysis (MA)
Process and Product Quality Assurance (PPQA)
Configuration Management (CM)

Maturity Level 3 (ML3)

Organizational Process Focus (OPF)
Organizational Process Definition (OPD)
Organizational Training (OT)
Integrated Project Management (IPM)
Risk Management (RSKM)
Decision Analysis and Resolution (DAR)
Requirements Development (RD)
Technical Solution (TS)
Product Integration (PI) - how to integrate the system (and dependencies)
Verification (VER) - selected WP meet their specified requirements; build the SW right
Validation (VAL) - build the software right; in the right environment; criteria for validation

Maturity Level 4 (ML4)

Organizational Process Performance (OPP) - establish and maintain a quantitative understanding of the performance of selected processes in the organization’s set of standard processes in support of achieving quality and process performance objectives, and to provide process performance data, baselines, and models to quantitatively manage the organization’s projects
Quantitative Project Management (QPM) - quantitatively manage the project to achieve quality and process performance objectives; metrics infrastructures

Maturity Level 5 (ML5)

Organizational Performance Management (OPM) - manage the org. performance to meet its business obj.

Causal Analysis and Resolution (CAR) - identify causes of problems (more broadly: selected outcomes) and take action to improve performance

CMMI-DEV: PPQA Process Area

PROCESS AND PRODUCT QUALITY ASSURANCE SUPPORT (ML2)
The purpose of Process and Product Quality Assurance (PPQA) is to provide staff and management with objective insight into processes and associated work products.

SG 1 Adherence of the performed process and associated work products to applicable process descriptions, standards, and procedures is objectively evaluated.
         SP 1.1 Objectively evaluate selected performed processes against applicable process descriptions, standards, and procedures.
         SP 1.2 Objectively evaluate selected work products against applicable process descriptions, standards, and procedures.

SG 2 Noncompliance issues are objectively tracked and communicated, and resolution is ensured.
         SP 2.1 Communicate quality issues and ensure the resolution of noncompliance issues with the staff and managers.
         SP 2.2 Establish and maintain records of quality assurance activities.

CMMI-DEV: SAM Process Area

SUPPLIER AGREEMENT MANAGEMENT PROJECT MANAGEMENT (ML2)
The purpose of Supplier Agreement Management (SAM) is to manage the acquisition of products and services from suppliers.

SG 1 Agreements with the suppliers are established and maintained.
         SP 1.1 Determine the type of acquisition for each product or product component to be acquired.
         SP 1.2 Select suppliers based on an evaluation of their ability to meet the specified requirements and established criteria.
         SP 1.3 Establish and maintain supplier agreements.

SG 2 Agreements with suppliers are satisfied by both the project and the supplier.
         SP 2.1 Perform activities with the supplier as specified in the supplier agreement.
         SP 2.2 Ensure that the supplier agreement is satisfied before accepting the acquired product.
         SP 2.3 Ensure the transition of products acquired from the supplier.

CMMI-DEV: RM Process Area

REQUIREMENTS MANAGEMENT PROJECT MANAGEMENT (ML2)
The purpose of Requirements Management (REQM) is to manage requirements of the project’s products and product components and to ensure alignment between those requirements and the project’s plans and work products.

SG 1 Requirements are managed and inconsistencies with plans and work products are identified.
         SP 1.1 Develop an understanding with the requirements providers on the meaning of the requirements.
         SP 1.2 Obtain commitment to requirements from project participants.
         SP 1.3 Manage changes to requirements as they evolve during the project.
         SP 1.4 Maintain bidirectional traceability among requirements and work products.
         SP 1.5 Ensure that project plans and work products remain aligned with the requirements.

CMMI-DEV: PP Process Area

PROJECT PLANNING PROJECT MANAGEMENT (ML2)
The purpose of Project Planning (PP) is to establish and maintain plans that define project activities.

SG 1 Estimates of project planning parameters are established and maintained.
SP 1.1 Establish a top-level work breakdown structure (WBS) to estimate the scope of the project.
SP 1.2 Establish and maintain estimates of work product and task attributes.
SP 1.3 Define project lifecycle phases on which to scope the planning effort.
SP 1.4 Estimate the project’s effort and cost for work products and tasks based on estimation rationale.

SG 2 A project plan is established and maintained as the basis for managing the project.
SP 2.1 Establish and maintain the project’s budget and schedule.
SP 2.2 Identify and analyze project risks.
SP 2.3 Plan for the management of project data (1).
SP 2.4 Plan for resources to perform the project.
SP 2.5 Plan for knowledge and skills needed to perform the project.
SP 2.6 Plan the involvement of identified stakeholders.
SP 2.7 Establish and maintain the overall project plan.

SG 3 Commitments to the project plan are established and maintained.
SP 3.1 Review all plans that affect the project to understand project commitments.
SP 3.2 Adjust the project plan to reconcile available and estimated resources.
SP 3.3 Obtain commitment from relevant stakeholders responsible for performing and supporting plan execution.


Additional information: 
(1) Data are forms of documentation required to support a project in all of its areas (e.g. administration, engineering, config. management, finance, logistics, quality, safety, manufacturing, procurement). Can take any form (printed documents, drawn) and exist in any medium (paper, electronic) and can be deliverable or not. Distribution could also take any form (including electronic distribution). 

CMMI-DEV: PMC Process Area

PROJECT MONITORING AND CONTROL PROJECT MANAGEMENT (ML2)
The purpose of Project Monitoring and Control (PMC) is to provide an understanding of the project’s progress so that appropriate corrective actions can be taken when the project’s performance deviates significantly from the plan.

SG 1 Actual project performance and progress are monitored against the project plan.
         SP 1.1 Monitor actual values of project planning parameters against the project plan.
         SP 1.2 Monitor commitments against those identified in the project plan.
         SP 1.3 Monitor risks against those risks identified in the project plan.
         SP 1.4 Monitor the management of project data against the project plan.
         SP 1.5 Monitor stakeholder involvement against the project plan.
         SP 1.6 Periodically review the project’s progress, performance, and issues.
         SP 1.7 Review the project’s accomplishments and results at selected project milestones.

SG 2 Corrective actions are managed to closure when the project’s performance or results deviate significantly from the plan.
         SP 2.1 Collect and analyze issues and determine corrective actions to address them.
         SP 2.2 Take corrective action on identified issues.
         SP 2.3 Manage corrective actions to closure.

CMMI-DEV: MA Process Area

MEASUREMENT AND ANALYSIS SUPPORT (ML2)
The purpose of Measurement and Analysis (MA) is to develop and sustain a measurement capability used to support management information needs.

SG 1 Measurement objectives and activities are aligned with identified information needs and objectives.
         SP 1.1 Establish and maintain measurement objectives derived from identified information needs and objectives.
         SP 1.2 Specify measures to address measurement objectives.
         SP 1.3 Specify how measurement data are obtained and stored.
         SP 1.4 Specify how measurement data are analyzed and communicated.
SG 2 Measurement results, which address identified information needs and objectives, are provided.
         SP 2.1 Obtain specified measurement data.
         SP 2.2 Analyze and interpret measurement data.
         SP 2.3 Manage and store measurement data, measurement specifications, and analysis results.
         SP 2.4 Communicate results of measurement and analysis activities to all relevant stakeholders.

CMMI-DEV: CM Process Area

CONFIGURATION MANAGEMENT SUPPORT (ML2)
The purpose of Configuration Management (CM) is to establish and maintain the integrity of work products using configuration identification, configuration control, configuration status accounting, and configuration audits.

SG 1 Baselines of identified work products are established.
         SP 1.1 Identify configuration items, components, and related work products to be placed under configuration management.
         SP 1.2 Establish and maintain a configuration management and change management system for controlling work products.
         SP 1.3 Create or release baselines for internal use and for delivery to the customer.

SG 2 Changes to the work products under configuration management are tracked and controlled.
         SP 2.1 Track change requests for configuration items.
         SP 2.2 Control changes to configuration items.

SG 3 Integrity of baselines is established and maintained.
         SP 3.1 Establish and maintain records describing configuration items.
         SP 3.2 Perform configuration audits to maintain the integrity of configuration baselines.