UNIVERSITY of GLASGOW

IT Services
home > services > IT Services > For Staff > Project office > GU Methodology

GU Methodolgy

How to Manage Projects within the University

The University’s approach to project management is based on PRINCE2, although we have pared down the PRINCE2 methodology to the bare bones. This pared down framework can be applied to all projects no matter how large and complex. Properly managed, this approach should be user-friendly and can be scaled to match the size, risk level and complexity of your project.

The diagram below clearly shows the lifecycle where some elements, namely Project Start-up and Project Closure occur only once. The remaining elements, Planning, Managing and Controlling, form an iterative cycle that may repeat many times before the project is complete.

po lifecycle
                                                                                                 Source: JISC

It must be stressed that the methodology is a framework and nothing more. It is a tried and tested, structured approach that will give you a sound basis for running a successful project. It is not, however, a substitute for creativity. Every project is unique to a degree and involves uncertainty and risk and require a flexible approach to their management.

The University’s Project’s Lifecycle

With every project there is a core amount of documentation required. It is usually the case with projects that organisations want to see documentation but those involved are less keen to produce it. We have tried to keep the required documentation to a minimum.

The table below gives a clear inidication of the documents a project should have.  This is not to say that other documents won't be produced over the course of a project, this is just the minimum that the Universiy expects.  Only IT related projects are required to report to IPSC, other projects will report to their own Project Boards in the first instance.

Phase Documents Required GU Template GU Examples Approval Body
Project Start Up Project Proposal (includes Business Case)

Project Proposal

Programme Information (PI) Project Proposal

IPSC Programme Board

Roles and Responsibilities

 

 

 

Initiating a Project Project Initiation Document   Programme Information Project PID Project Board
Risk Assessment     Project Board
Project Planning & Costing     Project Board
Directing a Project
Project Status Report Status Update Report Physical Resources Status Report IPSC Programme Board
Exception Report   HR Exception Report Project Board
Meeting Minutes      
User Acceptance Testing      
Risk Log Risk Log Programme Information Risk Log Project Board
Issues Log Issues Log Programme Information Issue Log Project Board
Change Control     Project Board 
End Stage Report     Project Board
Project Closure
Project Closure Document   Content Management System Report  Project Board
Post Implementation Review    

Project Board

Lessons Learned