|
|
|
|
 |
|
|
Project Plan Template
(27 pages).
What is it?
The Project Plan identifies the lifecycle and visibility tools the project will
use. It also describes the organization plan, risk plan, test plan,
documentation plan, review plan, installation plan etc.
Who uses it?
Development Manager, Project Manager, IT Manager, System Administrator, Test
Manager, Documentation Manager.
When is it used?
The Project Plan is used to guide both project execution and project control,
document planning assumptions and decisions, facilitate communication among
project stakeholders, and document approved scope, cost, and schedule baselines.
The project plan is used in analyzing the feasibility of the project and in
guiding the effort. Project Planning involves the following: developing the
project plan; interacting with stakeholders appropriately; getting commitment to
the plan; maintaining the plan.
|
Table of Contents
1 Introduction
1.1 Purpose of this document
1.2 Document Overview
1.3 Deliverables
1.4 Scope
1.5 Reference Materials
1.6 Relationship to Other Plans
1.7 Key Stakeholders
1.8 Points of Contact
1.9 Methodology, Tools, and Techniques
1.10 Policies, Directives and Procedures |
5 Work Packages,
Schedules and Budget
5.1 Work Packages
5.2 Dependencies
5.3 Resource Requirements
5.4 Budget Requirements
5.5 Budget Allocation
5.6 Resource Allocation
5.7 Master Schedule
5.8 Schedule |
2 Management
Structure
2.1 Project Lifecycle
2.2 Project Organization
2.3 Roles and Responsibilities
2.4 Resource Loading Chart
2.5 Problem Escalation
2.6 Reporting
2.6.1 Status Reports
2.6.2 Weekly
2.6.3 Monthly
2.7 Risk Management
2.8 Assumptions
2.9 Constraints
2.10 Acquisition Plan
2.11 Communication Plan
2.12 Startup
2.13 Closeout
2.14 Sign-Off Criteria |
6 Project Success
Criteria
6.1 Project Milestones
6.2 Approval Process
6.3 Acceptance Criteria
6.4 Critical Success Factors
|
3 Planning and
Control
3.1 Estimate
3.1.1 Estimation Process
3.2 Resource Identification
3.2.1 Staff
3.2.2 Time
3.2.3 Cost
3.2.4 Materials
3.3 Resource Allocation
3.3.1 Work Breakdown Structure
3.3.2 Schedule(s)
3.3.3 Budget
3.4 Tracking and Control |
7 Supporting Plans
7.1 Configuration Management Plan
7.2 Quality Assurance Plan
7.3 Testing Plan
7.4 Deployment Plan
7.5 Integration Plan
7.6 Procurement Plan
7.7 Operations Plan
7.8 Maintenance Plan
7.9 Staff Development Plan
7.10 Product Acceptance Plan |
4 Technical
Process
4.1 Engineering
4.1.1 Environment
4.1.2 Methods, Tools and Techniques
4.2 Technology
4.2.1 Environment
4.2.2 Methods, Tools, and Techniques
4.3 Infrastructure
4.4 Project Artifacts |
8 Appendix —
Glossary of Terms
8.1 Glossary of Terms
8.2 Acronyms and Abbreviations
|
Index of Tables
Table 1 — Deliverables
Table 2 — Roles and Responsibilities
Table 3 — Resource Loading Chart
Table 4 — Risks
Table 5 — Assumptions
Table 6 — Constraints |
Table 7 — Sign-off Criteria
Table 8 — Dependencies
Table 9 — Master Schedule
Table 10 — Milestones
Table 11 — Glossary of Terms
Table 12 — Acronyms and Abbreviations |
|
|
|
|
|
|
|
 |
|
