Purpose:

The process of formalizing acceptance of the completed project deliverables. The key benefit of this process is that it brings objectivity to the acceptance process and increases the chance of final product, service, or result acceptance by validating each deliverable.

Objective:

Formal process for accepting  completed project deliverables.

Description:

The verified deliverables obtained from the Control Quality process are reviewed with the customer or sponsor to ensure that they are completed satisfactorily and have received formal acceptance of the deliverables by the customer or sponsor. In this process, the outputs obtained as a result of the Planning processes in the Project Scope Management Knowledge Area, such as the requirements documentation or the scope baseline, as well as the work performance data obtained from the Execution processes in other Knowledge Areas, are the basis for performing the validation and for final acceptance.

The Validate Scope process differs from the Control Quality process in that the former is primarily concerned with the acceptance of the deliverables, while quality control is primarily concerned with the correctness of the deliverables and meeting the quality requirements specified for the deliverables. Control Quality is generally performed before Validate Scope, although the two processes may be performed in parallel.

Inputs:

  • Project Management Plan
  • Requirements Documentation
  • Requirements Traceability Matrix
  • Verified Deliverables
  • Work Performance Data

Outputs:

  • Accepted Deliverables
  • Change Requests
  • Work Performance Information
  • Updated Project Documents

Controls:

  • Inspection
  • Group Decision-Making Techniques

Task Instructions:

<?>

    1. Using the <?>, [the ?] with support from <?> is responsible for …