HKSM

Verified deliverables are project outputs that have passed quality checks and meet specified requirements. Evidence such as test results and inspection records shows they are complete and conforming. They are ready to be presented for formal acceptance.

Key Points

• Created by performing quality control activities such as inspections, reviews, and testing.
• Show that deliverables meet documented requirements and acceptance criteria with no unresolved defects.
• Include objective evidence like checklists, test reports, measurements, and sign-offs from qualified reviewers.
• Are inputs to formal acceptance processes; acceptance occurs only after verification is complete.
• May be produced incrementally as components are completed and verified throughout the project.
• Differ from accepted deliverables, which are approved by the customer or authorized sponsor.

Purpose

Provide objective proof that deliverables conform to requirements before seeking customer or sponsor acceptance. This reduces rework, builds confidence, and supports stage-gate and handover decisions.

Who Approves

• Quality assurance or quality control lead for verification sign-off.
• Subject matter experts and engineers responsible for technical checks.
• Project manager or team lead to confirm completeness and readiness for validation.
• Configuration management representative to confirm version and baseline alignment.

How to Prepare

• Confirm requirements and acceptance criteria are clear, testable, and traced to the deliverable.
• Execute inspections, tests, and reviews per the quality management plan and test protocols.
• Record results, measurements, and evidence; log nonconformances and defects.
• Resolve defects, retest, and update records until criteria are fully met.
• Package verification evidence with identifiers: version, configuration item, date, and approvers.
• Store artifacts in the project repository with controlled access and traceability to requirements.

How to Use

• Submit verified deliverables as inputs to validation and customer acceptance activities.
• Support stage-gate reviews, readiness assessments, and release decisions.
• Provide evidence for compliance, audits, and regulatory submissions.
• Feed lessons learned and process improvement with verification data and defect trends.

Gate Checklist Example

• All relevant requirements are traced and marked complete.
• Planned inspections and tests are executed with passed results.
• All defects and nonconformances are closed or formally waived with approval.
• Verification evidence (reports, checklists, logs) is attached and version-controlled.
• Configuration item ID and baseline alignment are confirmed.
• Risk, issue, and change records related to the deliverable are updated.
• Internal verification sign-offs are captured from authorized roles.

Governance Rules

• Use approved templates and test protocols to ensure consistency and auditability.
• Maintain separation of duties: creators do not solely verify their own work where feasible.
• Control versions and maintain traceability from requirements to verification evidence.
• Manage deviations and waivers through the change control process with documented impact.
• Retain verification records per organizational and regulatory retention policies.
• Subject verification artifacts to periodic quality audits for completeness and accuracy.

PMP Example Question

After completing inspections and tests, the team has documented that the product meets all specified criteria. What should the project manager do next?

1. Record accepted deliverables and start closing the project.
2. Submit the verified deliverables to stakeholders for formal acceptance.
3. Update the risk register and archive the verification reports.
4. Raise a change request to update the scope baseline.

Correct Answer: B — Submit the verified deliverables to stakeholders for formal acceptance.

Explanation: Verified deliverables are confirmed by quality control and then presented for acceptance. Acceptance is a separate step performed by authorized stakeholders.