The WBS Dictionary contains all the details of the Work Breakdown Structure which are necessary to successfully complete the project. Most importantly it contains a definition of each Work Package which can be thought of as a mini scope statement. Resources on the project will look at the WBS dictionary to determine the scope of the Work Package they’ve been assigned, so it’s important to be clear when writing the definition. Most WBS dictionaries contain more information than we show in our sample. These things usually include Level of Effort, Cost Control Numbers, Resource Assignments, Responsibility Assignments – just to name a few.
Scope verification discusses how the deliverables will be verified against the original scope and how the deliverables from the project will be formally accepted. The deliverables for the project should be formally accepted and signed off on by the customer throughout the lifecycle of the project and not held back as a single deliverable at the end of the project.
Below is an example of explaining how a deliverable will be verified against the original requirements. You can use some of the same ideas but your approach will probably by different and specific to your project and should be expressed in your own words.
As this project progresses the Project Manager will verify interim project deliverables against the original scope as defined in the scope statement, WBS and WBS Dictionary. Once the Project Manager verifies that the scope meets the requirements defined in the project plan, the Project Manager and Sponsor will meet for formal acceptance of the deliverable. During this meeting the Project Manager will present the deliverable to the Project Sponsor for formal acceptance. The Project Sponsor will accept the deliverable by signing a project deliverable acceptance document. This will ensure that project work remains within the scope of the project on a consistent basis throughout the life of the project.