Business Impact Assessment文档格式.docx

1、Purpose of DocumentThe purpose of the Business Impact Assessment document is to identify all business change impacts on stakeholders internal to and external to Information Technology Services. The document will:Provide sufficient information to enable the design and development of the Change Manage

2、ment Strategy or any other change artefactIdentify any dependencies and risksProvide any relevant recommendations for any change initiativesTable of Contents1 Executive SummaryPurposeThe Business Impact Assessment documents the impacts on business and people based on project implementation. Business

3、 Impact Assessment ObjectivesScopeIn ScopeOut of ScopeBusiness Impact SummaryInclude key impacts grouped as system, process and people. Also include impacted stakeholders. StakeholderStakeholder No.ImpactType （People, Process, Tech.）Impact Level （H/M/L）Key Findings Include key risks and any key inte

4、rrelationships between impacts 2Introduction-Provide background to the project （including drivers and reasons for change）. Information can be sourced from the Business Case and Project Brief.-Explain what a BIA is:“The Business Impact Assessment （BIA） identifies all stakeholder impacts as well as pr

5、oject implementation impacts based on stakeholder resistance or impacts of other projects. Analysing these impacts will help to identify the initial Change Management approach to be expanded on.”-Link project background to the Business Impact Assessment （BIA） and what the outcome will be. Business I

6、mpact Assessment Objectives General objectives of the BIA include:- Identifying the gaps between current and future states （using the Business Requirements Document （BDR） and Non-functional Requirements （NFR） documents）-Identifying other environmental impacts such as other projects, business changes

7、 etc-Identifying general resistance issues to technology for each stakeholder （using the Stakeholder Analysis Document）-Analysing （based on the above） the impact on stakeholders and initial recommendations on Change Management initiatives-Update with any additional objectivesDocument Scope In scope

8、Out of scopeExtensive analysis of University wide impacts3Gap AnalysisThe Gap Analysis captures requirements identified in the Business Requirements Document and the Non-Functional Requirements documents that will impact on stakeholders, business, processes etc . The analysis identifies the differen

9、ce between current and future states and the resulting gap can be further analysed to identify the extent of impact on stakeholders, business, processes etc.Process for completing:-Review Feasibility Study Business Environment section -Capture all BRD and NFRs （including reference numbers for tracea

10、bility）-Determine appropriate business representatives to provide input into the impact assessment （i.e. “as is” and “to be” situation）-Determine Current and Future States （note conduct workshop with relevant business and project representatives to brainstorm gaps-Information can also be sourced fro

11、m interviews, focus groups, surveys, assessments, action plans-Identify key audience groups impacted include numbers, locations, roles etcUse the following table for completing the analysis. BRD/NFR Ref no./ OtherCurrent StateFuture StateGapStakeholder Table 1: Gap Analysis4Environmental AnalysisSpo

12、nsorshipThis section allows you identify all other aspects that may impact the project. These may be （in most cases） indirect impacts, however need to be considered when analysing the overall impact on stakeholder groups. These impacts may include:Workplace agreementsEnterprise agreementsEHSSafetyFa

13、culty restructuresOther projectsNote that some of these will be out of scope and should be recorded as such. For example non project initiative faculty restructures and their associated change management will be managed by that faculty. An awareness of such changes may influence the level of impact

14、of a project specific cultural impact. 5Stakeholder AnalysisProvide an overview of stakeholder analysis and its importance to the overall impact analysis. Refer to the existing stakeholder analysis document and summarise key stake holder groups relevant for this document. This section can be introdu

15、ced with the following script and/or amended version. “Understanding the levels of influence and interest for both internal and external stakeholders ensures that any change impacts can also be viewed from the stakeholder perspective. The following table includes a summary of the stakeholder that ar

16、e impacted by this project as well as their expectations in relation to the project objectives. Stakeholders can also be broken down into subsets based on their level of experience with technology. For example in the case of researchers there will be focus groups, pilot groups and new users of a new

17、 system or service. These subsets will have different expectations which need to be considered when planning for the different change initiatives.”SubsetInfluenceInterestExpectationsResistance Issueseg Pilot groupH, M or Leg system that workseg has not worked I the past so what has changedTable 4: S

18、takeholder Summary6Impact Analysis Using the requirements impact analysis, environmental analysis and stakeholder analysis, review the overall impact using the template below.Identification of all impacts will help to identify key areas of focus such as stakeholder management, process improvement, t

19、raining initiative etc. HeaderDescriptionChange ImpactSummary of impactdescription of impact （no more than 100 words）Include stakeholder groups and/or role （if required）CategoryCategory identifies the type of impact People （is there a direct impact on people）Structure & roles （is there an impact on

20、how things are Culture （is there an overall impact on people/groups as a whole）Process （will there be a change to processes）Skills （will skills need to be developed）Technology （will there be system/technology changes）Level of impactHigh: Large number of people impacted and/or large amount of changeM

21、edium: Moderate number of people impacted and/or moderate amount of changeLow: Not many people impacted and/or small amount of changeResistance issuesInclude any stakeholder resistance issues that may impact awareness, acceptance and /or adoption of the change. Risk of inactionRisk of not implementi

22、ng some form of change management initiative. Change ActionsThe following change actions can be used based on all the information for each impact:Change Management Strategy for items that have significant impacts on stakeholders. This includes Organisational Redesign, Transition strategies, engageme

23、nt and communications strategies etc. Training Needs Analysis for items that have significant change to Business Process Reengineering for major process changesTable 13 Impact Analysis KeyBRD/NFR Ref No. or otherChange ImpactDescriptionStakeholderCategory （System/ Process/ People）Group Level of Impa

24、ct （H/M/L）Resistance IssuesChange ActionsBRD001User interface changes THEMIS Research to support business requirement of XXXResearcherProcessPeopleHTNABPRChange Mgt strategy0002Policy XX createdNew policy created which includes other changes as well as the specific project related changeAll admin st

25、affLThe mix of changes in the policy are not supported by staff and may impact the project change 7Risks and IssuesRisks and issuesMitigations8RecommendationsInclude any recommendations based on major impacts. 9Appendix AAttach any addition information that supplements the design specification.Gloss

26、ary of TermsIdentify all terms that establish meaning within the context of the plan. TermMeaningTable 14 Glossary of TermsDocument ControlApprovalsVersion NumberApproval DateNameTitleSignature/Email refReview HistoryReviewDateVersion HistoryVersionSummary of ChangesAuthorTemplate ControlYou should delete this template control page prior to using/publishing for your project.Template ApprovalsTemplate Review HistoryTemplate Version History0.119/3/2010Original documentA Turudic0.27/9/2010Confirmation of BRD and NFR number inclusions0.34/10/2010Update on Environmental Analysis section