Scope Verification: How to – Part I

November 7, 2009

There is whole set of documents you need to look at to be able to verify the scope of deliverables. The common thread that ties these documents together is that they help define the deliverables and the project context in the form of the project management plan.

What do you need for Scope Verification

The complete set of documents that you need for verifying scope at the end of a project, or the end of a phase, of the project include the following. The project management plan is a top of the list item. That is the master document that defines the complete framework. Some specific components of the project management plan are essential inputs to this verification process. These are the Scope baseline document, the WBS and the WBS dictionary.

The scope baseline describes the reference point of the scope that the project started with and as it evolved through the project lifetime and up to that point in time. WBS document defines the activities that were to be carried out and down to the work packages level. The WBS dictionary defines the work activities and the packages. WBS and the WBS dictionary together are able to specify the activities to be carried out to make defined deliverables available. So if one is to verify the scope one needs these definitions to be readily available.

Requirements document lists all the project, product, technical and other requirements of the project. Corresponding acceptance criteria are also available from this document. Another related document is the traceability matrix. This links down each requirement to the original business needs and any changes that would have happened during the project life cycle.

The documents mentioned up to now defines what was needed/expected in terms of deliverables. One last document defines what has actually happened. This is the validated deliverables document. It tells you about the deliverables as delivered and validated (checked for correctness) by the QA/QC processes.


Having looked at the two sides of what was needed and what was delivered the stakeholders and/or customers accept the deliverables and ask for changes in the ones not delivered right.

Popularity: 1% [?]

Tags: ,

Leave a Reply

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