Resources to deliver projects and change
At the end of each project phase (1 to 3), there is a stage-gate which acts as a progress checkpoint. It helps ensure the project is ready for the next phase.
Check you've completed all the relevant steps in the current phase before you move on. It's also important that you get approval from your project sponsor at each stage-gate. It's their responsibility to check everything has been done and confirm the project is ready for the next phase.
You can use our project life cycle and stage-gates checklist (Google Sheet) if it's helpful.
This diagram shows the project phases (in the middle) and the stage-gate checkpoints (on the right). View this diagram in more detail (Google Slides). On the left, it also shows how the project phases relate to the phases of change (plan, implement, embed).
Templates and guides for each phase
Templates and tools for each phase will help you progress through projects and keep on track. Use them to support and enhance your project. Pick and choose for your needs.
Projects vary in size and scope, so we've included templates for small projects and complex larger-scale projects.
- For small projects, you’ll only need a handful of templates. You can use them to help frame your thinking rather than completing every document.
- For large projects with lots of stakeholders, you'll need more documentation and governance. You're likely to use more templates to help stakeholders understand what's happening.
The four stages
Ensure strategic alignment and concept approval. Define the project's 'reason for being' by establishing high-level scope, objectives, and a high level business case to assess viability. Is the project worth the time, effort and resources?
Plan and design the project outputs, approach and requirements. Finalise the business case, including detailed resource requirements, technical specifications and an implementation plan. This phase transitions the project from an 'idea' to 'ready-to-deliver' with a clear plan and rationale.
Deliver the project and manage workstreams. Coordinate resources, manage risks/issues, and maintain stakeholder engagement to ensure outputs are delivered to the required quality and handed over to operations.
Measure the outcomes against the original Business Case and continue to embed the transition to Business as Usual. Ensure that the benefits are tracked and realised.
| Resource | Purpose | Small projects | Large projects | Project phase |
|---|---|---|---|---|
| Concept summary | Capture ideas, ambitions, risks and benefits of the project or change | May not need as much detail | Concept summary | 1. Identification |
| Business case | Provide rationale for the project or change. Clarify scope, delivery methods, resources, risks, benefits and timelines | n/a | Business case (large projects) | 1. Identification (high level overview) and 2. Definition |
| Change impact assessment | Assess the change against the capabilities, functions and business as usual (BAU) activity across the University | May not need as much detail | Change impact assessment | 1. Identification (high level overview) and 2. Definition |
| People impact assessment | This complements the change impact assessment above (it covers the impact of the change on people) | People impact assessment | Same template as small projects | 1. Identification (high level overview) and 2. Definition |
| High-level plan and milestones | Share high-level information to senior leaders to outline the main objectives and deadlines | High-level timeline and milestones (small projects) | High-level plan and milestones (large projects) | 1. Identification |
| Communications strategy and stakeholder engagement plan | Structure how you'll communicate with stakeholders throughout the project life cycle | May not need as much detail | Communications and stakeholder engagement plan (large projects) | 2. Definition |
| Project initiation document (PID) | Define what the project is aiming to achieve (vision, objectives, outputs, delivery methods and governance) | Scoping document (small projects) | Project initiation document (large projects) | 2. Definition |
| Project benefits | Identify, review and measure the benefits of the project or change | Benefits mapping (small projects) | Benefits management plan (large projects) | 2. Definition |
| Project schedule | Define the end-to-end timeline, considering dependencies and resources | Gantt chart template | Same template as small projects | 2. Definition |
| Roles and responsibilities across the project (RACI matrix) | Provide direction and give responsibility and accountability for each task and/or workstream | RACI matrix | Same template as small projects | 2. Definition |
| Project boards and governance | Provide structure and purpose for the project board | Project board - terms of reference (small projects) | Project board - terms of reference (large projects) | 2. Definition |
| Equality impact assessment | Help make sure our practices are inclusive for staff, students and visitors | Equality impact assessment | Same guidance for all projects | 2. Definition and/or 3. Delivery |
| Data impact assessment (DPIA) | A DPIA screening must be carried out before any planned project or change involving personal data | Data impact assessment | Same guidance for all projects | 2. Definition and/or 3. Delivery |
| Risks, issues and dependencies (RAID) | Identify and monitor risks, challenges, blockages, decisions and actions | Risk register (small projects) | RAID and dependencies project log (large projects) | 2. Definition and/or 3. Delivery |
| Procuring accessible systems | Assess digital tools and services you're procuring to ensure they're accessible and compliant. | Procuring accessible systems: Guidance and checklist | Same guidance for all projects | 2. Definition and/or 3. Delivery |
| Project checklist | Check you are ready to start the project | Project checklist (small projects) | Pre-flight checklist (large projects) | 2. Definition |
| Status report | Monitor project progress, report regularly on status and respond to risks and issues | Project status report | Same template as small projects | 3. Delivery |
| Change requests | Document and agree any changes to the scope and delivery of the project or change | May not be needed | Change request form | 3. Delivery |
| Handover outstanding deliverables | Complete a handover to business leads, including any outstanding deliverables or BAU | May not need as much detail | Handover to BAU | 3. Delivery |
| Lessons learned report | Learn from opportunities and challenges, so they can be taken into newer projects | Lessons learned (small projects) | Lessons learned (large projects) | 3. Delivery |
| Project closure report | Review achievements against the business case objectives and success criteria | May not be needed | Project closure report | 3. Delivery |