Where are key project deliverables documented?

In the PMBOK® Guide, the Work Breakdown Structure (WBS) is the primary tool for organizing and defining the total scope of the project. It is defined as a " deliverable-oriented hierarchical decomposition of the work to be executed by the project team. "

Why Choice D is correct:

Deliverable-Oriented: Unlike a schedule (which is action-oriented), the WBS focuses entirely on the " nouns " of the project—the actual products, results, or services that must be delivered.

Visualization of Scope: Each level of the WBS provides more detail about the deliverables. The highest levels represent the major project deliverables, which are then decomposed into smaller, more manageable components called work packages.

The Scope Baseline: The WBS, along with the WBS Dictionary and the Project Scope Statement, forms the Scope Baseline. While the Scope Statement describes the deliverables in text, the WBS documents and structures them visually to ensure 100% of the scope is accounted for.

Analysis of other options:

A (Project management plan): This is a master document that contains many subsidiary plans (like the scope management plan, schedule management plan, etc.). While it contains the WBS, it is too broad to be the specific answer for where deliverables are documented.

B (Requirements traceability matrix): The RTM links requirements to the deliverables that satisfy them. It tracks the status and origin of requirements throughout the project life cycle, but it is not the primary document used to structure and define the deliverables themselves.

C (User acceptance criteria): These are the conditions (the " rules " ) that must be met before a deliverable is accepted by the customer. Acceptance criteria are usually found in the Project Scope Statement or the WBS Dictionary, but they describe the quality/standards of a deliverable rather than acting as the documentation of the deliverables themselves.

Key Concept: The Project Management Institute (PMI) teaches the 100% Rule: The WBS must include 100% of the work defined by the project scope and capture all deliverables—internal, external, and interim. By using the WBS (Choice D), the project manager ensures that there is no " scope creep " and that every key deliverable is accounted for and assigned to a specific part of the project hierarchy.