CMMI and Acquisition
This topic contains information about how CMMI can be used for acquisition management.
Contents:
- Can CMMI be used for acquisition management?
- What is the CMMI Acquisition Module (CMMI-AM)?
- What is CMMI for Acquisition (CMMI-ACQ)?
- What is the Software Acquisition Capability Maturity Model (SA-CMM)?
- What is the difference between the SA-CMM, CMMI-ACQ, and the CMMI-AM?
- What problem was the SA-CMM, CMMI-ACQ, and CMMI-AM designed to solve?
- How does the SA-CMM and CMMI-ACQ differ from CMMI-DEV?
- Does the CMMI-AM replace the SA-CMM?
- Is the CMMI-AM a subset of CMMI-DEV or CMMI-ACQ? Does this constitute tailoring of the model for acquisition organizations?
- Can I get a maturity or capability level rating from the CMMI-AM?
- Does the CMMI-AM cover contractor software development processes?
- What is the impact of the CMMI-AM to a developer or supplier?
- What is the status of the SA-CMM model?
- How long will the SEI continue to support the SA-CMM?
Can CMMI be used for acquisition management?
CMMI for Development covers the acquisition discipline as it relates to product development and maintenance, which includes the use of commercial off-the-shelf (COTS) products and outsourcing.
The CMMI Acquisition Module (CMMI-AM) builds on relevant best practices extracted from the CMMI Framework to define effective and efficient practices for government acquisition organizations. This is a non-appraisable element of the CMMI Product Suite.
CMMI for Acquisition (CMMI-ACQ), a CMMI model designed for acquisition organizations, is planned for release in 2007. An initial draft of the model is now available.
The Software Acquisition Capability Maturity Model (SA-CMM) is a capability maturity model for organizations that acquire solutions such as hardware, software, services, and systems. It is used to appraise an organization's process maturity and help improve its acquisition processes.
return to top
What is the CMMI Acquisition Module (CMMI-AM)?
The CMMI Acquisition Module (CMMI-AM) builds on relevant best practices extracted from the CMMI Framework to define effective and efficient practices for government acquisition organizations. These best practices focus on the activities performed by acquisition professionals in the acquisition program office. They also address internal program office activities that support the monitoring and control of development contractors and suppliers. They provide a foundation for acquisition process discipline and rigor that enables product and service development to be repeatedly executed.
The CMMI-AM documents acquisition practices that should be performed by government acquisition projects acquiring systems or services. These practices, however, can also be used by non-government organizations to improve their acquisition or outsourcing practices.
The information in the CMMI-AM can also be used by acquisition organizations that manage several related acquisition projects (e.g., product centers, acquisition commands, Program Executive Officers, Service/Component acquisition executives) to establish an acquisition process improvement program, ensuring the success of projects in their purview.
return to topWhat is CMMI for Acquisition (CMMI-ACQ)?
CMMI for Acquisition (CMMI-ACQ), a CMMI model designed for acquisition organizations, is planned to be released in 2007, but an initial draft of the model is now available.
Following the success of CMMI models for development organizations, the need was identified for a CMMI model addressing the government's acquisition environment and industry's increasing use of outsourcing of software intensive systems and services. The initial draft CMMI-ACQ provides process improvement guidance for organizations engaged in acquisition. The practices focus on activities required for supplier sourcing; initiating and awarding supplier agreements; and managing the acquisition of products and services through a set of standard measures, acceptance criteria, and supplier deliverables. The initial draft CMMI-ACQ integrates bodies of knowledge that are essential for an acquirer.
This draft is based on the CMMI version 1.2 architecture and framework which incorporates the concept of constellations. Constellations are groupings of components to support a specific model application such as Development (DEV) or Acquisition (ACQ). This initial draft also is based on the CMMI-AM and SA-CMM.
return to topWhat is the Software Acquisition Capability Maturity Model (SA-CMM)?
The Software Acquisition Capability Maturity Model (SA-CMM) is a capability maturity model for organizations that acquire solutions such as hardware, software, services, and systems. It is used to appraise an organization's process maturity and help improve its acquisition processes. The SA-CMM provides acquisition organizations with guidance on how to gain control of their acquisition processes and helps them to do the following:
- benchmark the maturity level of the organization's acquisition process through appraisals
- set senior management goals for process improvement
- enable prediction of potential acquisition process performance
What is the difference between the SA-CMM, CMMI-ACQ, and the CMMI-AM?
CMMI models and CMMI modules are different types of products.
- CMMI models are part of the CMMI Product Suite, are the official documents that contain CMMI effective practices, and can be used with a Standard CMMI Appraisal Method for Process Improvement (SCAMPI) Class A appraisal to achieve and determine a maturity level or capability level rating.
- CMMI modules are documents that clarify applications of CMMI models for certain application domains such as acquisition. CMMI modules typically are selected excerpts from a CMMI model with additions and amplifications pertinent to a particular anticipated use. Modules provide guidance for beginning process improvement; however, an organization cannot obtain a maturity level rating from their use of modules.
- For process improvement, process models such as the SA-CMM, CMMI-ACQ, or CMMI-DEV provide the following:
- a place to start
- the benefit of a community's prior experiences
- a common language and a shared vision
- a framework for prioritizing actions
- a way to define what improvement means for your organization
- accepted appraisal methodologies
- related training
Many of the acquisition practices and amplifications in the CMMI Acquisition Module (CMMI-AM) are drawn and summarized from existing sources of best practices, including SA-CMM and CMMI as well as additional coverage areas defined by experienced acquisition professionals. The CMMI-AM, as well as the SA-CMM, may be used to help acquisition organizations examine the effectiveness of their processes, establish priorities for their improvement, and implement needed improvement. The CMMI-AM, through its interpretation and explanations, can help acquisition organizations understand the relationship between the SA-CMM and the CMMI, and how to transition easily from SA-CMM-based process improvement to a CMMI-based acquisition process improvement.
return to topWhat problem was the SA-CMM, CMMI-ACQ, and CMMI-AM designed to solve?
The lack of quality in management practices for acquisition of solutions, especially for software-intensive solutions, is the major problem these models and modules were designed to solve. The problem is characterized as continued failure of large acquisition and associated development efforts to meet cost, schedule, and/or performance goals. An immature acquisition organization can doom a project to failure as surely as an immature development organization.
return to topHow does the SA-CMM and CMMI-ACQ differ from CMMI-DEV?
The SA-CMM and CMMI-ACQ focus on the organization (the buyer or acquirer) that acquires solutions such as software-intensive systems or services. In contrast, CMMI-DEV, as typically interpreted, helps a systems/software development organization (the supplier or developer) mature and increase predictability in the development of software-intensive systems. Sufficient coverage of acquisition is provided so that organizations obtaining critical portions of their products from other organizations can address the critical risks to their success.
return to topDoes the CMMI-AM replace the SA-CMM?
No. The CMMI-AM is not an organizational process improvement maturity model like CMMI or the SA-CMM. The CMMI-AM's focus is at the acquisition program office personnel level.
return to topIs the CMMI-AM a subset of CMMI-DEV or CMMI-ACQ? Does this constitute tailoring of the model for acquisition organizations?
The CMMI-AM is not strictly a subset of a CMMI model since it does not include details such as subpractices and other informative material. It was derived from various sources of best practices including CMMI, SA-CMM, and the experience of acquisition and development communities. Amplifications are provided where useful in applying the guidance to the acquisition role.
return to topCan I get a maturity or capability level rating from the CMMI-AM?
No. To receive a maturity or capability level rating, an acquisition organization would need to be appraised against a CMMI model, not the CMMI-AM, using a Class A appraisal method such as SCAMPI A. However, the CMMI-AM can be used to perform a less formal gap analysis on an acquisition project that would result in the identification of strengths, weaknesses, risks, and improvement opportunities to help the acquisition project establish an acquisition process improvement program.
return to topDoes the CMMI-AM cover contractor software development processes?
No. Even though some CMMI process areas are applicable to activities performed by both the acquisition program office personnel and the developer (e.g., requirements development), the process areas and amplifications in the CMMI-AM are focused on defining and improving acquisition processes to be used by the acquisition program office personnel to accomplish the acquirer's activities across the lifecycle of the system or service development. This focus includes coverage of activities performed only by acquisition organization program office personnel (e.g., solicitation preparation) as well as contractor monitoring and insight activities performed by the acquisition organization.
return to topWhat is the impact of the CMMI-AM to a developer or supplier?
Use of the CMMI-AM in an acquisition program will provide a common language and framework for process improvement across the program office/contractor team. It will align the acquisition program office personnel and the supplier/developer personnel in terms of a common language and process, and by encouraging the recognition of the related roles and responsibilities of each.
return to topWhat is the status of the SA-CMM model?
Version 1.03 represents the second refinement of the original SA-CMM. The model now includes a separate KPA to address user requirements and has expanded the measurement and analysis sections of each KPA. The associated product suite for the SA-CMM, including the introductory course and appraisal related items have been updated to reflect the new version of the model.
The SA-CMM will continue to be recognized and used until CMMI for Acquisition (CMMI-ACQ) is released. CMMI for Acquisition, a CMMI model designed for acquisition organizations, is planned to be released in 2007, but an initial draft of the model is now available.
return to topHow long will the SEI continue to support the SA-CMM?
While the SEI feels that the CMMI-AM module captures most of the best practices for acquisition use, it does not provide the full aspects of a process improvement model, with training and appraisal capability. The CMMI Steering Group understood this deficiency and supported the development of the CMMI acquisition "constellation" to remedy this shortfall. Once the CMMI-ACQ has been released and initial appraisals have been performed to confirm its capabilities, the SA-CMM will be retired by the SEI.
return to topIf you have a question that is not answered within this FAQ, check the CMMI FAQ Main Page or send email to an SEI person at cmmi-comments@sei.cmu.edu. You will receive a response within 48 hours.