Skip to content
PMPCAPM

Deliverables

A deliverable is any unique and verifiable product, result, or capability to produce a service that is required to be produced to complete a process, phase, or project.

Share:

Explanation

Deliverables are the tangible or intangible outputs that the project produces. They can be physical products (a building, a piece of software, a document), results (improved process efficiency, research findings), or capabilities (a trained workforce, an operational system). Every project exists to create deliverables, and the success of the project is largely measured by whether those deliverables meet the acceptance criteria defined by stakeholders.

Deliverables go through several states during the project. They are first defined during scope planning and documented in the project scope statement and WBS. They are created during execution through the Direct and Manage Project Work process. They are verified through quality control processes (Control Quality) and formally accepted through the Validate Scope process. Finally, they are handed off during closing.

It is important to distinguish between internal deliverables (intermediate outputs needed for the project but not delivered to the customer, such as a project management plan or a design document) and external deliverables (the final products or services delivered to the customer or end user).

Key Points

  • Unique and verifiable products, results, or capabilities
  • Defined during planning, created during execution, accepted through scope validation
  • Must meet stakeholder acceptance criteria
  • Can be internal (for the project) or external (for the customer)

Exam Tip

Validate Scope is the process that formally accepts deliverables. Control Quality verifies deliverables meet quality requirements. The exam frequently tests whether acceptance (Validate Scope) or quality checking (Control Quality) comes first — quality control precedes validation.

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 is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

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.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Part of

PM Fundamentals & Frameworks

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.