Project Management
  1. Home
  2. Plan
  3. Plan

Plan

 

These should be reviewed at first meeting between PM and Sponsor.

Note that our key milestones should have these listed too.

There are a number of roles which are often typical, some essential, for any project.

Roles can vary greatly from project to project depending on the scale and complexity of what the project is to deliver.  Some projects have individuals performing multiple roles, some have additional roles not specified in this list, and some of the roles listed here may not be required at all.

Every project must have a Project Sponsor and a Project Manager.

 

Governance

Project will all have these governance roles by default.

Priority and Funding

This has been initiated at the direct instruction of the Chief Information Officer and as such is a Priority 1 initiative but a Priority 5 within the Programme. Funding is direct (£200k 16/17) and from existing budgets for handling such projects.

 

Background

For over a year the University has run on one of its two gateway nodes a proof of concept IDS using Suricata and ProofPoint Emerging Threats Signature feed. This is a daily updated list which covers more than forty different categories of network behaviours, malware command and control, DoS attacks, botnets, informational events, exploits, vulnerabilities, SCADA network protocols.

 

The objective of this project is to mature this proof of concept as follows:

Document Sign-off

Name Role Date signed off
Alistair Fenemore Project Sponsor 13/04/17
Kirsty Waddell Project Manager 17/04/17
Tony Weir Project Executive 17/04/17
     

 

Governance

Project will all have these governance roles by default.

11.Impact

The project focusses on reviewing existing ways of working and technology and therefore its impact is low. However the execution of any recommendations could have a significant impact across all University Departments, Colleges and Schools.

12.Priority and Funding

Funding is direct and from existing budgets for handling such projects.

13.Impact on Other Projects

1.Background

This project was meant to be done last year but didn't go ahead as it was decided to proceed with something practical that would directly impact end users. Therefore new ways of authenticating on the wireless network and Office 365 were pursued instead.

2.Objectives

The objectives of this project are as follows:

Document Sign-off

Name Role Date signed off
Tony Weir Project Sponsor  
Iain Moore-McLaughlin Project Manager  
Maurice Franeschi Portfolio Manager  
Graeme Wood Senior Supplier