Gate Review
A recorded decision to proceed, proceed with conditions, or stop, against the gate criteria, the end stage report and the updated business case.
Why it matters
Gates stop projects drifting into go-live unprepared.
- When
- End of every phase
- Length
- 1–2 hours
- Led by
- Senior Responsible Owner
- Draws on
- GovS 002; PRINCE2 Managing a stage boundary
- PRINCE2
- Managing a stage boundary, then Directing a project: authorise the next stage
Draws on
Led or owned by
In the resource library
Ready-to-use resources in the DelPulse workspace (sign in to open them):
- Ways of working playbook: how work flows · Playbooks
- New idea and request prioritisation · Guides
- Portfolio Kanban states and exit criteria · Guides
- Portfolio Lead · Role guides
- Solution Architect · Role guides
- Senior Responsible Owner self-assessment · Self-assessments
The rest of this page is for subscribers
Subscribe to read the other 4 sections of this page:
- How to run it
- Rules
- In the DelPulse workspace
- If you use Jira or Azure DevOps