A project may produce one or more deliverables. Each of these deliverables must be formally accepted. Deliverables acceptance management ensures that these deliverables meet the predefined objectives and criteria outlined in the [[Deliverables Acceptance Management Plan|Deliverables Acceptance Plan]], so the project requestor can formally accept them. Note that final project acceptance takes place in the Closing Phase. ![[Table 9.10 - Manage Deliverables Acceptance - Key Participants.png]] ## Inputs - Deliverables Acceptance Plan - Project Work Plan - Quality Management Plan - Outsourcing Plan (if applicable) ## Steps 1. The Project Manager (PM) ensures that the acceptance procedures and guidelines are applied and the necessary environments (space, infrastructure, tools, etc.), materials and information are provided for the acceptance process to take place. 2. The Project Steering Committee (PSC) approves the application of the documented acceptance strategy and acceptance schedule. 3. The project deliverables are accepted if the acceptance activities (as described in the Deliverables Acceptance Plan) are carried out within a pre-specified [[tolerance]] range. Note that project deliverables can be conditionally accepted, even with a set of known defects or issues, if these are documented and if there is a plan in place for addressing them. 4. The Business Manager (BM) provides (qualified) resources to support the users’ acceptance of the deliverables. 5. The Project Manager (PM) ensures that supporting deliverables (such as documentation) are supplied in addition to the main deliverables (taking an Information System as an example, such deliverables could include end-user support material, a User Manual, an Operations Manual, training materials, release notes, etc.). 6. The Project Owner (PO) formally accepts the project’s deliverables. **Note**: When domain-specific (e.g. technical) documentation is delivered for acceptance, it needs to be reviewed by a subject matter expert/representative. ### For example: - A stakeholder with business knowledge representing the business organisation—e.g. a User Representative (UR)—should review a User Manual. - A stakeholder from the support and maintenance organisation should review an Operations Manual. - A stakeholder from the organisation responsible for training should review training materials. - A stakeholder from the service operations organisation should review release notes. ![[Fig 9.11 Manage Deliverables Acceptance inputs - outputs and main roles.png]] ![[Table 9.10 - Manage Deliverables Acceptance - Related Artefacts.png]] ## Outputs - Deliverables Acceptance Checklist (PM2 Template) - Decision Log (PM2 Template) - Deliverables Acceptance Note ___ 🔼 [[9 Monitor & Control]] ◀️ [[9.9 Manage Quality]] ▶️ [[9.11 Manage Transition]] Spanish Guide: [[9.10 Gestión de la Aceptación de Entregables]] ___ ![[👉 Quick links]]