Deliverable
Any unique and verifiable product, result, or capability that must be produced to complete a process, phase, or project.
Breaking down the definition
Lets break this definition down so we can better understand its meaning, particularly the concept of being "verifiable."Unique: A deliverable is distinct and specific to the project at hand. It isn't a generic output but something tailored to the needs and objectives of the particular project. The Project Management Body of Knowledge (PMBOK) notes that repetitive elements may be present in some project deliverables, but this repetition does not change the fundamental, uniqueness of the project.
Verifiable: This is a critical aspect of the definition. A deliverable being "verifiable" means that it can be measured, tested, or validated in some way to ensure it meets the required standards or specifications. Verification is the process of confirming that the deliverable has been produced according to the predefined requirements and is of the expected quality. This could involve various methods depending on the nature of the deliverable, such as:
- Testing: For a product or software, testing could be used to verify that it functions as intended.
- Review and Approval: Documents or plans might need to undergo a review process and be approved by relevant stakeholders.
- Inspections or Audits: Physical constructions or organizational processes may be verified through inspections or audits.
- Performance Metrics: For results like increased sales or improved performance, verification could involve comparing against specific metrics or KPIs (Key Performance Indicators).
- Product: a tangible item like a machine, or intangible like a behaviour change.
- Result: outcomes or benefits derived from the project, such as increased efficiency, market research findings, or educational achievements.
- Capability: a new ability or capacity developed as a result of the project, like enhanced skills or new processes.
In summary, a deliverable in project management is not just any output; it must be distinctive, confirmable through some form of validation, and crucial for the successful completion of a particular stage or the entire project. This ensures that all efforts are aligned towards producing outcomes that can be demonstrably shown to meet the project's goals and requirements.
See also product, service, and result.
The Role of Deliverables in the Work Breakdown Structure (WBS)
The Work Breakdown Structure (WBS) is a foundational tool in project management, used to divide and conquer the scope of a project. Deliverables play a pivotal role in structuring the WBS, serving as the primary building blocks for breaking down the project work.How Deliverables Structure the WBS
The Work Breakdown Structure is structured by the project deliverables, with the major deliverables broken down into Work Packages.In the WBS, a project is decomposed into smaller, more manageable components, with each level providing a more detailed breakdown of the work required. At the highest level of the WBS, the major deliverables are identified. These deliverables represent the significant outputs or results that the project is committed to producing. By focusing on deliverables rather than tasks, the WBS aligns the project team and stakeholders around clear, tangible outcomes, ensuring a results-oriented approach to project management.
Each major deliverable is then further broken down into smaller elements, eventually reaching a level of granularity where the work can be easily assigned, estimated, monitored, and controlled. This hierarchical decomposition of deliverables into smaller work packages is fundamental to effective project planning and execution.
The relationship between Deliverables and Work Packages
The Process of Breaking Down Major Deliverables into Work Packages
The process of breaking down major deliverables into work packages involves several key steps.Identification of Major Deliverables
Starting with the project scope, the major deliverables are identified. These are often aligned with the key milestones or objectives of the project.Decomposition into Smaller Components
Each major deliverable is then decomposed into smaller, more manageable components. This step requires a thorough understanding of the work involved in realizing each deliverable.Development of Work Packages
As the decomposition progresses, the work is broken down into work packages. A work package is the smallest unit of work in the WBS and is manageable and assignable. It includes detailed tasks that are necessary to produce a part of a deliverable.Assignment of Responsibilities
Each work package is assigned to specific team members or groups, along with clear responsibility for its completion. This assignment clarifies accountability and facilitates better tracking and management of work. See our Resource Assignment Matrix and RACI template..Estimation of Resources and Duration
For each work package, the necessary resources, effort, and time required are estimated. These estimations are crucial for project scheduling and budgeting.Integration into the Overall Project Plan
Finally, the work packages are integrated into the overall project plan, linking them with the project schedule, resources, and budget.By structuring the WBS around project deliverables, project managers can ensure a clear focus on producing tangible outcomes. This deliverable-oriented WBS facilitates better understanding and communication of project scope, improves accountability, and enhances the ability to track and measure project progress and performance. The ultimate goal is to ensure that each piece of work contributes meaningfully towards the completion of the project's deliverables, aligning the day-to-day work with the project's overarching objectives.
What are examples of Project Deliverables?
Project deliverables can vary widely depending on the nature and scope of the project. They can be categorized into those that are internal and those that are external. Internal deliverables are required to deliver the project, while the external deliverables are typically delivered to the end users or customer. The term is often used more narrowly in reference only to external deliverables, which are usually subject to approval by the project sponsor or customer.Here are some examples across different types of projects:
Construction Project:
- Blueprints and Design Plans: Detailed architectural or engineering designs.
- Built Structure: The completed building or infrastructure.
- Safety Inspections and Compliance Reports: Documentation ensuring the project meets safety and regulatory standards.
- Software Application: The final software product ready for deployment.
- Source Code: The complete source code of the software.
- User Manuals and Documentation: Guides and documentation for end-users and maintainers.
- Marketing Materials: Digital or print advertising materials, such as brochures, banners, or social media content.
- Campaign Strategy Document: A detailed plan outlining the campaign strategy, target audience, and objectives.
- Analytics Report: Data and analysis on the campaign's performance.
- Research Paper or Report: The final document detailing the research findings and methodologies.
- Data Sets: Collected and processed data that was used in the research.
- Presentations: Slides or posters presented in conferences or meetings.
- Event Itinerary: A detailed schedule of the event.
- Venue Arrangement: Completed setup of the event venue.
- Post-Event Report: Analysis of the event's success, including attendee feedback and financial report.
- Prototype: An early model of the product to test and refine the design.
- Final Product: The completed, market-ready product.
- Market Analysis Report: Insights into market trends and consumer preferences relevant to the product.
- Curriculum or Course Material: Educational content and materials for the program.
- Certification or Accreditation: Documents certifying the completion or accreditation of the program.
- Feedback and Evaluation Reports: Analysis of the program's effectiveness based on participant feedback.
- Consultation Report: A document providing analysis, solutions, and recommendations for the client.
- Implementation Plan: A step-by-step plan for implementing the consultant's recommendations.
- Follow-up Assessments: Reports or meetings assessing the implementation's progress or success.
Which PMBOK project documents relate to deliverables?
In the Project Management Body of Knowledge (PMBOK), several project documents are directly related to deliverables. These documents are essential for planning, executing, monitoring, controlling, and closing project work. They help in defining, tracking, and managing the project's deliverables. Here are some of the key documents:Change Requests: During the project, any proposed changes that might affect project deliverables are documented in change requests. These are formally reviewed and approved or rejected. Get a Change Request Template.
Project Charter: This document formally authorizes a project and provides a high-level description of the project, including its objectives and main deliverables.
Project Management Plan: This comprehensive document outlines how the project will be executed, monitored, and controlled. It integrates and consolidates various subsidiary plans, including scope management, schedule management, and cost management plans, which all relate to the project's deliverables.
Quality Management Plan: This plan describes how the project management team will implement its quality policy. It includes quality control activities that verify whether the project's deliverables meet the defined quality standards.
Requirements Documentation: This document captures the conditions or capabilities that must be met by the project deliverables to meet the stakeholders' needs and expectations.
Download requirements management templates:
- Requirements Gathering Template
- Requirements Management Checklist
- Requirements Management Plan
- Requirements Traceability Matrix
Work Breakdown Structure (WBS): The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team. It identifies the project's major deliverables and breaks them down into smaller, more manageable parts. Get a Work Breakdown Structure Template. Download example Work Breakdown Structures.
Work Breakdown Structure Dictionary: Accompanying the WBS, this document provides detailed descriptions of the work packages and deliverables in the WBS, including work activities, deliverables, and timelines.
Logs and registers for tracking progress of deliverables, and the issues and risks that might impact them
Issue Log: While not directly about deliverables, this document tracks issues that can impact the project, including risks to project deliverables.Lessons Learned Register: Captures the lessons learned concerning the management of project deliverables, which can be useful for future projects.
Risk Register: Identifies risks that could affect the project's deliverables and outlines strategies for managing these risks.
Status Reports: Regular reports that provide information on the progress of the project, including the status of deliverables.
These documents are crucial for ensuring that the deliverables are well-defined, agreed upon, and aligned with the project goals. They also provide a framework for tracking the progress and performance of deliverables throughout the project lifecycle.
See all project management words
Methodology specific dictionaries / glossaries
- View the Agile Dictionary
- Managing Successful Programmes (MSP) Dictionary
- Prince 2 glossary of terms
- Full ITIL glossary of terms
- See also Risk Management Dictionary.