Validate Scope Process

The validate scope process is used to accept project deliverables. Its major advantage is to provide objectivity to the acceptance process, as well as to improve the final product, service, or result by validating the deliverables.

When you have already determined which deliveries will happen as part of the project, your customer needs to decide whether or not the deliveries fit within the scope of the project. Additional supervision will also be carried out on deliveries. When it is determined that prepared deliveries do not satisfy some of the requirements, the organization carrying out the project may need to reconstruct unsuitable sections.

The scope approval process, although related to the closing process and quality control processes, may not always be properly understood. For a delivery to pass control measures, it has to go through tests, audits, and assessments and be cleared by various inspectors in both processes. However, it must not be forgotten that while quality control is an internal process of the project, scope approval is a customer concern. In addition, the quality control process also seeks to identify and eliminate the causes of deficiencies.

Inputs to Validate Scope Process

  • Scope Management PlanA scope management plan will set the framework for accepting and verifying the final project deliverables.
  • Requirements Management Plan: In this project management process, a requirements management plan outlines how project requirements are validated.
  • Scope Baseline: Scope baselines are created at the start of a project, and at its completion, they are used to determine if additional adjustments need to be made.
  • Lessons Learned Register: Previous lessons learned in the current project or earlier phases or stages in the project can be applied or re-implemented in the latter phases or stages of the project in an attempt to validate the project and deliverables with more efficiency and effectiveness.
  • Quality Reports: Quality reports include information about quality issues associated with the project, as well as recommendations for improvement. They also detail quality problems found through control quality process. This information is thoroughly checked before we are able to accept the product.
  • Requirements Documentation: This process outlines all the requirements for the project, the product, and any related items, as well as their acceptance criteria. Considering these factors, it is the project manager's job to meet the stakeholder's requirements. The important thing about requirements is that clear documentation can identify and resolve any variations from the initially agreed-upon scope of the project or product.
  • Requirements Traceability MatrixThe traceability matrix ties requirements to their source and stages them throughout the life cycle of the project. Similarly, it matches the performance of the project to the Project Management plan, comparing each objective to a requirement to ensure the deliverables satisfy the client's needs.
  • Verified deliveries
  • Work performance data

Tools and Techniques of Validate Scope Process

  • Inspection: An inspection examines the work product for conformity to the standards, and includes measurements at any level.
  • Group Decision-Making Techniques: It involves taking a group of options, consulting with a group of peers and finalizing an informed decision, which you then follow through on.

Outputs of Validate Scope Process

  • Accepted Deliveries: Deliverables are handed over to customers once they are submitted and accepted as they match the customer's requests. 
  • Change Request: The customer may have new requirements anytime in validation process to request a change to a part of the project, he submits a change request. Upon approval by the change control board, a change request can be implemented by the project team.
  • Work Performance Information
See also: