CMMI for Acquisition Blog – Special Series: 08th Part: This blog series on the cmmiconsultantblog.com is a systematic and structured coverage of CMMI Process Areas starting from Maturity Level 2 to Maturity Level 3: using CMMI–ACQ, Version 1.3, as the Reference CMMI Model: As CMMI Consultant, during CMMI Consulting assignment if you are asked about the steps, inputs and outputs of Requirements Management (REQM) Process Area, what would be your response:

CMMI FAQ 0

28th July, 2017

For the above-mentioned question, CMMI Consultants may take inputs from the following:

Requirements Management (REQM) process area helps in managing the project requirements related to the product and product components. It also ensures that project work is in sync with the project requirements.

Activities

Requirements Management involves the following activities:

• Gathering Initial Requirements
• Taking Commitment to Requirements from Different Stakeholders
• Handling Requirements Changes
• Keeping track of Bidirectional Traceability of Requirements
• Managing Sync Between Requirements and Project Work/Tasks

Inputs

Following are some examples of input to the Requirements Management:

• SOW, Contract, Agreement
• Surveys
• Legacy System
• Stakeholders Details

Outputs

Outputs created during the implementation of the Requirements Management activities are as under:

• Set of approved requirements
• Results of surveys, analysis
• Impact Assessments
• Requirements Changes Log
• Requirements Change Impact Analysis
• Requirements traceability matrix, Requirements Tracked through Tools
• Review Report of Project Work With Respect to Requirements
• Corrective Actions Taken to Align Project Work to Requirements

The above is not an exhaustive coverage of the Requirements Management (REQM) CMMI Process Area but is substantive enough to create a good foundation of the Requirements Management process in an organization.

Source: CMMI for Acquisition Version 1.3