Skip to content
PMPCAPM

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Share:

Know it well enough for the exam? Questions on Deliverables are scenario-based, not definitional.

Practice it free

Explanation

Deliverables are the unit that scope is built from. The scope statement lists them with their acceptance criteria, the WBS decomposes them into work packages, schedule and cost estimates roll up from those work packages, and the quality and acceptance processes act on them. If a deliverable is defined vaguely, everything downstream inherits the vagueness, which is why unclear deliverables sit behind so many exam scenarios about scope creep and disputes at sign-off.

A deliverable is an output, not the goal. The PMBOK Guide 7th edition puts the emphasis on outcomes and value: deliverables exist to enable a change, and that change is what produces benefits for the organization. A project manager is responsible for both: delivering what was agreed, and noticing when a deliverable that meets its specification will no longer achieve the business objective. In that case the right move is to raise it with the sponsor or product owner, not to deliver to spec in silence.

In adaptive approaches deliverables arrive incrementally. Each iteration produces a working increment that stakeholders can inspect, and acceptance happens story by story. That reduces the risk of a large deliverable being rejected at the end of the project, which is the classic failure mode of a purely plan-driven approach.

Deliverables in plain language

A deliverable is something the project must produce that someone can check. “Improve customer experience” is not a deliverable; “a redesigned checkout page that passes the agreed usability test” is. The two words in PMI's definition that matter are unique (it is made for this project, not routine operations) and verifiable (there is an objective way to say it is done).

Deliverables come in three forms, and the exam likes to test that a deliverable need not be a physical thing:

  • Product: a building, a software release, a manual.
  • Result: a research finding, an audit report, a completed data migration.
  • Capability: a trained support team able to handle the new product, a working process.

They can be external (handed to the customer or end user) or internal (needed to run the project, such as the project management plan, a design specification or test reports). Both count, and both appear in the WBS, which is decomposed by deliverable rather than by activity.

How a deliverable moves through a predictive project

In a plan-driven project, each deliverable passes through three states. The vocabulary is precise, and exam answers depend on it.

Direct and Manage Project Workteam builds the workdeliverablesControl Qualityis it correct? (internal)verified deliverablesValidate Scopeis it accepted? (customer/sponsor)accepted deliverablesClose Project or Phasehand over and closeNot accepted →change requestsOutput: final product, service or result transition
The deliverable data flow used in the PMBOK Guide 6th edition. Quality is checked internally before the customer is asked to accept.
StateProduced byWho checksQuestion answered
DeliverablesDirect and Manage Project Work—Has the work been done?
Verified deliverablesControl QualityProject team / quality functionIs it correct and does it meet the quality requirements?
Accepted deliverablesValidate ScopeCustomer or sponsorIs this what we asked for, against the acceptance criteria?
Final product transitionClose Project or PhaseSponsor / operationsHas ownership been handed over?

Acceptance is formal and usually signed. It can happen deliverable by deliverable throughout the project, not only at the end. Deliverables that fail validation are not quietly fixed; the gap is recorded and goes through change requests for defect repair.

And in an agile project

The deliverable is the working increment. Each item carries acceptance criteria (the specific conditions for that story) and must meet the team's definition of done (the quality checklist for every item). The product owner accepts completed items, and stakeholders inspect the increment at the sprint review. The roles map loosely to predictive terms: meeting the definition of done is like verification, product owner acceptance is like validation.

Worked example: a website redesign

A retailer's website redesign project lists its deliverables in the scope statement. Here are six of them with their type and acceptance criteria.

DeliverableFormInternal / externalAcceptance criteriaAccepted by
Responsive website on productionProductExternalAll 40 template pages render correctly on the agreed browser list; checkout loads in under 3 s on a 4G test profileMarketing director (sponsor)
Migrated product contentResultExternal1,200 product pages migrated; random sample of 100 shows zero broken images or pricesE-commerce manager
Trained content editorsCapabilityExternalEach of 8 editors publishes a page unaided after trainingHead of content
Accessibility audit reportResultExternalIndependent audit against WCAG 2.1 AA with no open critical issuesSponsor and legal
Project management planProduct (document)InternalApproved baselines for scope, schedule and costSponsor
Test summary reportResultInternalAll severity-1 defects closed; open issues loggedProject manager / QA lead

Two things to notice. First, every criterion is something a third party could check; that is what makes each deliverable verifiable. Second, the “trained editors” deliverable is a capability, and it is the one most often forgotten in real projects and most often used as a distractor on the exam.

Suppose the sponsor reviews the live site and rejects it because checkout takes 5 seconds. The site passed internal testing (it was a verified deliverable) but it is not an accepted one. The project manager documents the rejection, and the fix enters change control as a defect repair. Adding an unrequested feature to sweeten acceptance would be gold plating, which PMI treats as poor practice.

Common exam traps

  • Validate Scope before Control Quality.

    Quality comes first. Control Quality produces verified deliverables, and only those go to Validate Scope for acceptance. They can overlap in time, but the order for any single deliverable is verify, then validate.

  • Treating Validate Scope as a quality check.

    Validate Scope is about acceptance by the customer or sponsor against acceptance criteria. Control Quality is about correctness against quality requirements. Different people, different question.

  • "Deliverables are accepted at project closure."

    Acceptance happens through Validate Scope, often repeatedly during the project. Closing transfers the already-accepted deliverables and confirms all work is complete.

  • Putting activities in the WBS.

    The WBS breaks down deliverables to work packages. Activities are defined later, in the activity list, by decomposing work packages.

  • Calling a milestone a deliverable.

    A milestone is a significant point in time with zero duration, often marking a deliverable’s completion. The deliverable is the thing; the milestone is the moment.

Deliverable vs neighbouring terms

TermWhat it isExample
DeliverableA unique, verifiable product, result or capabilityThe redesigned website
RequirementA condition or capability the deliverable must meetCheckout loads in under 3 seconds
Work packageLowest level of the WBS, where cost and duration are estimatedCheckout page build
MilestoneA significant point or event, zero durationWebsite go-live
OutcomeThe change the deliverable makes possibleFewer abandoned carts
BenefitThe measurable gain the organization realizes8% more completed orders per month

Why this matters on the newer exams

The PMBOK Guide 7th edition shifts the emphasis from producing deliverables to delivering outcomes and value. Deliverables still matter (they sit in the Delivery performance domain), but scenario questions increasingly ask whether a deliverable that met its criteria actually achieved the intended outcome. A project can produce every deliverable on time and still miss its business objective.

Practice and related pages

Key Points

  • •Unique and verifiable: there must be an objective way to confirm it is complete
  • •Three forms: a product, a result, or a capability; internal or external
  • •Predictive flow: deliverables, then verified deliverables (Control Quality), then accepted deliverables (Validate Scope), then transition (Close Project or Phase)
  • •The WBS is deliverable-oriented; activities are not part of it
  • •In agile, the increment is the deliverable, governed by acceptance criteria and the definition of done
  • •Deliverables are outputs; outcomes and benefits are what they make possible

Exam Tip

Order matters: Control Quality (verified) comes before Validate Scope (accepted). If a scenario has the customer rejecting a deliverable, look for the answer that documents the rejection and routes the fix through change requests, not one that quietly reworks it or adds extras to win approval (gold plating).

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Predictive Life Cycle (Waterfall)

A predictive life cycle is a plan-driven approach where the project scope, schedule, and cost are determined early and changes are carefully managed.

Subsidiary Plans

Subsidiary plans are the individual management plans that are components of the overall project management plan, each addressing a specific Knowledge Area or management function.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Part of

PM Fundamentals & Frameworks

Study full domain →

Practice Deliverables

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.