<Project Name>
Stage Gate 0 Review – Registration & Process Advice
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 0 Review Report
Page 1 of 7
<Project Name> – Stage Gate 0 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 7
<Project Name> – Stage Gate 0 Review Report
1. Stage Gate Description
The primary function of Stage Gate 0 – Registration & Process Advice is to provide
formal approval for the Project Brief. Once this gate is successfully passed, the project
will proceed into the Feasibility phase, where the Business Case will be developed. This
gate approves the project to be included in the ITS portfolio, but full approval for the
project will occur at Gate 1. Funds approved at this gate are for Feasibility phase
activities only.
1.1. Stage Artefacts (as applicable)
Document
Description
Project Brief
The Project Brief is the initial document used to define the
project. It contains details of the scope of work to be
undertaken and objectives to be achieved. It will also include
a summary of the approach to be taken for delivery of the
project, and a high level indication of the governance
structures to be adopted. That is, it may indicate that there
will be a Project Board, and what roles will sit on the board,
but not necessarily who will fill those roles at this stage.
Needs
Assessment
This is the high level requirements from the users. It is really
a structured list of all of the business outcomes that are being
expected by the users.
Project approach
This document is produced by the Enterprise Architect, and
will detail the approach that the project should follow to best fit
in with the strategic architecture requirements of the
University. This approach will be endorsed by the University
ICT Architecture Committee before inclusion in the Project
Brief and submission to Gate 0.
Page 3 of 7
<Project Name> – Stage Gate 0 Review Report
2. Approval Signatures
Approver Name
Title
Signature
Date
PMO Manager
Page 4 of 7
<Project Name> – Stage Gate 0 Review Report
3. Review Gate Checklist
Item Question
Response
1
Has the project demonstrated the level of Feasibility activities that will be
required?
Yes
No
2
Has the University ICT Architecture Committee (or other appropriate technical
authority) endorsed the technical approach?
Yes
No
3
Has the project been prioritised appropriately against the remainder of the
portfolio?
Yes
No
4
Have the deliverables for the Feasibility Phase been identified?
Yes
No
5
Is the proposed governance structure appropriate for the size and complexity
of the project?
Yes
No
Gate Review Executive Summary
It is recommended that progress to the Feasibility phase for this project be:
Approved
Not Approved
Conditionally Approved
This recommendation is based on....
Page 5 of 7
<Project Name> – Stage Gate 0 Review Report
4. Open Issues
Issue
Planned Resolution
Page 6 of 7
<Project Name> – Stage Gate 0 Review Report
Appendix: Review Gate Considerations
Consideration
Artefact
Complete
Comments/Reference
Project Definition:
 High level concept/scope statement
In broad terms, this describes what the
project will accomplish.
Project Brief
 Project Sponsor identified
A single individual is identified as the Sponsor.
Project Brief
 Key stakeholders
Primary stakeholders and/or groups are
identified.
Project Brief
 High level business requirements
Business requirements at the highest level are
identified and documented. It should be
stated how the project aligns to strategic
goals.
Project Brief
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Project Approach:
 Project Manager
PM or appropriate project oversight is
assigned.
Project Brief
 Project Approach
Project approach is agreed and documented.
Project Brief
 Governance
High level governance plan is documented.
Project Brief
Controls:
 Funding available
Funding is allocated for Feasibility phase.
 Technical Approach
Approach documented and signed off by
appropriate technical authority.
Page 7 of 7