《PostImplementation Review 0f Business Outcomes实施后回顾的业务成果.doc》由会员分享，可在线阅读，更多相关《PostImplementation Review 0f Business Outcomes实施后回顾的业务成果.doc（10页珍藏版）》请在三一办公上搜索。
1、Post-Implementation Review of Business Outcomes Template PROJECT DELIVERY FRAMEWORKPOST-IMPLEMENTATION REVIEW OF BUSINESS OUTCOMES Agency/Organization NamePROJECT NAMEVERSION: VERSION NUMBERREVISION DATE: DATEApproval of the Post-Implementation Review of Business Outcomes indicates an understanding
2、and acceptance of the post-implementation results described in this deliverable. By signing this deliverable, each individual agrees the information accurately conveys project delivery results and is ready to be forwarded to the Quality Assurance Team.Agency HeadNameEmailTelephoneSignature:Date: Exe
3、cutive SponsorNameEmailTelephoneSignature:Date: Technology SponsorNameEmail TelephoneSignature:Date: Project ManagerNameEmailTelephoneSignature:Date: Information Security OfficerNameEmailTelephoneSignature:Date: ContentsSection 1.Project Impact on Agency Objectives11.1Product and/or Service Performa
4、nce11.2Goals and Objectives1Section 2.Quantitative and Qualitative Benefits12.1Statutory Fulfillment12.2Strategic Alignment22.3Agency Impact Analysis32.4Financial Analysis4Section 3.Project Outcomes53.1Project Quality53.2Scope53.3Cost (Budget)63.4Schedule6Section 4.Agency and State Lessons Learned6S
5、ection 5.Future Review Plans7Section 6.Glossary7Section 7.Revision History7Section 8.Appendices7Section 1.Project Impact on Agency Objectives1.1Product and/or Service PerformanceBusiness goals and objectives were described in the Business Case and refined in the Project Plan by establishing performa
6、nce objectives, standards, and measurements for the product and/or service. Describe the actual performance measurement results achieved for each performance objective. Product and/or Service Performance ObjectivePerformance StandardActual Performance Measurement Results1.2Goals and ObjectivesBased
7、on actual performance measurement results, describe the projects impact on the agencys ability to meet the business goals and objectives described in the Business Case and refined in the Project Plan. If the stated business goals and objectives were not met, include factors that inhibited performanc
8、e in the project impact description.Business Goal/ObjectiveProduct and/or Service Performance ObjectiveProject Impact to Business OutcomeSection 2.Quantitative and Qualitative Benefits2.1Statutory FulfillmentFor each of the factors identified and described in Section 5 of the Business Case, and show
9、n below, describe the projects impact on the agencys ability to fulfill statute and other mandates. If a value factor is not applicable to the project, state “not applicable.” If applicable, include reasons that inhibited achieving the expected benefit in the project impact description.#Value Factor
10、Project Impact to Business Outcome1The project is implemented to satisfy a direct mandate or regulation (state, federal, national, international)2The project is implemented to satisfy a derived mandate or regulation (state, federal, national, international)3Implementing the project improves the turn
11、around time for responses to mandates or regulatory requirements4The project results in agency compliance to mandates or regulatory requirements 5The project results in agency avoidance of enforcement actions (e.g., penalties) based on mandates or regulatory requirements6Implementing the project ach
12、ieves the desired intent or expected outcomes of the mandates or regulatory requirements7Implementing the project imposes stricter requirements, or different or additional requirements, than those required by the mandates or regulations8Other9Other10Other11Other2.2Strategic AlignmentFor each of the
13、factors identified and described in Section 5 of the Business Case, and shown below, describe the projects impact on the ability to deliver a technology solution aligned with the agencys and the states strategic goals and objectives. If a value factor is not applicable to the project, state “not app
14、licable.” If applicable, include reasons that inhibited achieving the expected benefit in the project impact description.#Value FactorProject Impact to Business Outcome1The project is aligned with, and delivers business outcomes, that support agency and statewide goals2The project satisfies a strate
15、gic agency or state mission critical need, regardless if required by a mandate or regulation 3The project results in the ability of the agency or state to better share resources with other agencies or states as part of a long-term strategic alignment effort 4The project is aligned with the overall m
16、ission of the agency and state5The project strategically consolidates and streamlines business practices and administrative processes6The project is aligned with the overall vision of the agency and state7The project is aligned with the overall priorities of the agency and state8Other9Other10Other11
17、Other2.3Agency Impact AnalysisFor each of the factors identified and described in Section 5 of the Business Case, and shown below, describe the projects impact on the ability to deliver a technology solution that supports the agencys architecture and standards. If a value factor is not applicable to
18、 the project, state “not applicable.” If applicable, include reasons that inhibited achieving the expected benefit in the project impact description.#Value FactorProject Impact to Business Outcome1The project results in systems which support the defined architecture/standards for the agency and stat
19、e2The project results in systems which reduce or eliminate redundant systems3The project results in systems which enable reuse of code/components available from other state or federal agencies4The project results in systems which improve consistency between systems within the agency through standard
20、ization5The project results in systems which leverage the technical capability of commercial-off-the-shelf (COTS) software packages6The project results in systems which provide the ability to evolve as new technologies emerge7Other8Other9Other10Other2.4Financial AnalysisFor each of the factors that
21、represent the projects quantitative benefits, identify and quantify the benefits realized to date. Provide a forecast of the benefits not yet realized. Identify the specific time period (mm-yy) encompassed by the realized and forecasted benefits. If a factor is not applicable to the project, state “
22、not applicable.”Realized Time PeriodForecasted Time Periodtoto#Value FactorRealizedForecastedIdentify Cumulative Savings1Reduced IT and non-IT FTE costs including fringe benefits2Reduced IT and non-IT contractors/consultants3Reduced outsourced labor costs4Improved workflow/business processes5Reduced
23、 error rate6Reduced hardware maintenance/upgrade expense7Reduced software maintenance/upgrade expense8Reduced facilities rental/maintenance expense9Reduced equipment rental/supplies and materials expense10OtherIdentify Cost Avoidance11Avoid penalties12Avoid loss of funding13Improved enforcement acti
24、ons14Asset protection15OtherIdentify Revenue Generation16Additional revenue generated17Increased interest earned18OtherIdentify Constituent Project Benefits19Reduced constituent transaction costs20Reduced service delivery cycle time21Increased service availability/accessibility22Expansion of service
25、s23Reduced (paper) reporting requirements24Improved ability to locate regulatory requirements25Improved accountability/compliance26Greater consistency in constituent/state transactions27OtherGeneral Questions Regarding Financial Forecast:28Will the Net Present Value exceed 0? If so, by how much?29Wh
26、en is the expected Project Breakeven Point?30What is the projects expected Return on Investment?Section 3.Project Outcomes3.1Project Quality 3.1.1Quality Standards Summarize the overall project quality, including the impact on business outcomes, based on an assessment of whether the project satisfie
27、d the quality standards defined for the project. =3.1.2MethodologiesSummarize which aspects of the planned methods were used and explain the impact of using or not using each method on project outcomes, including the impact of using the defined project life cycle methodology, project management meth
28、odology, systems development methodology, or other methodologies on project outcomes.=3.2ScopeSummarize the impact of any changes to the initial project scope on business outcomes, including approved and non-approved changes. =3.3Cost (Budget)Identify the initial estimated and final project costs.Pr
29、oject ItemReport to DateInitial Estimated Project CostProject Cost to Date (Fiscal)Project Cost to Date (Total)Summarize the impact of any changes to the initial cost baseline on business outcomes, including approved and non-approved changes. =3.4ScheduleIdentify the initial planned project start an
30、d finish dates. Identify the final project start and finish dates.Project ItemReport to DateInitial PlannedProject Start and Finish DatesBaseline Date:FinalProject Start and Finish DatesBaseline DateSummarize the impact of any changes to the initial schedule baseline on business outcomes, including
31、approved and non-approved changes.=Section 4.Agency and State Lessons LearnedState lessons learned in terms of a problem (issue). Describe the problem and include any agency/state-level references (e.g., Governance Handbook, Business Continuity Plan, Project Delivery Framework tool) that provide add
32、itional details. Identify recommended improvements to correct a similar problem in the future, including elevation plans for communication and follow-up about the improvement.Problem StatementProblemDescriptionReferencesRecommended ChangeElevated ToSection 5.Future Review PlansDescribe plans for per
33、forming future review(s) of benefits or business outcomes following project closeout if necessary. Include planned execution and approval dates, who is responsible for ensuring the review is accomplished, and the frequency, if applicable.Review DescriptionPlanned DatePlanned Approval DateAssigned To
34、FrequencySection 6.GlossaryDefine all terms and acronyms required to interpret the Post-Implementation Review of Business Outcomes properly.=Section 7.Revision HistoryIdentify changes to the Post-Implementation Review of Business Outcomes.VersionDateNameDescriptionSection 8.AppendicesInclude any relevant appendices.=
