Project Resources and Templates
All projects for Information Technology are formally requested using a proposal form. Projects are reviewed by IT Tech/OP Leadership.
Conducting a Lessons Learned meeting after the project is complete can be a powerful tool for improving the execution of projects. This agenda can be used as a starting point for that meeting.
A PIER report documents the history and outcome of a project and is used to build a repository of what works well and what doesn't in the organization.
The Program Charter is to consolidate information, like a master project, across a program that will encompass several smaller projects. Individual projects should use the Project Charter Template.
The Project Charter documents the scope of the project and identifies all of the key stakeholders. It is normally created when a project is first conceptualized and can be used to document known issues or risks.
A form used to request a change to the scope of a project.
A simple one page PowerPoint report that communicates the status of a project. The report includes sections that cover project scope, activities, schedule, budget, issues and risks. The Project Manager coordinates with the Project Owner to determine how often the project status should be reported.
A worksheet used with large projects to identify the type of risk, and the level of risk associated with successfully completing a project.
A template used by the project team to confirm they have considered all aspects of launching a new service. When the project is completed, and the service is launched, this document is used as a reference for supporting the service. There is also a Service Handbook for Vendor Hosted Services.
A template used to document all requirements for a software development project.
The Start Up Checklist is used for large projects to determine if the team is ready to begin the full implementation phase of the project.
This vendor questionnaire needs to be completed when discussions begin with hardware or software vendors.
A Work-Breakdown Structure (WBS) lists all the activities that are needed to complete a project, and specifies when they should be completed. This template is used to help organize projects and to ensure that some standard activities, including Service Design and Release Management, are not being overlooked.