【正文】 ivery of the agreed project outputs. The subheadings under section ( – ) may not be required if the above content is adequately covered in the Project Business Plan. Introduction This section expands the operational management of the XYZ Project, as defined within the Project Business Plan. SubProject Management Define the operational management of the sub projects if this has not already been defined within the Project Business Plan. Reference Groups Detail any specific reference groups (. function, objectives, membership etc) that are required and have not been defined in the Project Business Plan. 錯誤 !使用“開始”選項(xiàng)卡將 Heading 1 應(yīng)用于要在此處顯示的文字。 Project Title: Project Execution Plan – Version Page 1 of 24 1 Introduction Document Purpose Depending on the size and plexity of the project, the need for multiple Project Execution Plans (PEPs) for the Project may arise. Examples include where separate Project Teams are developing specific outputs for different business areas (. as subprojects). The Project Execution Plan (PEP) is the operational document for the project. It is owned, maintained and utilised by the Project Manager and Project Team to support the delivery of the agreed project outputs. The PEP is the responsibility of the Project Manager and is the ‘road map’ enabling the effective daytoday (operational) management and control of the project. The PEP expands on the Project Business Plan which is the approved plan describing ‘what’ will happen in the project. The PEP details ‘how’ the Project Team will carry out their tasks/activities to ensure that the ‘what’ will occur. The document provides new Project Team members, or a new Project Manager with the ability to start during a project, and continue to perform the project’s activities in a consistent manner. The document should be reviewed and amended to meet changed conditions during the project’s life span. Intended Audience Clearly identify the intended audience of this document, as it may include key representatives from the business area(s), and other stakeholders who will be impacted by the planned outputs. State any assumptions regarding the document up front that may assist the reader, for example: ? Knowledge of the project and a basic understanding of project management principles and practices is assumed。 and ? gain acceptance by the Project Sponsor or Proposer to the suitability of these activities. What you need before you start: ? Agreement to proceed with the development of the Project Execution Plan from the Project Sponsor or Proposer. ? Knowledge and understanding of developing detailed project plans, quality plans, implementation and delivery plans, resource scheduling, risk management planning and financial planning. ? Knowledge and understanding of the Key Elements, as outlined in the Tasmanian Government Project Management Guidelines. 1 For a definition of these underlined terms, refer to the Project Management Glossary. Department of Premier and Cabi, Tasmania 3 Optional: ? Any of the following documents Strategic Information Systems Plan, Project Proposal/Brief, Process Review Report or Feasibility Study. ? Departmental Project Management Guidelines. What you will have when you are finished: A pleted Project Execution Plan that is ready for acceptance by the Project Sponsor or Proposer. How to use this template? The template contains sections which are either optional or can be developed at a number of levels of detail depending upon individual need. Sections that are not pleted can be indicated in a number of alternative methods depending on the reason for nonpletion, for example by referring to another document, by deleting the heading, or by indicating that the section is not applicable. All documents developed based on this template should include an appropriate acknowledgement. A number of different text styles have been used within the template, as follows: ? Text in italics is intended to provide a guide as to the kind of information that can be included in a section and to what types of projects it might be applicable. ? Text in normal font is intended as examples. ? Text enclosed in angle brackets is intended to be replaced by whatever it is describing. Copy: Uncontrolled (PM 005 Version 14 December 2021) Project Title Project Execution Plan Organisational Unit DEPARTMENT OF … Version (dd mmm yyyy) Project Title: Project Execution Plan – Version Page i of v DOCUMENT ACCEPTANCE and RELEASE NOTICE This is release/version of the Project Title Project Execution Plan. The Project Execution Plan is a managed document. For identification of amendments each page contains a release number and a page number. Changes will only be issued as plete replacement. Recipients should remove superseded versions from circulation. This document is authorised for release once all signatures have been obtained. PREPARED: DATE:___/___/___ (for acceptance) (Name, Project Title Project Manager) ACCEPTED: DATE:___/___/___ (for release) (Project Sponsor, Name, Title) Project Title: Project Execution Plan – Version Page ii of v 1. BUILD STATUS: The most recent amendment first. Version Date Author Reason Sections dd mmm yyyy Name . Initial Release All 2. AMENDMENTS IN THIS RELEASE: Section Title Section Number Amendment Summary . This is the first release of this document. 3. DISTRIBUTION: Copy No Version Issue Date Issued To 1 dd mmm yyyy Name, Title, Organisation 2 Electronic Project Title: Project Execution Plan – Version Page iii of v Table of Contents 1 Introduction ....................................................