verify scope

7/30/2019 Verify Scope

1/5

Verify scope is the process of receiving formal acceptance of the completed project

deliverables

Verifying scope includes

Reviewing deliverables with the customer or sponsor to ensure that they are

completed satisfactorily and obtaining formal acceptance of the deliverables by the

customer or sponsor.

Here the project charter identifies who can sign off the project is complete.

The project scope statement identifies criteria for completion.

Scope verification differs from perform quality control process

Scope verification is primarily concerned with acceptance of deliverables, while

quality control is primarily concerned with the correctness of the deliverables and

meeting the quality requirements specified for the deliverables.

Quality control is generally performed before scope verification, but these two

processes can be performed in parallel.

Figure 5-11: Verify Scope: Inputs, Tools & Techniques, and Outputs


2/5

Figure 2-1 shows the flow of completed deliverables through various processes.

You can see how the deliverables created from the Direct and Manage Project

Execution process are validated in the Perform Quality Control process. Those

validated deliverables are ready for inspection in the Verify Scope process. After the

deliverables are accepted, they are ready for close-out.


3/5

5.4.1 Verify Scope: Inputs

1 Project Management Plan

The project management plan described in Section 4.2.3.1 contains the scope

baseline. Components of the scope baseline include:

Project scope statement. The project scope statement includes the

product scope description, includes the project deliverables, and

defines the product user acceptance criteria.


4/5

WBS. The WBS defines each deliverable and the decomposition of the

deliverables into work packages.

WBS dictionary. The WBS dictionary has a detailed description of work

and technical documentation for each WBS element.

2 Requirements Documentation

The requirements documentation lists all the project, product, technical, and other

types of requirements that must be present for the project and product, along with

their acceptance criteria. Requirements documentation is described in Section

5.1.3.1.

3 Requirements Traceability Matrix

The requirements traceability matrix links requirements to their origin and tracks

them throughout the project life cycle, which is described in Section 5.1.3.3.

4 Validated Deliverables

Validated deliverables have been completed and checked for correctness by the

Perform Quality Control process.

5.4.2 Verify Scope: Tools and Techniques

1 Inspection

Inspection includes activities such as measuring, examining, and verifying to

determine whether work and deliverables meet requirements and product

acceptance criteria. Inspections are sometimes called reviews, product reviews,

audits, and walkthroughs. In some application areas, these different terms have

narrow and specific meanings.

5.4.3 Verify Scope: Outputs

1 Accepted Deliverables

Deliverables that meet the acceptance criteria are formally signed off and approved

by the customer or sponsor. Formal documentation received from the customer or

sponsor acknowledging formal stakeholder acceptance of the projects deliverables

is forwarded to the Close Project or Phase process (4.6).


5/5

2 Change Requests

Those completed deliverables that have not been formally accepted are

documented, along with the reasons for non-acceptance. Those deliverables may

require a change request for defect repair. The change requests are processed for

review and disposition through the Perform Integrated Change Control process (see

Section 4.5).

3 Project Document Updates

Project documents that may be updated as a result of the Verify Scope process

include any documents that define the product or report status on product

completion.

verify scope

Documents