What is a Project Execution Plan? What you need before you start: The Project Execution Plan is the Agreement to proceed with the ‘road map’ used by the Project Team to deliver the development of the Project Execution agreed project outputs. It outlines the Plan from the Project Sponsor. responsibilities of the Project Team and key Knowledge and understanding of stakeholders. developing detailed project plans, quality plans, implementation and delivery plans, Why would you develop a Project resource scheduling, risk management Execution Plan? planning and financial planning. Knowledge and understanding of the Key A Project Execution Plan is developed to Elements, as outlined in the Tasmanian expand on the Project Business Plan by Government Project Management specifying the day-to-day (operational) Guidelines. management procedures and control plans including: Also Advisable: detailed project plans; Any of the following documents - resource schedules; Strategic Information Systems Plan, quality procedures; Project Proposal, Process Review Report or Feasibility Study. reporting procedures; Departmental Project Management product purchasing and development Guidelines. plans; risk management planning; and project budgets. Integration Process: The document enables those completing the Any endorsed documents (for example a tasks/activities in the project to deliver the Project Proposal, Project Business Case or expected results, as per the agreed Project Project Business Plan) should be utilised to Business Plan. populate the Project Execution Plan. This information, along with any gaps, then When would you develop a Project provides a basis for further discussion, Execution Plan? clarification and confirmation of the project scope. Approval to proceed to develop a Project Execution Plan is usually obtained from the It should be noted that development of the acceptance or approval of a preceding stage Project Execution Plan is not a static such as a Project Proposal or Project process, and that all aspects described in Business Plan. The Project Execution Plan the Execution Plan must be re-examined expands the proposals developed in these many times over the life of the project, documents in order to: particularly where a great deal of change is involved. This iterative development should document the day-to-day (operational) involve the Project Manager and Project management and control activities to be Team. The key is to obtain clear sign-off undertaken by the Project Team; and where scope changes are required during gain acceptance by the Project Sponsor the life of the project. to the suitability of these activities.
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 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 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. 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. Also Advisable: Any of the following documents - Strategic Information Systems Plan, Project Proposal, Process Review Report or Feasibility Study. Departmental Project Management Guidelines. Integration Process: Any endorsed documents (for example a Project Proposal, Project Business Case or Project Business Plan) should be utilised to populate the Project Execution Plan. This information, along with any gaps, then provides a basis for further discussion, clarification and confirmation of the project scope. It should be noted that development of the Project Execution Plan is not a static process, and that all aspects described in the Execution Plan must be re-examined many times over the life of the project, particularly where a great deal of change is involved. This iterative development should involve the Project Manager and Project Team. The key is to obtain clear sign-off where scope changes are required during the life of the project.
Project_execution_plan_template_and_guide.docx