<Project Name>
Stage Gate 2 Review – Delivery Readiness Assessment
Revision History
Date
Version
Author
Description
Project Information
Project Name
Project Manager
Project Executive
Business Owner
Project Objective
Gate Approval Date
<Project Name> – Stage Gate 2 Review Report
Page 1 of 9
<Project Name> – Stage Gate 2 Review Report
How to use this document: (when complete, delete this guidance text)
The Stage Gate Description in section 1 below describes the overall purpose of this gate review,
and the artefacts that may be required. The Project Manager or Team Leader should use the
appendix, Review Gate Considerations, as a checklist to assist in preparing for the gate review.
When the Project Manager or Team Leader has completed the checklist, the PMO will review it
and provide feedback and questions, helping to ensure that appropriate planning has been done
for the next phase of the project. Evidence of review activities may be requested and must be
accessible if required.
The PMO will complete section 3, providing a recommendation based on the review, with details
in an Executive Summary. This recommendation will be one of the following:



Approved to advance to the next phase,
Not approved to advance to the next phase, or
Conditionally approved to advance to the next phase, when the action items provided
are cleared.
The Project Manager or Team Leader will be advised of the results of the review, and should
share this with their Project Board and other governance groups.
Page 2 of 9
<Project Name> – Stage Gate 2 Review Report
1. Stage Gate Description
The primary function of Stage Gate 2 – Delivery Readiness Assessment is to approve
that the appropriate level of planning has been undertaken, and that the project is ready
to begin the Build/Configure stage. Final approval of the Project Initiation Document
(PID) takes place at this Gate. Approval at this gate is a commitment that all resources
required will be made available to the project.
1.1. Stage Artefacts (as applicable)
Document
Description
Project Initiation
Document (PID)
At this stage, the PID will be in final configuration, and have
the approval of the Project Board. Full details of how the
project will be delivered must be included, including details of
all resources required during the life of the project.
Project Plan
This is a detailed plan of delivery for the project. It includes all
resources required, which are assigned at task level for all
stages of the project.
Detailed
Requirements
This is the final signed off version of the requirements from the
users. It must detail all requirements, listing their priority i.e.
Must Have, Nice to Have, etc.
Detailed Design
The Technical Architect translates the Solution Design into
technical details that will enable the development team to
proceed with the Build and/or configuration of the solution. It
should be endorsed by the Solution Design Authority to
ensure compliance with the approved architecture.
Test Plan
This plan will detail all levels of testing to be performed during
the Build/Configure/Test phase of the project. Iterations of
testing cycles should be indicated, as well as environments to
be used for the testing. Details must also be included of the
exit criteria for each level of testing i.e. what exit criteria must
be met at each level to proceed to the next level.
Vendor Selection
If the solution involves a vendor, there must be a summary of
the process followed to select the most suitable candidate.
Selection criteria and scoring against those criteria must be
shown to lead to a totally objective selection.
Page 3 of 9
<Project Name> – Stage Gate 2 Review Report
2. Approval Signatures
Approver Name
Title
Signature
Date
PMO Manager
Page 4 of 9
<Project Name> – Stage Gate 2 Review Report
3. Review Gate Checklist
Item Question
Response
1
Is the plan for delivery of the project reasonable, and been approved by all
necessary parties?
Yes
No
2
Has the appropriate technical authority endorsed the technical solution?
Yes
No
3
Is there evidence that the Support Team has been engaged in the planning
process, and agreed?
Yes
No
4
Is the Test Plan detailed enough to ensure success of the testing regime?
Yes
No
5
If appropriate, is the vendor selection process clearly objective, and focused
on finding the best candidate?
Yes
No
Gate Review Executive Summary
It is recommended that progress to the Build/Configure/Test phase for this project be:
Approved
Not Approved
Conditionally Approved
This recommendation is based on....
Page 5 of 9
<Project Name> – Stage Gate 2 Review Report
4. Open Issues
Issue
Planned Resolution
Page 6 of 9
<Project Name> – Stage Gate 2 Review Report
Appendix: Review Gate Considerations
Consideration
Artefact
Complete
Comments/Reference
Detailed Design:
 Detail requirements
Detailed
Contains detailed functional and derived
Requirements
technical requirements of appropriate level to
drive detailed design.
 Detailed design
Detailed solution design, including as-is and
to-be diagrams. To be endorsed by
appropriate technical authority.
Detailed
Design
 Test plan
Describing testing strategy, as well as
progression, regression, UAT, and any other
testing. Should include exit criteria.
Test Plan
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Project Planning:
 Final scope
Final agreed scope, including all inclusions
and exclusions. A scope change management
plan is in place.
PID
 Final deliverables
An agreed list of all project deliverables.
PID
 Work breakdown structure (WBS)
Breaks the scope of work down to a work
package level. This may require refinement
as work progresses. Work packages include
estimates of time to complete work.
PID, Project
Schedule
 Resource estimates
Internal and external resource requirements
based on WBS work packages.
PID
 Schedule
Should include milestones, dependences,
resources, and the identified critical path.
Project
Schedule
Page 7 of 9
<Project Name> – Stage Gate 2 Review Report
 Budget
Includes both internal and external/vendor
resources and materials by month. Ideally,
high/low/ most likely or +/-% estimates will
be provided.
Budget, PID
 Communication plan
Updated plan includes all stakeholder and
team communication requirements for the
delivery phase. Evidence that the plan is
being followed.
PID
 Governance
Updated plan confirms all lines of reporting
and escalation, reviewers, approvers, and
decision makers for each deliverable or
decision point. Evidence that plan is being
followed, including the establishment of
Project Board.
PID
 Quality plan
Describes methods for ensuring high standard
of deliverables, including reviewing and
approval of project documentation, and
implementation test plans. Evidence that plan
is being followed. This may be combined with
deliverables list.
PID
 Stakeholder engagement
Management plan is up to date, stakeholders
are being engaged, requirements have been
elicited, and expectations being managed.
PID
 Risks and Issues logs
Identifies risks and issues, owners, dates,
likelihood, impact, mitigation plan, with
evidence of regular review and update.
Risk Log
Issues Log
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No

Business change management (BCM)
plan
Contains results of initial impact assessment
and plans for addressing information and
training needs.
PID
Procurement Planning:
Page 8 of 9
<Project Name> – Stage Gate 2 Review Report
N/A
 Vendor requirements
PID, Vendor
Identified vendor requirements based on WBS Selection Plan
work packages.
N/A
 Vendor Contract
Contractual agreement for the vendor to
deliver the required scope of work.
N/A
 Vendor selection
The method used to select a vendor, and the
method to be used to manage risks and
ensure successful delivery.
Contact
PID, Vendor
Selection Plan
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Controls:
 Final PID Signed off
Project Board approval provided.
PID
 Detailed Design
Detailed Design documented and signed off
by appropriate technical authority.
 Vendor selection approved
Project Board approval provided.
 Support Requirements
PID endorsed by Support Team Lead
N/A
Detailed
Design
PID, Vendor
Selection
Plan, Contract
PID
Page 9 of 9