Check back soon for more information.
| Project Initiation |
Brief Template Explanation |
OIT | Tier I |
Tier II |
|---|---|---|---|---|
| Project Request Form |
A vehicle to begin the process for requesting a project. |
M | M | M |
| Sponsor Brochure |
This tri-fold color brochure explains the role of the Project Sponsor during each phase of the project. Use it to encourage a constructive level of Sponsor participation. |
M | M | |
| Stakeholder Registry & Communication Plan |
A vehicle to record critical stakeholder information. Provides a basis for management's expectations and communication. |
S | M | M |
| Project Charter lite |
This document is used to present project information to the Governance Committee. It asks exactly the right questions for any project. Can serve as a companion document to the Project Evaluation Tool. |
M | M | M |
| Quick IT Project Risk Evaluator |
Easy to use tool asks 25 multiple choice questions that provide a surprisingly effective risk evaluation for any Information Technology project. Fully customizable; questions can be changed for any knowledge domain. Risk summary can be printed separately from the questionnaire. |
M | M | |
| Procurement Plan |
Details how the Project Team will go about acquiring significant goods and services required for the project but only available from outside organizations (e.g., RFI and RFP processes) |
AN | AN | AN |
| Preliminary Project Cost Estimator |
Simple tool for developing an early estimate of project cost. |
S | S | S |
| Project Charter Budget Worksheet |
A Budget worksheet for IT projects designed to help the Charter team develop a reasonable accurate Project Cost Estimate. Includes Operational and capital costs. |
M | M | |
| Project Charter Form Milestones |
Schedule Addendum for the Project Charter. Use this to record information about project phases, milestones, phase reviews and project completion criteria. |
S | M | |
| Project Charter Selection Criteria Addendum |
This document prompts for information which will be used to compare projects during the project selection process. Can serve as a companion document to the Project Evaluation Tool. |
M | M | |
| Cost Benefit Analysis |
A vehicle in which to document the pros and cons of various project approaches and why the current approach was selected. |
S | S | S |
| Project Evaluation Tool |
A project scoring model assists in Project Selection and Prioritization. Selection parameters deliver quantitative data that result in a numeric score for each project. Considers strategic alignment, risk, benefit, cost and more. Includes project categorization and a summary table of all project scores. This form is used by the Project Team and the results will be presented to the ITRG and ITGC. |
M | M | |
| Phase Exit Plan |
Details all requirements that must be met before the Project Team can exit one project phase or begin the next. Can serve as teh basis for end-of-phase project reviews. |
M | M |
| Analysis Phase |
Brief Template Explanation |
OIT | Tier I |
Tier II |
|---|---|---|---|---|
| Project Change Control Plan |
Describes the process through which changes may be introduced into the project. Best Practice: Get this document signed by the Project Sponsor early in Planning and use it to control the high level scope definition found in the Project Charter. Later, use the same process to protect the integrity of your project scope baselin3. |
S | M | |
| Project Change Request Form |
Used by any stakeholder to request a change in the project. When it applies to scope, budget, schedule, quality, risk or Business Value, a formal Change Control Process is invoked. Change Requests are reviewed during regular project meetings. This form provides a much easier document for stakeholders, and supports more complete analysis by the project team. |
M | M | |
| Project Change Request Log |
Summarizes all project change Requests and their status, and supports tracking of changes to project baselines. |
S | M | M |
| Scope Statement Lite |
Describes all of the work - and only the work - required to complete the project. |
M | M | |
| Requirements Management Plan |
Describes all of the work - and only the work - required to complete the project. Update provides a more complete understanding of scope in a simple format |
BA | BA | |
| Commitments Agreement |
This form is used when your project requires either:
|
M | M | |
| Responsibility Assignment Matrix (TAM) |
A chart that displays who, in which role, is responsible for which tasks. A tool for keeping stakeholders on task. |
S | S | |
| Procurement Plan | Details how the Project Team will go about acquiring significant goods and services required for the project but only available from outside organizations (e.g., RFI and RFP processes) |
AN | AN | AN |
| Risk Management Plan |
Explains how the Project Team will identify, quantify, prioritize, and manage project risks. Updated to most recent Risk Management terminology and a tighter fit with the Risk Register |
S | S | |
| Risk Assessment Questionnaire |
Used by the Quality Organization (or Project Team) to determine the degree of risk in a project. |
S | S | |
| Risk Identification Tool |
Use this tool to harness the insights of your project team and stakeholders. Combines the features of SWOT Analysis (Strengths - Weaknesses - Opportunities - Threats). Start with general sources of risk and drive down to specifics. |
S | M | |
| Issue Document |
Used by any stakeholder to report an issue in the project. |
M | M | |
| Issue Log |
Summarizes all project Issues and their status. Open issues are reviewed at every regular project meeting. |
S | M | M |
| Meeting Minutes |
A convenient format for recording minutes from Project team and other meetings. |
M | M | M |
| Design Phase |
Brief Template Explanation |
OIT | Tier I |
Tier II |
|---|---|---|---|---|
| BA Productivity Pack |
Six Templates in one Excel file. Fully BABOK® compatible:
|
BA | BA | |
| BA Tool Kit |
Seven Templates in one Excel file. Fully BABOK® compatible:
|
BA | BA | |
| USE Case |
Used to document functional requirements of the project that can be expressed as Use Case Scenarios. The Use Case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal. Fully BABOK® compatible. |
BA | BA | |
| Requirements Resource Plan |
Details all of the goods, services and personnel required by the Business Analysis Team Lead (including when they are needed and the projected cost). Fully BABOK® compatible. |
BA | BA | |
| Project Requirements Document |
a.k.a. Business Requirements Document (BRD), this template promotes the best practice of complete documentation of project requirements. Supports a wide array of requirements types, including Business, Functional, Technical, User, Process and more. |
M | M | |
| Issue Log |
Summarizes all project Issues and their status. Open issues are reviewed at every regular project meeting. |
S | M | M |
| Execution and Control |
Brief Template Explanation |
OIT | Tier I |
Tier II |
|---|---|---|---|---|
| Vendor Product Presentation Rating Form |
Allows a group to quantify and summarize their ratings of presentations done by multiple vendors |
AN | AN | |
| Vendor Proposal Rating Form |
Allows a group to quantify and summarize their ratings of proposals provided by multiple vendors. |
AN | AN | |
| Consultant Evaluation Summary |
Allows a group to summarize their findings when evaluation consultants or vendors |
AN | AN | |
| Project Status Presentation (PPT) |
Allows a group to summarize their findings when evaluating consultants or vendors. This template is great in project review meetings. The format is simple and direct, focusing on objectively measurable results and exceptions to plan. This format supports "Reporting by Exception" where every project report is limited to five minutes. |
S | S | |
| Status Report |
Used to report project status. Provides a consistent format, including an Executive Summary section, for enhanced communication with upper management. |
S | M |
| Project Close |
Brief Template Explanation |
OIT | Tier I |
Tier II |
|---|---|---|---|---|
| Lessons Learned Checklist |
Checklist format provides an easy means of documenting Lessons Learned throughout the project. |
S | S | S |
| Lessons Learned Document |
Record commentary regarding Lessons Learned throughout the project in this form. Provides categories of project work to encourage group discussion. |
S | S | S |
| Project Close Report |
Create this report at the very end of the project when all other work has been completed. The information provided on this template will allow management to evaluate project outcome. When this report is signed off, the project is officially closed. |
M | M | M |