Completion of the product scope is measured against the product:

According to the PMBOK® Guide, a clear distinction is made between Project Scope and Product Scope regarding how completion is measured:

Product Scope: The features and functions that characterize a product, service, or result. Completion of the product scope is measured against the product requirements to ensure that the delivered product has all the specified characteristics and functions.

Project Scope: The work performed to deliver a product, service, or result with the specified features and functions. Completion of the project scope is measured against the project management plan, specifically the scope baseline (which includes the scope statement, WBS, and WBS dictionary).

Validation: During the Validate Scope process, the formalized acceptance of the completed project deliverables is obtained. This involves inspecting the deliverables to ensure they meet the documented requirements and acceptance criteria.

Comparison with other options:

A. Prototypes: These are a tool used in the Collect Requirements process to provide a working model of the expected product. While they help define requirements, they are not the formal metric against which final completion is measured.

C. Analyses: Data analysis is a technique used throughout the project to make decisions or identify trends, but it is not the baseline for scope completion.

D. Benchmarks: Benchmarking involves comparing actual or planned practices to those of comparable organizations to identify best practices or provide a basis for measuring performance. It helps set the standard for requirements but is not the requirements document itself.