CMMI for Acquisition Blog – Special Series: 11th 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 Acquisition Validation (AVAL) Process Area, what would be your response:

CMMI FAQ 0

24th November, 2017

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

Acquisition Validation (AVAL) process area helps in confirming that the concerned product or service works in the user environment (production) as it was supposed to work.

Activities

Acquisition Validation involves the following activities:

• Preparation/planning for validation
• Selection of products for validation
• Setting up the validation environment
• Deciding the validation procedures and criteria
• Conducting Validation
• Analyzing Validation Results

Inputs

Following are some examples of input to the Acquisition Validation:

• Product/Services details
• Scope or Requirements
• Detailed Requirements document
• Service/Product or Product Component availability for Validation
• Relevant Validation plans after review
• Validation Environment

Outputs

Outputs created during the implementation of the Acquisition Validation activities are as under:

• Validation results / validation case sheet with actual validation results
• Issue Reports
• Validation Incident Report
• Integrated and Validated System
• Updated Traceability Matrix
• Acceptance Validation / Acceptance Validation Report

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

Source: CMMI for Acquisition Version 1.3