A Deliverable: Unique and Verifiable Product, Result, or Capability

PMBOK v8 Definition

A deliverable is any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project. Deliverables also include ancillary results such as project management reports and documentation. These deliverables may be described at a summary level or in great detail, and may be tangible or intangible.

Why It Matters for the Exam

This definition appears frequently in PMI exam questions testing your understanding of what constitutes a project deliverable versus other project artifacts. Questions often present scenarios where you must identify which items qualify as deliverables, distinguish deliverables from requirements or acceptance criteria, or determine the correct point in the project lifecycle when deliverables are formally accepted.

Key Points to Remember (for the exam)

• Core Definition: A deliverable is any unique AND verifiable product, result, or capability to perform a service
• Scope of Deliverables: Includes both primary outputs (product, service, result) AND ancillary results (project management reports, documentation)
• Verification Requirement: Deliverables must be verifiable against established acceptance criteria
• Accepted Deliverables: These are products, services, and capabilities that are validated by an appointed individual or group against established criteria; when criteria are met, deliverables are approved and accepted
• Decomposition: Work breakdown structure (WBS) decomposes deliverables into verifiable components; lower-level WBS components must be necessary and sufficient for completion of corresponding higher-level deliverables
• Quality Dimensions: Deliverables must be evaluated for resilience (cope with unforeseen failures), satisfaction (elicit valuable feedback), uniformity (parity across similar outputs), efficiency (greatest output with least input), and sustainability
• Project Purpose: Projects are undertaken to fulfill objectives by producing deliverables

Typical PMI Exam Example

A project manager is developing the WBS for a software implementation project. The project charter lists "user training" as a key output. Which of the following represents a deliverable in this context?

Answer: The training materials, training sessions conducted, and the training completion report are all deliverables because they are unique and verifiable products, results, or capabilities required to complete the project.

PMI Exam Traps

• Trap: Confusing deliverables with requirements documentation

• Reality: Requirements documentation elaborates characteristics of the product, service, or result; deliverables are the actual products, results, or capabilities produced

• Trap: Thinking only tangible products are deliverables

• Reality: Deliverables may be tangible (physical product) OR intangible (service, capability, report)

• Trap: Assuming all project outputs are deliverables

• Reality: Only outputs that are unique, verifiable, AND required to complete a process, phase, or project qualify as deliverables

• Trap: Confusing accepted deliverables with verified deliverables

• Reality: Accepted deliverables are validated by an appointed individual against established criteria; this is a formal approval step that occurs after verification

Important PMI Connections

Quick Review Questions

1. A project team completes a software module. The module functions correctly, but the customer has not yet formally reviewed it against the acceptance criteria. Is this software module considered a deliverable? Why or why not?

2. During project execution, the team produces weekly status reports and a risk register. Are these project management reports considered deliverables according to PMBOK v8?

3. A project's WBS includes "user documentation" as a work package. The team decomposes this into "installation guide," "user manual," and "quick reference card." What principle of deliverable decomposition does this demonstrate?

4. A deliverable passes all functional tests but users report poor usability. According to PMBOK v8, which quality dimension is being evaluated in this scenario?

5. When are deliverables formally considered "accepted deliverables" in the project management process?

PMBOK v8 Reference

Section 3 – Project Management Principles (Embed Quality Into Processes and Deliverables) Section 4 – Inputs and Outputs (Accepted Deliverables) Deliverables definition appears in multiple sections including the definition of deliverables and their role in project management