项目输出实现计划

1、；.PM 006 Outcome Realisation PlanDRAFT Template & GuideThis Guide is intended to be read in conjunction with the following template for the development of an Outcome Realisation Plan. As such the Guide should be removed from the front of your final document.Version 0.C (10 January 2001)What is a

2、n Outcome Realisation Plan?The Outcome Realisation Plan is used to support the organisational change management process required for effective utilisation of the agreed project outputs in the business unit(s). It assists in ensuring the achievement of the project outcomes described in the Project Bu

3、siness Plan. Why would you develop an Outcome Realisation Plan?An Outcome Realisation Plan is developed to provide the link between the realisation of the benefits from a project, and the outputs delivered by the Project Team. It covers the final stages of a project up to the point when the utilisat

4、ion of the project outputs has become routine, and the processes are transactional.The purpose of the Outcome Realisation Plan is to ensure that:· the final stages of the project are managed in a satisfactory manner;· the utilisation of the projects outputs are linked to the planned projec

5、t outcomes;· that the success of the projects outputs are assessed and corrective action performed if required; and· the planned project outcomes are achieved prior to formal project closure.In order for the business unit(s) to prepare for the project outputs, they need to be planning and

6、implementing changes progressively throughout the project. Depending on the size and complexity of the project, there may be one or more Outcome Realisation Plan(s). For example where a Business Owner is accountable for only a subset of the projects outcomes, or where multiple Business Owners are ac

7、countable for the same outcomes but in a different organisation / areas.The Outcome Realisation Plan specifies the management procedures, control plans and performance measures that each business unit/area will be put in place once the Project Team has delivered the outputs. In addition, the documen

8、t details any changes that need to be made within the business areas prior to receiving the project outputs.The document enables those completing the tasks/activities in the business area to deliver the expected results, as per the agreed Project Business Plan.When would you develop an Outcome Reali

9、sation Plan?Approval to proceed to develop an Outcome Realisation 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 Plan2 For a defin

10、ition of these underlined terms, refer to the Project Management Glossary. An Outcome Realisation Plan is developed in an iterative manner as the project progresses. Although the Business Owner(s) is responsible for creating and updating the Outcome Realisation Plan, the Project Manager may develop

11、the first release with their co-operation.The Outcome Realisation Plan expands the proposals developed in these documents in order to:· ensure the planned project outcomes are achieved prior to formal project closure.· document how the benefits from the project will be measured, including

12、the base line metrics;· provide the basis for reporting by the business unit(s) to senior management and the Steering Committee on progress towards achievement of these outcomes;· document what changes will be made by the business unit(s) to their tools, policies/procedures and organisatio

13、n in preparation for receiving the outputs from the Project Team;· document the management and control activities to be undertaken by the business unit(s) upon receiving the outputs from the Project Team; and· gain acceptance by the Steering Committee or Proposer to the suitability of thes

14、e activities.What you need before you start:· Agreement to proceed with the development of the Outcome Realisation Plan from the Steering Committee or Project Sponsor.· Knowledge and understanding of the relationship between the outcomes and outputs of the project, and how they are utilise

15、d by each customer (business unit).· Knowledge and understanding of the current tools, policies/procedures or organisation of the business unit(s).· Some knowledge and understanding of the proposed tools, policies/procedures or organisation of the business unit(s). This knowledge and under

16、standing will develop in more detail as the project progresses.· Knowledge of the Tasmanian Government Project Management Guidelines.Optional:· Any of the following documents - Project Proposal/Brief, Project Business Plan.· Knowledge and experience in the development of performance m

17、easures.· Current copies of relevant business process policies/procedures.· Corporate/business plans for dept or business unit.· Departmental Project Management Guidelines.What you will have when you are finished:An Outcome Realisation Plan that is ready for acceptance by the Steering

18、 Committee or Project Sponsor. As the project progresses, this document will need to be updated, revised and re-released.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

19、 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

20、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 no

21、rmal font is intended as examples.· Text enclosed in <angle brackets> is intended to be replaced by whatever it is describing.；.<Project Title>Outcome Realisation PlanOrganisational UnitDEPARTMENT OF Version 0.A (dd mmm yyyy).；.AcknowledgementsThe contribution of the following indiv

22、iduals in preparing this document is gratefully acknowledged:<contributors/reviewers/developers>The following two paragraphs should be included in the documents where these templates have been used as a basis for development.This document has been derived from a template prepared by the Depart

23、ment of Premier and Cabinet, Tasmania. The structure is based on a number of methodologies as described in the Tasmanian Government Project Management Guidelines.For further details, refer to .au.DOCUMENT ACCEPTANCE and RELEASE NOTICEThis is <release/version>

