GREEN EXPERT TECHNOLOGY INC.
Project Management Plan
Project Name
Bruce Green
7/14/13/2013
© Green Expert Technology Inc. 2013
TABLE OF CONTENTS
1.
Introduction ..................................................................................................................................................................... 2
2.
Project Goal ...................................................................................................................................................................... 2
3.
Major Milestones ............................................................................................................................................................ 2
4.
Project Team .................................................................................................................................................................... 2
5.
Assumptions & Constraints ....................................................................................................................................... 3
6.
Development Approach and Detailed Plans ....................................................................................................... 3
7.
6.1
List of Associated Planning Documents ...................................................................................................... 3
6.2
Project Statement of Work ............................................................................................................................... 3
6.3
Project Scope .......................................................................................................................................................... 4
6.4
Integrated Change Management Plan .......................................................................................................... 4
6.5
Issues/Action Item Tracking System ........................................................................................................... 4
6.6
Communications Management Plan ............................................................................................................. 4
6.7
Risk Management Plan....................................................................................................................................... 4
6.8
Schedule ................................................................................................................................................................... 5
6.9
Quality Assurance ................................................................................................................................................ 5
6.10
Vendor Management........................................................................................................................................... 5
Project Closure Plan ...................................................................................................................................................... 5
1
1. INTRODUCTION
Insert a short description of the project and the following statement: This document defines how
the Project will be executed, monitored, and controlled. Detailed subsidiary plans are referenced in
this document.
It is recommended that the introduction paragraphs in the Project Management Plan, Project
Scope document, Requirements, and other project documents contain identical descriptions of the
project. That will ensure clarity and consistency while also allowing basic project information to be
found in every major document – so that someone using the document does not have to search to find
basic answers.
2. PROJECT GOAL
Concisely state the project goals and how they will be achieved.
Example goal: Construct a solar power generation field for the ABC data center in Cherry Hill, NJ.
Example of how: Solar field will be developed in conjunction with two prime vendors: SolarTown Inc. –
who will provide the power generation and distribution – and XYZ Construction.
3. MAJOR MILESTONES
Major milestones and project tasks are described in the Work Breakdown Structure (WBS)
document as well as in the project schedule. These documents are updated and reviewed during
weekly status meetings. The table below provides a list of major milestones with dates that are
subject to change. Examples are provided in the table below.
Milestone
Date
Kickoff Meeting
Preliminary Design Review
Final Design Review
Prototype Testing
Acceptance Testing
Installation Begins
Final Testing & Approval
Project Lessons Learned Meeting
4. PROJECT TEAM
Provide a list of the key project resources and their roles. Example roles are provided in the table
below.
Role
Project Owner
Name(s)
Contact Info
2
Project Manager
Technical Team
Vendor Team Manager
5. ASSUMPTIONS & CONSTRAINTS
This table lists the key assumptions that the project plan relies on. An example is: The X Project will be
complete prior to construction to enable use of the thingamabob.
Assumption
Description
This table lists the important constraints that the project must deal with. An example is: Operating
System – The data center will be entirely run on LINUX OS.
Constraint Type
Description
6. DEVELOPMENT APPROACH AND DETAILED PLANS
6.1
LIST OF ASSOCIATED PLANNING DOCUMENTS
Document
Project Scope
Project Management Plan
Work Breakdown Structure
Project Schedule
Change Request
Status Meeting Minutes
Risks and Changes Register
Action Items Log
Communication Plan
Quality Assurance Plan
Vendor Management Plan
Format
File Name
MS Word
MS Word
MS Excel
PDF
MS Word
MS Word
MS Excel
MS Excel
MS PPT
MS Word
MS Word
6.2
PROJECT STATEMENT OF WORK
Specific description of work to be accomplished.
3
The associated work breakdown structure for this project is described in the MS Word
document titled “Project WBS”.
6.3
PROJECT SCOPE
A short description of the scope of the project.
The project scope is fully described in the MS Word document “Project Scope.”
6.4
INTEGRATED CHANGE MANAGEMENT PLAN
A formal change request process will be required to change any approved documents. Change
Control Board will be managed by __________. The change control board agrees to vote on all change
requests within 2 working days of receipt. Voting may be via email, meeting, or conference call.
6.5
ISSUES/ACTION ITEM TRACKING SYSTEM
Issues will be tracked in the project checklist and reviewed at every weekly status meeting. Project
checklist will be accessible for viewing by all on shared site. Items will be opened / closed at weekly
meetings. The format of the Issues/Action Item Tracking is provided in the table below.
ID
Description
6.6
Owner
Date Open ECD
Status
COMMUNICATIONS MANAGEMENT PLAN
The Communications Management Plan is a Word document that provides the entire
communications plan for the project. This includes a communications requirements analysis,
communications plan, and email templates.
6.7
RISK MANAGEMENT PLAN
A Risk Register will be completed and maintained throughout the project life and be available
for viewing on a shared site. Changes to the Risk Register will not require Change Request but will
be agreed upon during weekly status meetings.
The format of the risk register is as follows.
Risk
ID
Description
Family
Impact
(1=Low to
5=High)
Probability
(1=Low to
5=High)
Risk
Rating
Mitigation
4
6.8
SCHEDULE
The detailed schedule and Gantt chart will be maintained and available for viewing. The initial
schedule will be discussed during the analysis phase and finalized at the end of analysis as a
deliverable. Major changes to schedule will be brought to the Change Control Board for approval.
6.9
QUALITY ASSURANCE
Quality assurance plan designates the quality gates, audits, approvals, and test cycles that will be
enforced for the project. The detailed quality assurance plan is provided in the MS Word document
titled QA Plan.
6.10 VENDOR MANAGEMENT
Vendor management plan details how _________ will work with major vendors to ensure that our
schedules, tasks, and goals remain aligned. Vendor Management Plan describes how the team will
execute their project plan while also interfacing and staying aligned. The detailed vendor
management plan is provided in the MS Word document titled Vendor Management Plan.
7. PROJECT CLOSURE PLAN
A project audit will be conducted at ________ to review status of all deliverables and turnover of
operations. At the project audit outstanding actions and issues will be reviewed. Funding status will
be reviewed. Next steps or requirements for sustainment will be discussed. A closing report will be
issued in the form of a final status report.
5