Project templates for the IS Critical Path
In promoting best practices, the IS Department has submitted a standardised set of project and "business as usual" (BAU) templates for approval by Campus Development. These templates will enable a consistent structure to be followed when managing tasks on the IS critical path. The amount of detail to be captured should be commensurate with the size and scope of each project/BAU.
Details on the different roles and responsibilities relating to project management are available here
|Project proposal template||
The Project Proposal should be completed at the very start when the project is in the early ideas phase. The information provided is likely to be sketchy, but it should be sufficient to determine what the scale of the project is likely to be and the extent to which the benefits justify the resources to be applied. It provides an outline of the project and is used by the SLT Campus Development sub-committee to determine whether the proposal should be progressed to the charter development stage.
Click on this link for details the Draft IS Critical Path approvals process
|Project charter template||
The Project Charter will be written following approval in principle by Campus Development of a project proposal. The Charter should provide sufficient information to provide a high-level understanding of all elements of the proposed project and will enable Campus Development to decide whether to commit the requested costs and resources to the project.
"Business as usual” (BAU) is the repeated delivery of ICT-related services in support of business operations. BAU is funded through recurrent IS budgets and will require fewer than ten IS person-days per iteration. This work is considered essential but an assessment of the resources is required to ensure the overall Critical Path is achievable
|Project budget||This template allows you to track your project’s spending to current and original spending plans|
MS project is the preferred method for managing your project plan
Once approved and project execution commences a progress report must be submitted at periodic intervals (usually every 2 weeks) to the ISPMO. This report must detail the progress of the project against the project management plan. ISPMO will use these report to update ISSC on the progress of the development programme
|RAID log||The ISPMO risk register is mandatory to document project risk however it is acceptable to use other risk registers templates|
|Project Closure||The project closure form is initiated once the project work is completed. The closure form captures key information such as lessons learned through the project and benefits realised.|
|Change control form||
The change control form is initiated if the project deviates significantly from the project management plan. The change control form must detail the key changes proposed for the project and approval is required from the ISSC to proceed.
|Agenda template||Sample template to structure project team, board and other meetings|
|Minutes template||Sample template to record decisions and actions for project team, project board or other meetings|
|Roles & Responsibilities||Identifies the and lists roles and responsibilities of project personnell|
|Lessons learned||Lists the things that went well and the things that did not go so well. In supporting process improvement this information will be stored in a lesson learned repository from which future project managers and teams will have access|
|Post project review||A review of a project 3, 6 9 or 12 months after the project closes. This reivew will rate each of the benefits set out in the project charter to identify if they have been acheived.|