The case study below offers an excellent perspective on how projects are often initiated under less than ideal circumstances—which often lays the ground work for project failure.Companies that provi

To be sure to set the context, open with a description/definition of a Verification and Validation plan. Be sure to tie your narrative to the specific project. Include a high level description of the project objectives and scope. Identify customers, other key stakeholders and key deliverables.

Map out (draw a flowchart or swim-lane diagram) that shows how two types of assurances can be obtained: Verification and Validation. The plan must include both the processes/steps AND the role(s)/person(s) performing each step. To ensure understanding, a written narrative that explains the plan and each step must also be generated.

Verification: The evaluation of whether or not a product, service or result complies with a regulation, requirement, specification or imposed condition. The ‘correctness’ of deliverables. (Refer to the Charter & Case Study).

Validation: The assurance that a product, service or result meets the needs of the customer and other identified stakeholders (Refer to the Charter & Case Study).

See page 163-166 PMBOK 6e. Consider the inputs (including project objectives and success criteria) and the processes/steps needed for the customer(s) to make acceptance decisions. Be sure to consider customers from both companies (both internal and external customers). Consider the process required for each phase of the project.