Capability Maturity Model (CMM) goals - quick reference

The goals to achieve a CMM level is summarized for quick reference:

CMM Level 2 (Repeatable)

Projects in Level-2 organizations have installed basic software management controls. Realistic project commitments are based on the results observed on projects and on the requirements of the current project. The software managers for a project track software costs, schedules, and functionality; problems in meeting commitments are identified when they arise. Software requirements and the work products developed to satisfy them are baselined, and their integrity is controlled.

Key Process Areas (KPA)

• Requirement Management
• Software Project Planning
• Software Project Tracking and Oversight
• Software Subcontract Management
• Software Quality Assurance
• Software Configuration Management

Goal 1: System requirements that are allocate to software are controlled to establish a baseline for software engineering and management use

Goal 2: Software plans, products, and activities are kept consistent with the system requirements allocated to software

Goal 3: Software estimates are documented for use in planning and tracking the software project

Goal 4: Software project activities and commitments are planned and documented

Goal 5: Affected groups and individuals agree to their commitments related to the software project

Goal 6: Actual results and performances are tracked against the software plans

Goal 7: Corrective actions are taken and managed to closure when actual results and performance deviate significantly from the software plans

Goal 8: Changes to software commitments are agreed to by the affected group and individuals

Goal 9: The prime contractor selects qualified software subcontractors

Goal 10: The prime contractor and the software subcontractor agree to their commitments to each other

Goal 11: The prime contractor and the software subcontractor maintain ongoing communications

Goal 12: The prime contractor tracks the software subcontractor’s actual results and performance against its commitments

Goal 13: Software quality assurance activities are planned

Goal 14: Adherence of software products and activities to the applicable standards, procedures, and requirements is verified objectively

Goal 15: Affected groups and individuals are informed of software quality assurance activities and results

Goal 16: Noncompliance issues that cannot be resolved within the software project are addressed by senior management

Goal 17: Software configuration management activities are planned

Goal 18: Selected software work products are identified, controlled, and available

Goal 19: Changes to identified software work products are controlled

Goal 20: Affected groups and individual are informed of the status and content of software baselines