Professional Documents
Culture Documents
Bhd.
Prepared by:
[Project manager name]
Project Manager
[Client logo]
Document Information
Project Name:
Project Manager:
Customer / Client:
Document Version
Date:
Document By:
DD/MM/YYYY
BIT
Prepared By:
Preparation Date:
DD/MM/YYYY
Reviewed By:
Review Date:
DD/MM/YYYY
Distribution List
From
To
Action*
Date
Phone/Fax
Due Date
Phone/Fax
* Action Types: Approve, Review, Inform, File, Action Required, Attend Meeting, Other (please specify)
Version History
Ver. No.
Ver. Date
Revised By
Description
Filename
Page 1 of 16
141151323.doc
[Project name]
[Client logo]
Table of Contents
[Client logo].......................................................................................................... 2
Proprietary Notice.................................................................................................4
Instructions on the Use of this Template (delete the section when using the
template)................................................................................................................ 4
Purpose:.................................................................................................................................. 4
Audience:................................................................................................................................ 4
Customer Version:.................................................................................................................. 4
1. Executive Summary.............................................................................................5
2. Introduction........................................................................................................ 6
2.1. Customers Purpose and Goals ........................................................................................6
2.2. Project Goals and Strategy................................................................................................6
2.3. Constituent Projects.......................................................................................................... 6
2.4. Critical Success Factors..................................................................................................... 6
2.5. Key Milestones.................................................................................................................. 6
2.6. Assumptions..................................................................................................................... 6
2.7. Constraints and Dependencies..........................................................................................6
2.8. Definitions ........................................................................................................................ 6
2.8.1. Terms............................................................................................................................ 6
2.8.2. Abbreviations................................................................................................................. 6
3. Scope & WBS...................................................................................................... 7
3.1. Solution Overview............................................................................................................. 7
3.2. Scope................................................................................................................................ 7
3.3. Project Deliverables.......................................................................................................... 7
3.4. WBS.................................................................................................................................. 7
4. Activities and Estimates......................................................................................8
4.1. Activities and Estimates.................................................................................................... 8
5. Schedule............................................................................................................ 9
5.1. Project Schedule............................................................................................................... 9
5.2. Milestone List.................................................................................................................... 9
6. Resources......................................................................................................... 10
6.1. Project Organisation Structure........................................................................................ 10
6.2. Responsibilities............................................................................................................... 10
6.3. Material and Supplies Resources.....................................................................................10
6.4. Facilities.......................................................................................................................... 10
6.5. Other............................................................................................................................... 10
7. Communication................................................................................................. 11
Business Information Technology (M) Sdn.
Bhd.
Project Management Plan
[Client name]
Page 2 of 16
141151323.doc
[Project name]
[Client logo]
7.1. Stakeholders................................................................................................................... 11
7.2. Status Meetings.............................................................................................................. 11
7.3. Status Reporting............................................................................................................. 11
8. Project Risks .................................................................................................... 12
8.1. Risk Identification, Assessment and Risk Responses.......................................................12
8.2. Risk Management Plan.................................................................................................... 12
9. Project Processes.............................................................................................. 13
9.1. Project Tracking and Control........................................................................................... 13
9.2. Change Control Process.................................................................................................. 13
9.3. Customer Acceptance Process........................................................................................ 13
9.4. Issue Management and Escalation Process.....................................................................13
9.5. Warranty......................................................................................................................... 13
10. Appendices..................................................................................................... 14
10.1. Attachments ................................................................................................................. 14
Page 3 of 16
141151323.doc
[Project name]
[Client logo]
Proprietary Notice
[Insert the appropriate legal text for restrictions, use and disclosure.]
the template)
Purpose:
The purpose is to communicate:
Project goals and the means to achieve them
Resources required (time, money, personnel) and of milestones that have been or will be
achieved
Assumptions that were made in determining how the project's goals will be met
Project risks as well as the associated risk response plans
The template provides the structure for the central parts of most projects, however more plans
may be needed depending on the specific project requirements. The project manager must
exercise sound business judgment to determine whether the template has the adequate sections
or not. If not, the project manager decides whether to include more sections in the template or to
develop separate plans.
The template does not include sections for:
Quality Plan
Acceptance Test Plan
Deployment Plan
Configuration Management Plan
Contract and Procurement Plan
Warranty Plan
Support Plan
Audience:
The primary audience for the Project Management Plan document is BIT management, who
approves the plan.
An adapted version of this Project Management Plan may also be shared with the customer
because, for the solution to be a success, the customer must "buy into" the plan for producing it.
Finally, a completed Project Management Plan may be used as a reference document by project
teams and project managers involved in related or similar efforts.
Customer Version:
Before distributing this Project Management Plan it must be adapted to remove proprietary
information. The project manager, together with BIT management, must determine what
information in the plan is appropriate to give the customer and how best to provide it. E.g. the
sections 4. Activities and Estimates, 6. Resources, and 8. Project Risks are critical to revise and/or
remove before distribution.
Page 4 of 16
141151323.doc
[Project name]
[Client logo]
1. Executive Summary
[At a minimum, include:
The project name
The customer name
All locations involved
A brief project history
A description of the project
A description of the solution to be delivered
Any other information relevant to the project]
Page 5 of 16
141151323.doc
[Project name]
[Client logo]
2. Introduction
2.1. Customers Purpose and Goals
[Briefly describe the customers business needs and problems, explain what the purpose of the
project is from a customer perspective.]
2.6. Assumptions
[List the assumptions on which the BIT solution has been built.]
2.8. Definitions
[Describe any terms, acronyms and abbreviations required to understand this document.]
2.8.1.
Terms
2.8.2.
Abbreviations
Page 6 of 16
141151323.doc
[Project name]
[Client logo]
3.2. Scope
[Provide a statement that describes the limits of the project (describe the what, the who, the
where, and the quality criteria of the project). Document what the project will not address.]
Deliverable Name
3.4. WBS
[Provide a graphical or tabular overview of the projects WBS, or refer to the document where the
WBS can be found.]
Page 7 of 16
141151323.doc
[Project name]
[Client logo]
Activity Description
Resources/Skills
Required
Estimate
d Effort
Responsible
Person
Page 8 of 16
141151323.doc
[Project name]
[Client logo]
5. Schedule
5.1. Project Schedule
[Include a high-level schedule for the major deliverables listed in the Work Breakdown Structure
(WBS). For each primary deliverable, include duration, start date and end date. Or if a Microsoft
Project schedule has been created, a high-level (collapsed) version can be pasted into this
section; however, do not paste in the detailed Microsoft Project Gantt Chart.]
Table 5.1 Schedule Summary
Project Deliverable
Planned
Start Date
Planned
End Date
Actual
Start Date
Actual End
Date
Milestone Name
Planned
Completion
Date
Actual
Completion
Date
Page 9 of 16
141151323.doc
[Project name]
[Client logo]
6. Resources
6.1. Project Organisation Structure
[Insert organisational chart]
6.2. Responsibilities
[Define the responsibilities for each resource on the organisation chart ---- BIT, the customer, and
all internal and external participants.]
Table 6.2. Project Responsibilities
Name
Role
Responsibility
Organisation
Person-Days
Allocated
[List the internal BIT resources that are indirectly involved in the project (account manager,
financial analyst, legal support, etc.)]
Table 6.3 BIT Internal Management & Supporting Responsibilities
Name
Role
Responsibility
Organisation
6.4. Facilities
[Describe the requirements for workspace, office space, or any special facility requirement.]
6.5. Other
Page 10 of 16
141151323.doc
[Project name]
[Client logo]
7. Communication
7.1. Stakeholders
[Provide list of stakeholders contact information. List all individuals who are directly and
indirectly involved with the project.]
Table 7.1 Stakeholders
Name
Role
Phone
Participants
Frequency
Author
Recipients
Frequency
Page 11 of 16
141151323.doc
[Project name]
[Client logo]
8. Project Risks
8.1. Risk Identification, Assessment and Risk Responses
[List the risks that have been prioritised, provide a brief description of the impact of the risk if it
occurs. List the risk response strategy that has been chosen for each risk (Avoidance,
Transference, Mitigation, or Acceptance), and attach the latest copies of the Risk Response Plan.]
Table 8.1 Project Risk Overview
Risk Title
Risk Response
Strategy
Page 12 of 16
141151323.doc
[Project name]
[Client logo]
9. Project Processes
9.1. Project Tracking and Control
[Describe the project tracking and control processes e.g. for cost, scope, schedule. Refer to
section 7.2 Status Meeting and 7.3 Status Reporting as appropriate.]
9.5. Warranty
[Describe the approach to provide warranty for the projects products and or services. Describe
any warranty processes. Identify and estimate the resources required to provide warranty
services.]
Page 13 of 16
141151323.doc
[Project name]
[Client logo]
10. Appendices
10.1. Attachments
[List all attachments and reference documents here.]
Table 10.1 Attachments and References
Document Name
File Name(s) /
Appendix Name
Attached
(yes/no)
Page 14 of 16
141151323.doc
[Project name]