Plan
Methodology Compliance
|
Methodology Stage |
Standard Stage Sign-Off |
Project Approach |
|
Planning |
Approval by Project Manager, Project Sponsor and IS Applications Management Team (WIS) |
|
|
Business Analysis |
Cost Benefit Analysis
Five Year Costs
|
Tangible Costs Summary |
||||
|
5 Year Summary |
IT Services i.e. IS staff, hardware, software and services |
Support Group Staff Costs |
College Staff Costs |
Total |
Executive Summary
Business Objectives and Project Deliverables
|
No.* |
Description* |
Priority** |
Owner*** |
|
Obj1 |
Output / outcome / benefit / strategic objective |
L/M/H/C or MoSCoW |
This is a multi-page template for the Terms of Reference (TOR).
The Terms of Reference lays out the terms and conditions for the project that is about to be undertaken. It helps to ensure that all stakeholders have a common understanding of what the project is seeking to deliver.
You can navigate through the pages of this template via the page controls displayed at the bottom of this page, or via the menu on the left-hand side.
Contributors
This is a sample project to provide guidance on managing a project using the 'software' type of project methodology. This methodology is particularly suitable for projects developing software, as it includes templates for software design, technical specifications and acceptance testing.
Please feel free to browse.
There are also similar sample projects for the following different types of project:
Current project status
| Report Date | RAG | Budget | Effort Completed | Effort to complete |
|---|---|---|---|---|
| November 2019 | RED | 0.0 days | 0.0 days | 0.0 |
Document Sign-off
|
Name |
Role |
Date signed off |
|---|---|---|
|
Graeme Wood |
Project Sponsor Service Owner |
25/05/2017 |
|
Maurice Franceschi |
Programme Manager |
13/04/2017 |
Priority and Funding
Check the Forward Look and Annual Plan on ITI Sharepoint to see the project's priority within programme and portfolio (and reflect this also on the project info section of the website).
Confirm that we have funding for this project.
Background
This project brief has prompts and tips for many of the sections. Please remove/edit these as they are there to help authors in writing the document and for project teams to consider but not suitable for the final version of the brief.
Scope
Changes to Scope will be logged on the PICCL and also recorded on the Project Scope Change page.
Document Sign-off
| Name | Role | Date signed off |
|---|---|---|
| Project Sponsor | ||
| Project Manager | ||
| Programme Manager | ||