Project verification and inspection

Project verification (scope verification / validation) is the process of formally checking that the project deliverables are complete, satisfy the requirements and meet acceptance criteria before they are accepted by the customer or sponsor. In PMBOK this is "Validate scope" (Monitoring and controlling), while verification more broadly confirms that the product was built correctly according to specification ("did we build the product right?").

Process

1. Gather completed deliverables that have passed quality control.
2. Review them with the customer or sponsor against the scope statement, requirements and WBS dictionary.
3. Record accepted and rejected items.
4. Obtain formal written acceptance (sign-off).
5. Raise change requests or defect repairs for rejected items.

Inspection (tool and technique)

Inspection includes activities such as measuring, examining and testing to determine whether work and deliverables meet requirements and acceptance criteria. It is also called reviews, product reviews, audits and walkthroughs.

Deliverable -> Inspect -> Meets criteria?
                  yes -> Acceptance sign-off
                  no  -> Change request / rework

Outputs

Accepted deliverables, change requests, work performance information and project document updates.

Verification vs validation

• Verification: checks conformance to specification (internal, often by team).
• Validation: confirms the product meets the customer's needs (external, by customer).

Example: A new payroll module is demonstrated to finance staff who check calculations against 50 test cases and sign the acceptance form.