Deliverable
DE: Lieferergebnis
Any unique product, result, or capability produced by a project.
Detailed Explanation
A deliverable is any unique and verifiable product, result, or capability produced to complete a process, phase, or project. Deliverables can be tangible (a software application, a building) or intangible (a training program, a process improvement).
Every deliverable should have clear acceptance criteria that define when it is considered complete and acceptable. The scope statement lists the major deliverables, and the WBS decomposes them into manageable work packages.
Deliverables are the building blocks of project value. They are what the project produces for the customer or organization. Managing deliverables effectively requires clear definition, quality standards, and formal acceptance processes.
Key Points
- Can be tangible (product) or intangible (service, result)
- Must have clear acceptance criteria defined upfront
- Listed in the scope statement, decomposed in the WBS
- Subject to quality control and formal acceptance
- Building blocks of project value delivery
- Must be verified and validated before acceptance
Practical Example
An ERP implementation project has these deliverables: requirements document, system configuration, data migration scripts, user training materials, go-live support plan, and post-implementation review report. Each has acceptance criteria. The client formally accepts each deliverable after QC review.
Tips for Learning and Applying
Define acceptance criteria for every deliverable before starting work
Track deliverable status in a deliverable register
Conduct quality reviews before presenting deliverables for acceptance
Document formal acceptance with stakeholder sign-off
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.