PM 005 Project Execution PlanTemplate & 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 1.0 (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 day-to-day (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 completing 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 day-to-day (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: 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 completed 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 completed can be indicated in a number of alternative methods depending on the reason for non-completion, 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 is intended to be replaced by whatever it is describing.Project Execution PlanOrganisational UnitDEPARTMENT OF Version 0.A (dd mmm yyyy)DOCUMENT ACCEPTANCE and RELEASE NOTICEThis is of the 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 complete replacement. Recipients should remove superseded versions from circulation. This document is authorised for release once all signatures have been obtained.PREPARED:DATE:_/_/_(for acceptance) (, Project Manager)ACCEPTED:DATE:_/_/_(for release) (Project Sponsor, )1.BUILD STATUS:The most recent amendment first.VersionDateAuthorReasonSections2.AMENDMENTS IN THIS RELEASE:Section TitleSection NumberAmendment Summary3.DISTRIBUTION:Copy NoVersionIssue DateIssued To12ElectronicTable of Contents1Introduction11.1Document Purpose11.2Intended Audience11.3Project Outputs11.4Scope of Work22Management Plan22.1Management22.2Status Reporting32.3Risk Management42.4Provision of Facilities and Equipment52.5Skills and Resource Requirements52.6Configuration Management62.7Confidentiality7