Download OCIO Deliverable Overview and Acceptance Form

<Insert project name>
Deliverable Overview and
Acceptance Form
Template
Deliverable Overview and Acceptance Form
Document Control Information
Document Information
Document Identification
<Insert document ID, if applicable>
Document Name
Deliverable Overview and Acceptance Form
Project Name
<Insert project name>
Document Author
<Insert author name>
Document Version
<Insert version number>
Document Status
<Insert document status>
Date Released
<Insert release date dd-mmm-yyyy>
Document Edit History
Version
Date
<Version #>
Additions/Modifications
< dd-mmm-yyyy >
<Provide additional details about this
document version.>
Prepared/Revised by
<Name>
Document Review/Approval History
Date
Name
< dd-mmm-yyyy >
<Name>
Organization/Title
<Organization/Title>
Comments
<Comments>
Distribution of Final Document
The following people are designated recipients of the final version of this document:
Name
<Name>
Document Control Information
13-Aug-17
Organization/Title
<Organization/Title>
Page ii
<Insert project name>
Document1
Deliverable Overview and Acceptance Form
<Insert document
ID, if applicable>
Document Guide
The following table presents the answer to some of the key initial questions regarding the Deliverable
Overview and Acceptance Form.
Topic
Guidance
This document serves two purposes:
Why is this document
important?
1. Define the requirements for the successful completion of a deliverable
2. Provide the process for formally accepting and signing off a deliverable
Why should I use this
document?
This form establishes a consistent understanding of what is required for
successful completion of the deliverable and provides a record of that agreement
Further, it expedites closure and approval of deliverables by explicitly identifying
the success criteria (at the start), so both the project team and approver clearly
understand the end goal(s)
Is this a mandatory document?
The Deliverable Overview and Acceptance Form is a mandatory document for all
IM/IT projects.
Who should complete this
document?
Any individual or group of people who are responsible to approve the
deliverable(s), as defined in the Project Management Plan.
Is this document required for
OCIO reporting?
No
Where can I get additional help
from?
Ministry PMO or PMP designated project manager.
Once you have reviewed and completed this document, please answer the question below:
In reviewing and completing this form, have you
identified any new risks or issues that are not
fully addressed by the Deliverable Overview and
Acceptance Form document?
13-Aug-17
 Yes
 No
If yes, have you recorded and escalated the risk/issue in
the appropriate log?
Page 3 of 6
<Insert project name>
Document1
Deliverable Overview and Acceptance Form
<Insert document
ID, if applicable>
Purpose
This form includes six sections that need to be completed by the owner (“R” in the RACI) of the
deliverable package.
1. Deliverable Package Overview
Project Name:
<Enter the name of the project.>
Project Sponsor:
<Enter project sponsor’s name.>
Phase:
<The project phase where the project deliverable was created.>
Deliverable Name:
<Enter the name of the deliverable under review for deliverable
acceptance.>
Deliverable Approver:
<Enter the deliverable approver as identified in the PM Plan or
other project process>
Deliverable ID:
<Enter the project deliverable ID or tracking #.>
Purpose of Deliverable
<Provide a summary of the purpose of the deliverable.>
Assumption(s)
<State the assumption(s) made in developing the deliverable.>
Date Deliverable
Submitted for
Acceptance:
<dd-mmm-yyyy>
Deliverable
Acceptance
Due Date:
<dd-mmm-yyyy>
2. Deliverable Package RACI Overview
Role #7
I – Informed: Those who are kept up to date on the task / activity / deliverable
Role #6

Role #5
C – Communicated: Those who are consulted / communicated with
Role #4

Project Manager
A – Accountable: Accountable (provides approval) for task / activity / deliverable
Project Sponsor

Executive
Sponsor
R – Responsible: Responsible for the task / activity / deliverable
Project Roles

Role #8
State the project roles in the columns and list each deliverable in the deliverable package per row.
For each deliverable, complete the RACI model and include, at a minimum, those stakeholders
who must provide input and or review before signoff will be provided. This prevents surprises or
last minute additions to the review process that can cause project delays. Additionally, the
(typically and ideally single) formal approver must also be identified with the “A” in the RACI table.
Name of Deliverable #1
Name of Deliverable #2
Name of Deliverable #3
3. Dependencies
13-Aug-17
Page 4 of 6
<Insert project name>
Document1
Deliverable Overview and Acceptance Form
<Insert document
ID, if applicable>
State other activities or documents that are dependent on the acceptance of this deliverable
package.
Project Plan Task #
Dependency
Dependency Name
123
Date
<dd-mmm-yyyy>
Owner
Jon Doe
4. Deliverable Acceptance Criteria
Acceptance Date:
<dd-mmm-yyyy>
<State the deliverable acceptance criteria as stated in the Project
Management Plan.>
Examples include:
Deliverable Acceptance
Criteria:
1.
2.
3.
4.
5.
Comprehensiveness
Completeness
Accuracy
Alignment with business case outcomes / objectives
Etc.
Accepted
Acceptance Response:
Not accepted until the comments below are addressed
5. Additional Comments
Comments
Document comments regarding the acceptance of the deliverable.
If the deliverable is not accepted, the reviewer and or approver must:
i.
Reference the specific failed criteria, which were previously identified, documented and
accepted in the Project Management Plan or Deliverable Overview document(s).
ii.
Describe, in detail, the item(s) preventing acceptance in a manner that clearly establishes
what remediation is required to accept the deliverable.
Summary comments…

Bullet 1

Bullet 2

Etc.
6. Sign-off
Name & Title
Signature
<Name & title of the representative
authorized to accept the project
deliverable>
<Signature of the
representative authorized to
accept the project deliverable>
13-Aug-17
Page 5 of 6
Date
<Date of the signature>
<Insert project name>
Document1
Deliverable Overview and Acceptance Form
<Insert document
ID, if applicable>
---- END DOCUMENT ----
13-Aug-17
Page 6 of 6
<Insert project name>
Document1