||Trinity Management Consultants Limited
|34 Fountains Place|
|The CMMI Technical Referencefirstname.lastname@example.org|
Measurement and Analysis
|Specific Goal and Practice Summary
SG 1 Align Measurement and Analysis Activities
SP 1.1 Establish Measurement Objectives
SP 1.2 Specify Measures
SP 1.3 Specify Data Collection and Storage Procedures
SP 1.4 Specify Analysis Procedures
SG 2 Provide Measurement Results
SP 2.1 Obtain Measurement Data
SP 2.2 Analyze Measurement Data
SP 2.3 Store Data and Results
SP 2.4 Communicate Results
|A Support Process Area at Maturity Level 2
The purpose of Measurement and Analysis (MA) is to develop and sustain a measurement capability used to support management information needs.
The Measurement and Analysis process area involves the following activities:
• Specifying objectives of measurement and analysis so that they are aligned with identified information needs and project, organizational, or business objectives
• Specifying measures, analysis techniques, and mechanisms for data collection, data storage, reporting, and feedback
• Implementing the analysis techniques and mechanisms for data collection, data reporting, and feedback
• Providing objective results that can be used in making informed decisions and taking appropriate corrective action
The integration of measurement and analysis activities into the processes of the project supports the following:
• Objective planning and estimating
• Tracking actual progress and performance against established plans and objectives
• Identifying and resolving process related issues
• Providing a basis for incorporating measurement into additional processes in the future
The staff required to implement a measurement capability may or may not be employed in a separate organization-wide program. Measurement capability may be integrated into individual projects or other organizational functions (e.g., quality assurance).
The initial focus for measurement activities is at the project level. However, a measurement capability can prove useful for addressing organization- and enterprise-wide information needs. To support this capability, measurement activities should support information needs at multiple levels, including the business, organizational unit, and project to minimize re-work as the organization matures.
Projects can store project specific data and results in a project specific repository, but when data are to be used widely or are to be analyzed in support of determining data trends or benchmarks, data may reside in the organization’s measurement repository.
Measurement and analysis of product components provided by suppliers is essential for effective management of the quality and costs of the project. It is possible, with careful management of supplier agreements, to provide insight into data that support supplier performance analysis.
Measurement objectives are derived from information needs that come from project, organizational, or business objectives. In this process area, when the term “objectives” is used without the “measurement” qualifier, it indicates either project, organizational, or business objectives.
Related Process Areas
Refer to the Requirements Development process area for more information about eliciting, analyzing, and establishing customer, product, and product component requirements.
Refer to the Configuration Management process area for more information about establishing and maintaining the integrity of work products using configuration identification, configuration control, configuration status accounting, and configuration audits.
Refer to the Organizational Process Definition process area for more information about establishing the organization’s measurement repository.
Refer to the Project Monitoring and Control process area for more information about monitoring project planning parameters.
Refer to the Project Planning process area for more information about establishing estimates.
Refer to the Quantitative Project Management process area for more information about quantitatively managing the project.
Refer to the Requirements Management process area for more information about maintaining bidirectional traceability of requirements.