Project Management Plan Template Page 6
ADVERTISEMENT
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
Project Charter
The project charter follows the project summary information. Like the project
summary, the project charter information was developed during the project
conception and definition phase and includes a business problem, statement of
work, objective, success factors, project dependencies, and constraints. In the
plan template, this information is contained on two pages or in the following
two figures. A sample of the completed information from the template is shown
below.
2. Project Charter(Sample
)
B.
Project Charter:
Business Problem.
All projects start with a business problem/issue to solve.
Sample
The lack of a statewide automated planning system for scheduling transportation road repair maintenance resources has
resulted in road closures, duplicated capital expenditures, and increased staff overtime costs.
Statement of Work (Goal).
The statement should be short and to the point. It should not contain language or terminology that might not be understood.
Sample
Design and prototype an automated, dynamic planning system by Q4, 1997, based on an SQL database and GUI front end.
Based on the prototype, pilot the system and complete full implementation by Q4, 1998.
Project Objectives:
Provide a brief, concise list of what the project is to accomplish.
The project objectives are a detailed version of the statement of work. Taken with the statement of work, the objectives
define the boundaries (scope) of the project. The objective statement can also be seen as a decomposition of the statement
of work into a set of necessary and sufficient objective statements, including:
Outcome - Be specific in targeting an objective
Measurement- Establish a measurable indicator(s) of the progress
Ownership - Make the object assignable to a person for completion
Timeframe - State what can realistically be done with available resources
Sample
1.
Define the planning requirements for the system by Q2, 1997
2.
Define user needs in terms of inputs and outputs by Q2, 1997
3.
Conduct user and stakeholder meetings during Q1 and Q2, 1997
4.
Develop the prototype and test, with a completion date of Q4, 1997
5.
Conduct the pilot of system with completion by Q2, 1998, with the pilot lasting at least three months
6.
Complete system acceptance and user documentation by Q3, 1998
7.
Complete system installation at all locations by Q4, 1998
Project Management Methodology
PM Planning
Project Plan Format
Page 6
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Business