The process of scope verification is to confirm that the work being completed matches the details stated in the WBS, project scope management plan and project management plan. The inspections used to determine verification of the requirements will usually consist of reviews, audits and user trials.
The final stage of verification involves obtaining formal acceptance of the delivered product or service by the stakeholder, so confirmation is given that the deliverables correspond to the requirements included within the agreed project scope statement and project charter. For example, during a meal in a restaurant your waiter will normally visit your table and confirm that you are enjoying your food. The reason for this question is to determine whether the food has been prepared and cooked to your satisfaction. If there is no complaint about the meal, the waiter has been able to ensure that payment should be forthcoming because the food has matched the diner's expectations.
If a project has to be terminated early for any reason, the process of scope verification is still required to determine the degree of project success. The verification report should document what was achieved at the point of termination, because this information could establish the start point for possible legal action.
Once the approval of a deliverable is formally declared, documentation should be generated to state acceptance of this fact. (Payment of the restaurant bill is one way to demonstrate customer acceptance.) On occasion, confirmation of acceptance may need to be signed off by both the sponsor and customer before formal compliance is granted. If a deliverable fails its acceptance criteria, a formal document stating non-compliance should be produced instead. The key aspect for any acceptance is to ensure the requirements are met, prior to completing the documentation to state that a deliverable has been achieved. With all the ticks in the right boxes, the project can formally gain sign-off status.
Top of Page