Project Management Plan Template.docx

Project Management Plan TemplateProject Management Plan for Project Name Customer Name Prepared by: Document Author Document Author Title Project Document Id Date Prepared: Date_Prepared Customer Name Project ID No.: Project ID No Document Information Project Name: Prepared By: Title: Reviewed By: Project Name Document Author Document Author Title Document Version No: Document Version Date: Review Date: Version Number Version Date Distribution List From Date Phone/Fax/Email Action* Due Date Phone/Fax/Email To * Action Types: Approve, Review, Inform, File, Action Required, Attend Meeting, Other (please specify) Version History Ver. No. Ver. Date Revised By Description Filename Customer Name Project ID No.: Project ID No Table of Contents Proprietary Notice . 5 Instructions on the Use of this Template . 5 Purpose: . 5 Audience: . 5 TeamPlay Users: . 5 Customer Version: . 5 References: . 6 1. 2. Executive Summary . 7 Introduction . 7 2.1. 2.2. 2.3. 2.4. 2.5. 2.6. 2.7. 2.8. Customers Purpose and Goals . 7 Project Goals and Strategy . 8 Constituent Projects . 8 Critical Success Factors . 8 Key Milestones . 8 Assumptions . 8 Constraints and Dependencies . 8 Definitions . 8 2.8.1. Terms . 8 2.8.2. Abbreviations . 8 3. Scope & WBS . 8 3.1. 3.2. 3.3. 3.4. 4. 5. 4.1. 5.1. 5.2. 6. 6.1. 6.2. 6.3. 6.4. 6.5. Solution Overview . 8 Scope . 8 Project Deliverables . 9 WBS . 9 Activities and Estimates . 9 Project Schedule . 9 Milestone List . 10 Project Organisation Structure . 10 Responsibilities . 10 Material and Supplies Resources. 10 Facilities . 11 Other . 11 Activities and Estimates . 9 Schedule . 9 Resources . 10 Customer Name Project ID No.: Project ID No 7. Communication . 11 7.1. 7.2. 7.3. Stakeholders . 11 Status Meetings . 11 Status Reporting . 11 Risk Identification, Assessment and Risk Responses . 12 Risk Management Plan . 12 Project Tracking and Control . 13 Change Control Process . 13 Customer Acceptance Process . 13 Issue Management and Escalation Process . 13 Warranty . 13 8. Project Risks . 12 8.1. 8.2. 9. Project Processes . 12 9.1. 9.2. 9.3. 9.4. 9.5. 10. Appendices . 13 10.1. Supplemental Plans . 13 10.2. Attachments . 14 Customer Name Project ID No.: Project ID No Proprietary Notice Instructions on the Use of this Template (delete the section when using the template) Purpose: The purpose is to communicate: l Project goals and the means to achieve them l Resources required (time, money, personnel) and of milestones that have been or will be achieved l Assumptions that were made in determining how the project's goals will be met l 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: l Quality Plan l Acceptance Test Plan l Deployment Plan l Configuration Management Plan l Contract and Procurement Plan l Warranty Plan l Support Plan Audience: The primary audience for the Project Management Plan document is HW 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. TeamPlay Users: If you have, or will, produce a Project Data Sheet (PDS), you are not required to complete every section described in this template. TeamPlay users with a PDS must complete the following sections: l Introduction: definitions, terms and abbreviations l Resources -the entire section l Communication - the entire section l Project Processes - entire section Customer Version: Before distributing this Project Management Plan it must be adapted to remove proprietary information. The project manager, together with HW management, must determine what information in the plan is appropriate to give the customer and how best to provide it (e.g., sections 4. Activities Customer Name Project ID No.: Project ID No and Estimates, 6. Resources, and 8. Project Risks are critical to revise and/or remove before distribution). References: Visit the HW Global Method website to see a number of references to aid in project planning, including: l PJM0100G Applying Global Method PM Guide l PJM1100G Integration Management Guide l PJM1300G Issue Management Guide l PJM1400G Change Control Guide l PJM2101G Scope Management Guide l PJM2150G Work Breakdown Structure Guide l PJM3100G Time Management Guide l PJM4100G Cost Management Guide l PJM5100G Quality Management Guide l PJM6100G HR Management Guide l PJM6500G PMO Practices & Procedures Guide l PJM7100G Communications Management Guide l PJM7150G Project Document Management Guide l PJM8100G Risk Management Guide l PJM9100G Procurement Management Guide Customer Name Project ID No.: Project ID No 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 Table 1.1 Project Summary Project Manager Project Sponsor Goals & Objectives Project Scope Project Mgt. Reporting Approach Risk Mgt. Approach Quality Approach Change Mgt. Approach Knowledge Coordination Approach Milestone Estimates Document Author Name of project sponsor Objective #1 Objective #2 Description of project scope A Description (ex., a monthly summary report, which includes key milestones and critical management issues will be sent to xyz during the first week of each month . . . ) Description of risk management approach Description of quality approach Description of change management approach Description of knowledge coordination approach Milestones Plan Key Milestone #1 Key Milestone #2 Staffing Approach ?/?/20? ?/?/20? Brief explanation of staffing 2. 2.1. Introduction Customers Purpose and Goals Briefly describe the customers business needs and problems, explain what the purpose of the project is from a customer perspective. Table 2.1 Triggering Problems/Opportunities: Supporting Objectives Obj. # (Triggers) 1 ( ) 2 ( ) 3 ( ) 4 ( ) Description The Project is complete when. Performance Measure Target Customer Name Project ID No.: Project ID No Supporting Objectives 2.2. Project Goals and Strategy Describe the project goals, and how they will be met for example, through a turnkey solution, a partnership with the customer, or integration with third-party solutions. Describe how this project is aligned with / impacts the strategy for the account. 2.3. Constituent Projects List constituent projects of this project/program. Identify project managers both for HW and third party projects. Cover customer managed project when appropriate. 2.4. 2.5. 2.6. 2.7. Critical Success Factors Key Milestones Assumptions Constraints and Dependencies Describe the items that need to be in place for the project to be successful. Summarise from the milestone table in section 5.2 List the assumptions on which the HW solution has been built. Describe the limitations and external dependencies that could impact the success of the project. Describe the interfaces to organisations external to the project that are essential to its success. 2.8. 2.8.1. 2.8.2. Definitions Terms Abbreviations Describe any terms, acronyms and abbreviations required to understand this document. 3. 3.1. 3.2. Scope & WBS Solution Overview Scope Provide a high-level description of HW's solution