【正文】 PM 005 Project Execution PlanTemplate amp。 GuideThis Guide is intended to be read in conjunction with the following template for the development of a Project Execution Plan. As such the Guide should be removed from the front of your final document.Version (14 December 2000)What is a Project Execution Plan?The Project Execution Plan is the ‘road map’ used by the Project Team to deliver the agreed project outputs. It outlines the responsibilities of the Project Team and key stakeholders.Why would you develop a Project Execution Plan?A Project Execution Plan is developed to expand on the Project Business Plan by specifying the daytoday (operational) management procedures and control plans including: detailed project plans。 resource schedules。 quality procedures。 reporting procedures。 product purchasing and development plans。 risk management planning。 and project budgets.The document enables those pleting the tasks/activities in the project to deliver the expected results, as per the agreed Project Business Plan.When would you develop a Project Execution Plan?Approval to proceed to develop a Project Execution Plan is usually obtained from the acceptance or approval of a preceding stage such as a Project Proposal/Brief For a definition of these underlined terms, refer to the Project Management Glossary. or Project Business Plan. The Project Execution Plan expands the proposals developed in these documents in order to: document the daytoday (operational) management and control activities to be undertaken by the Project Team。 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.Optional:167。 Any of the following documents Strategic Information Systems Plan, Project Proposal/Brief, Process Review Report or Feasibility Study.167。 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:167。 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.167。 Text in normal font is intended as examples.167。 Text enclosed in angle brackets is intended to be replaced by whatever it is describing.Department of Premier and Cabinet, Tasmania 3Project TitleProject Execution PlanOrganisational UnitDEPARTMENT OF …Version (dd mmm yyyy)Project Title: Project Execution Plan – Version Page ii of viDOCUMENT ACCEPTANCE and RELEASE NOTICEThis 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)1. BUILD STATUS:The most recent amendment first.VersionDateAuthorReasonSectionsdd mmm yyyyName. Initial ReleaseAll2. AMENDMENTS IN THIS RELEASE:Section TitleSection NumberAmendment Summary. This is the first release of this document.3. DISTRIBUTION:Copy NoVersionIssue DateIssued To1dd mmm yyyyName, Title, Organisation2ElectronicTable of Contents1 Introduction 1 Document Purpose 1 Intended Audience 1 Project Outputs 1 Scope of Work 22 Management Plan 2 Management 2 Status Reporting 3 Risk Management 4 Provision of Facilities and Equipment 5 Skills and Resource Requirements 5 Configuration Management 6 Confidentiality 7 Output Review and Acceptance 7 Updating this Plan 73 Quality Plan 9 Introduction 9 Methodologies and Standards 9 Development Environment 10 Inspection, Measuring and Test Equipment 10 Development Cycle 10 Outputs to be Developed 10 Project Evaluation 11 Records 114 Purchasing Plan 12 Purchasing Specification 12 Selection of Suppliers 13 Subcontractor Management 13 Inspection and Testing of Purchased Goods amp。 Services 13 Records Required 145 Development Plan 14 Design and Development Activities 14 Organisation and Staffing 15 Design Methodology 15 Design Input 15 Design Output 15 Inspection and Review 15 Approval and Acceptance 16 Authorisation and Distribution 16 Updating and Changing 166 Test Plan 17 Introduction 17 Unit Testing 17 System and Integration Testing 17 Acceptance Testing 18 Certification of Test Results 187 Implementation and Delivery Plan 19 Implementation 19 Handling, Packing, Markin