livrables

Livrables are the outputs produced as a result of work, delivered to a client or stakeholder, and capable of being evaluated against agreed criteria. They can be tangible goods or intangible services, documents, or data, and they form the basis for acceptance in a project or contract.

Common types include final products, project documentation, software modules, reports, designs, prototypes, datasets, training materials, or a combination of these. Deliverables may be internal (used within the organization) or external (delivered to a customer) and are defined in the project scope and contract.

The delivery process typically begins in initiation and planning, where deliverables and their acceptance criteria are identified. They are controlled through versioning and change management, and verification and validation are used to ensure they meet requirements before formal sign-off by the appropriate authority.

Examples by sector illustrate the variety: software projects may produce code, test plans, and user manuals; construction projects may produce drawings, permits, and a completed structure; research projects may produce datasets and reports; marketing projects may produce campaign assets and analytics.

The management of deliverables is important for scope control, scheduling, budgeting, and quality assurance. Ambiguity or poor definition can lead to scope creep, rework, and stakeholder dissatisfaction. Roles typically involved include the project manager, sponsor, client, and the authorized acceptance authority.

Deliverables are closely related to requirements, and they are often organized within a work breakdown structure and tied to milestones and handoffs. They form the basis for acceptance testing and project closeout.