0D Guide to ITS Project Management Templates
3
GUIDE TO ITS PROJECT MANAGEMENT DOCUMENTS MARCH 2012 Document/Template Description 0A Guide to IT Project Management This document is designed as a guide for Project Managers and Sponsors – to provide initial assistance on setting up and running their IT projects. 0B Project Process Diagram This diagram illustrates the Project Management Life Cycle Process for IT projects. The intended audience is ITS staff members who anticipate working on IT projects as either managers or project team members. 0C Guide to Project Roles & Responsibilities This document lists the key roles for IT projects and describes primary duties for each. The intended audience is Otago staff members from any division who anticipate working on IT projects in any capacity. 0D Guide to its Project Management Documents This document lists all of the templates and documents that are available to project managers and what they are used for. 1 Project Concept Form This document allows ITS to capture the ideas that Project Managers and other interested parties have for a project 2 Project Definition This document is the initial document in the ITS project management process initiating the Project Management Life Cycle Process. It is used to clarify and determine a project.
description
ITS PROJECT MANAGER
Transcript of 0D Guide to ITS Project Management Templates
GUIDE TO ITS PROJECT MANAGEMENT DOCUMENTS
MARCH 2012
GUIDE TO ITS PROJECT MANAGEMENT TEMPLATES
Document/TemplateDescription
0A Guide to IT Project ManagementThis document is designed as a guide for Project Managers and Sponsors to provide initial assistance on setting up and running their IT projects.
0B Project Process DiagramThis diagram illustrates the Project Management Life Cycle Process for IT projects. The intended audience is ITS staff members who anticipate working on IT projects as either managers or project team members.
0C Guide to Project Roles & ResponsibilitiesThis document lists the key roles for IT projects and describes primary duties for each. The intended audience is Otago staff members from any division who anticipate working on IT projects in any capacity.
0D Guide to its Project Management DocumentsThis document lists all of the templates and documents that are available to project managers and what they are used for.
1 Project Concept FormThis document allows ITS to capture the ideas that Project Managers and other interested parties have for a project
2 Project DefinitionThis document is the initial document in the ITS project management process initiating the Project Management Life Cycle Process. It is used to clarify and determine a project.
3A Project Business CaseThis document is the final output of the initiation phase of the Project Management Life Cycle. It describes the business drivers which justify undertaking the project. It also provides an opportunity to give a brief background of events leading up to the creation of the project.
3B Communication PlanThis is an internal project document which needs to be completed in the initiation phase of the Project Management Life Cycle and updated and reviewed throughout the lifecycle of the project. It encourages the project manager to think about who the key information needs to be communicated to and what methods they will use to do this.
4A Project PlanThis document contains details of the strategies and information necessary to execute a project. It is a living umbrella document for the entire set of project controls used to manage the Execution phase of the Project Life Cycle.
4B Project Risk LogWhere applicable it is expected that project managers will enter this information directly into Sentient.This document addresses items which may occur in the future, but have not yet happened. Risks, while they may be mitigated and diminish in exposure, remain throughout the project and never end. This document contains tracking mechanisms, a log and example risk categories to help get you started.
4C Project Issue LogWhere applicable it is expected that project managers will enter this information directly into Sentient.This document is for items which are currently present or have already occurred and must be addressed. Issues should be addressed and completed. This document contains tracking mechanisms and a log.
4D Project Work Breakdown Gantt ChartWhere applicable it is expected that project managers will enter this information directly into Sentient.This document is a diagrammatic representation of the project activities. This document should contain: Major milestones; Deliverables; Key activities; Tasks with assigned staff and associated costs; Timeline.
4E Project Change Request FormThis form is used to request approval of notable, strategic changes in a project from its Steering Committee.
4E Project Change Request LogThis log is used track all project changes requested.
5A Project Status ReportWhere applicable it is expected that project managers will enter this information directly into Sentient.This document is a tool that you will use to communicate with the Sponsor, Stakeholders and SMT to let them know how your project is going and keep everybody informed on a regular basis.
5B Project DiaryThis document is to record all project activities. It is useful as a record of events for decision-making and for reflection during the Post-Implementation Review.
6 Project Final ReportThis document is used to close a project and communicate final project status and outstanding issues to the Sponsor, Stakeholders and the SMT.
7 Project Post Implementation Review (PIR)This document is used to supply information about the outcomes and success of a project. The PIR lists the expected outcomes as specified in the Project Plan, reports on variances from that plan and then asks for recommendations and how they will be used, as well as lessons learned.
