5.4 Verify Scope Process

The Verify Scope Process obtains the customer and stakeholders' acceptance of the completed deliverables.

During scope verification, the deliverables are compared to the scope statement to make sure all the requirements have been met.

Scope verification process is also performed by the project team throughout the project as deliverables are ready but before the stakeholders or customers verifies the deliverables.

Since the project scope includes the requirements and acceptance criteria, it serves as the checkpoint.

The deliverables are verified through inspection, which in this context means any tools that measure, examine, or verify that the work and deliverables meet the requirements and acceptance criteria.

Though inspection may be more narrowly defined in some industries and application areas, its context here should be broadly interpreted.

Deliverables that don't meet these criteria result in change requests to address the deficiencies.

Scope verification process ultimately involves the stakeholders and customers, who are the ones who must agree that the deliverables meet their needs as established in the scope.

But this process is also performed beforehand by the project team, usually after quality control.

Scope verification process always occurs at least once for each project, and even if the project is terminated before completion the deliverables are compared to the scope’s requirements based on the work completed when the project was canceled.

scope verification as a "customer review" process

Scope verification process: PROCESS  ⇒ PURPOSE ⇒ PRIMARY OUTPUT

It's probably best to think of scope verification as a "customer review" process because that helps eliminate some of the confusion with two other processes concerned with verification and user acceptance.​

Perform Quality Control validates the deliverables against quality requirements while scope verification is concerned with the overall acceptance and verification of the project scope statement.

The Close Project or Phase process also includes the formal acceptance of the deliverables by the customer (through the Administrative Closure Procedure), but its focus is on the formalities required by the customer or the performing organization, such as a signed acceptance document.

Verify Scope process

Verify Scope Process Decomposition

Verify Scope Process: Inputs

  • Project management plan
    The project management plan details how the project will be executed, managed, and controlled.
    For scope verification, the project management plan contains the project scope statement, work breakdown structure, and the WBS dictionary.
    These are the scope baseline, and the validated deliverables will be compared to these documents for adherence to requirements.
  • Requirements documentation
    The product scope and project objectives are broken down into requirements and described in a collection of requirements documentation that's applicable to the project and requirement type
    Requirements can be documented and described in a number of different levels (executive, summary, and detailed) and in a variety of methods (textually or visually).
  • Requirements traceability matrix
    All requirements are logged onto a requirements traceability matrix.
    The main purpose of the matrix is to enable every requirement to be logged and attached to a project's objective or to another requirement in a hierarchical manner.
  • Validated deliverables
    These are deliverables that have met all the quality requirements through Perform Quality Control.

Verify Scope Process: Tools and Techniques

  • Inspection
    Inspection is any activities that make sure the work and deliverables meet the requirements and the product acceptance criteria. The inspection usually involves measuring, examining, or other verification activities.

Verify Scope Process: Outputs

  • Accepted deliverables
    Deliverables that have met project requirements and the product acceptance criteria are known as accepted deliverables.
  • Change requests
    Deliverables that do not meet the project’s requirements and the product acceptance criteria will result in change requests for correction and defect repair. These are treated as any other change request and processed through Perform Integrated Change Control.
  • Project document updates
    Project status information, change logs, and other project documents may need to be updated through scope verification activities.

Related Articles

Project Communications Management Knowledge Area |... Project Communications Management includes the activities that generate, collect, distribute, formulate, store, and retrieve project communications. ...
4.1 Develop Project Charter Process The project charter formally authorizes the project and establishes a partnership between the performing organization and the project’s stakeholders a...
11.3 Perform Qualitative Risk Analysis Process Perform Qualitative Risk Analysis follows risk identification, and it prioritizes risks based on their likelihood of occurring and their potential imp...
4.6 Close Project or Phase Process The Close Project or Phase process is the formal completion of the project, or in multi-phase projects the closure of a phase.It includes making sure ...

Leave a Reply

Your email address will not be published. Required fields are marked *