24、 <n.n> of the <Project Title> Outcome Realisation Plan.The Outcome Realisation 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 vers

25、ions from circulation. This document is authorised for release once all signatures have been obtained.PREPARED:DATE:_/_/_(for acceptance)(<Name>, <Project Title>, <Business Unit>)APPROVED:DATE:_/_/_(for acceptance)(<Director/Manager>, <Name, Title>)ACCEPTED:DATE:_/_/_(f

26、or release)(Project Sponsor, <Name, Title>)on behalf of the <Project Title> Steering Committee1.BUILD STATUS:The most recent amendment first.VersionDateAuthorReasonSections<n.n><dd mmm yyyy><Name><e.g. Initial Release><All>2.AMENDMENTS IN THIS RELEASE:Sectio

27、n TitleSection NumberAmendment Summary<e.g. This is the first release of this document.>3.DISTRIBUTION:Copy NoVersionIssue DateIssued To1<n.n><dd mmm yyyy><Name, Title, Organisation>2ElectronicTABLE OF CONTENTS1.INTRODUCTION11.1.Document Purpose11.2.Intended Purpose11.3.Outco

28、mes21.4.Management Plan31.5.Assumptions and constraints31.6.Current Project Status31.7.Updating this Plan42.TRANSITION PLAN52.1.Current Situation52.1.1.Culture52.1.2.Physical Environment52.1.3.Structure52.1.4.Job Design / Responsibilities62.1.5.Skills / Knowledge Requirements62.1.6.Policies / Proced

29、ures62.1.7.Workflows / Processes62.2.New Situation62.2.1.Culture62.2.2.Physical Environment62.2.3.Structure72.2.4.Job Design / Responsibilities72.2.5.Skills / Knowledge Requirements72.2.6.Policies / Procedures72.2.7.Workflows / Processes72.3.Transition Current to New72.3.1.Culture82.3.2.Physical Env

30、ironment82.3.3.Structure82.3.4.Job Design / Responsibilities92.3.5.Skills / Knowledge Requirements92.3.6.Policies / Procedures92.3.7.Workflows / Processes92.3.8.Employee Motivation / Incentives92.3.9.Human Resource Management102.4.Transition Schedule103.COMMUNICATION PLAN113.1.Key Communication Issu

31、es113.2.Communications Strategy113.3.Stakeholder Groups123.3.1.Stakeholder Analysis123.4.Communication Milestones134.TRAINING PLAN145.MAINTENANCE PLAN176.PERFORMANCE MEASUREMENT PLAN176.1.Purpose176.2.Defined Measures176.3.Baseline176.4.Monitoring and Reporting176.5.Project Closure177.GLOSSARY AND A

32、PPENDICES17.；.1. Introduction The Introduction is used to explain the purpose, role and scope of this document, and describes the context in which it has been developed.1.1. Document PurposeUnder the Tasmanian Governments project management methodology, the Outcome Realisation Plan (ORP) is the mana

33、gement document for the projects Business Owner(s). Once a project delivers outputs to the Business Owner(s), they must be utilised to enable the projects outcomes to be generated and realised. This stage of the project is therefore referred to as Outcome Realisation.Depending on the size and comple

34、xity of the project, the need for multiple ORPs for the project may arise. Examples include where Business Owners may be accountable for only a subset of the projects outcomes, or multiple Business Owners may be accountable for the same outcomes but in a different organisation / areas.State the proj

35、ects other planning documentation (e.g. Project Business Plan, Execution Plan etc) to provide a picture of the methodology being applied to the project.The purpose of the Outcome Realisation Plan is to ensure:¨ the final stages of the project are managed in a satisfactory manner;¨ the util

36、isation of the projects outputs are linked to the planned project outcomes;¨ that the success of the projects outputs are assessed and corrective action performed if required; and¨ the planned project outcomes are achieved prior to formal project closure.This document is the responsibility

37、 of <Name, Title, Org. of Business Owner> and will be revised and amended to meet changing conditions or objectives during the projects life span.1.2. Intended PurposeClearly identify the intended audience of this document. It may include the Steering Committee, key representatives from the bu

38、siness area(s), and major stakeholders who will be impacted by the planned outcomes.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 assumed;¨ as

39、 the document proceeds through a series of iterations during the life of the project, its structure, emphasis and intended audience may change.1.3. OutcomesThis section is used to re-iterate the projects outcomes and clearly identify output utilisation and outcome realisation responsibilities.List t

40、he projects outcomes and the Business Owners accountable for their realisation.Table <n>: Outcome ownershipOutcomeAccountable Business Owner(s)A.<Improve access to Tasmanian legislation>B.<Reduce the input costs of business and Government in respect to the law><Table examples ar

41、e from the Legislation System Project (LSP)>The process to identify the linkages between outcomes, outputs and stakeholders usually occurs during the project initiation and planning phase.Under the Tasmanian Governments project management methodology, there is a formal process defined for the acc

42、eptance and hand-over of outputs to the Business Owner(s). This is usually defined within the Project Execution Plan. In the absence of this process being defined elsewhere, a summarised description or document cross-reference may be appropriate here.Table <n+1>: Output utilisersStakeholders w

43、ho will utilise OutputsXYABOutcomeOutputsA.1. <Implementationof a new legislation drafting and storage system>2. <Consolidation of the Tasmanian Statute Book in electronic form>*B.3. <Re-engineer current legislation printing process>.*<Table examples are from the Legislation Sys

44、tem Project (LSP)>An * appearing in column indicates stakeholder utilisation.The tables provided above are but one example for presentation purposes. Depending on the size of the project, the information may be presented using alternative methods or in other tabular formats within an appendix.1.4

45、. Management PlanAlthough Business Owners are accountable for outcome realisation, they will usually not be in a position to execute the ORP directly, nor manage its execution. Performing these tasks may require separate resources as it can be regarded as a project in its own right. Appropriate gove

46、rnance within the business area(s) therefore ensures output utilisation will be managed once the outputs have been accepted for implementation.A detailed management plan is therefore included as Appendix 1 to this template. Its applicability will very much depend on the nature of the project, the or

47、ganisational context and how the governance of the project is to be / has been established. Appendix 1 is quite detailed. Only the relevant sections should therefore be completed to avoid duplication or conflict with other project documentation such as the Project Business and Execution Plans.Altern

48、atively, the governance structure defined in the Project Business Plan, or corresponding document, may already include provisions for managing the outcome realisation stage of the project.1.5. Assumptions and constraintsIt is essential that any assumptions and constraints are recognised and recorded

49、 within each release of this Outcome Realisation Plan. Cross-reference to the Project Business Plan section on assumptions and constraints if appropriate. Examples of assumptions and constraints include deadlines, financial and budgetary, legislation, resource availability, environmental, technology

50、, security, related projects etc.1.6. Current Project StatusThis section allows for the current status of the project to be summarised so as to describe for the reader the context in which a particular release of the ORP has been produced. If an ORP is to be a one-off release, this section may be in

51、appropriate. However, the ORP may develop through a series of released documents during the projects life span, then this section may add value for stakeholders. Information that may be summarised includes:· phases, milestones, and dates from the projects schedule;· what has been achieved;

52、 what has changed significantly since the project commenced, and what is to happen over the next period;· current risks and issues etc.1.7. Updating this PlanExperience in managing large projects has shown that the development of the ORP needs to commence as early as possible in the projects li

53、fe span, usually once the scope and objectives are defined and agreed. Planning for and undertaking some implementation activities will be required prior to acceptance of the first output.Describe the strategy that is to be followed for the development of this Outcome Realisation Plan. Is it expecte

54、d that the Outcome Realisation Plan will be updated and released to the Steering Committee at key points during the projects life span?As a minimum, it is recommended that the ORP be released prior to the implementation and utilisation of any project outputs.Table <n+2>: Outcome Realisation Pl

55、an release scheduleVersionDateReasonWho<1.0><dd mmm yyyy><Initial release of the ORP during the projects planning phase to introduce the change thread: from the business units perspective to the key stakeholders><Project Manager and Business Owner(s)><2.0><dd mmm yyy

56、y><Release after functional requirements/design but prior to development/testing><Business Owner(s)><3.0><dd mmm yyyy><Release during/after acceptance testing but prior to development/testing><Business Owner(s)><4.0><dd mmm yyyy><Updated release

57、after/during implementation as a result of changes, revised schedules, staged implementation etc (optional).><Business Owner(s)>2. Transition PlanThe Transition Plan is used to describe how the changes to the business unit(s) environment will be implemented.The Implementation Plan focuses o

58、n changes that are anticipated, planned ahead of time (e.g. a reduction in the number of staff). However, other changes may result, such as those that emerge and are unintended (e.g. increased salaries). At a minimum, these changes or issues will require tracking.2.1. Current SituationBriefly describe the current situation within the business unit(s) that will be impacted by this transition plan in the areas of:· Culture;· Physical Environment;· Structure;· Job Designs/Responsibilities;· Skills and Knowledge;· Policies/Proc