0000 Business Analysis Template Gap Analysis v006

download 0000 Business Analysis Template Gap Analysis v006

of 14

  • date post

    05-Sep-2014
  • Category

    Documents

  • view

    110
  • download

    3

Embed Size (px)

Transcript of 0000 Business Analysis Template Gap Analysis v006

This document contains an instructional text style and an instructional list bullet style, both identifiable in blue paragraphs. Prior to finalising your document ensure you remove all instructional text. To do this: Word 2003 Right click on any blue paragraph. From the menu Select text with similar formatting. Hit Delete on your keyboard. If instructional text bullet styles are present click on any blue paragraph bullet style and repeat the step. Word 2007 Right click on any blue paragraph. From the menu select Styles and then Select text with similar formatting. Hit Delete on your keyboard. If instructional text bullet styles are present click on any blue paragraph bullet style and repeat the step. NB: Page and sections breaks may be out of alignment until all instructional text is removed.

Gap AnalysisType the Programme Name below if applicable. Delete the line if not required.

Follow these steps to set Document Properties. Word 2003 Open File/Properties/Summary. In the Title field enter the Document Name. In the Subject field enter the Project Name. In the Author field enter Your Name. Click OK and save the document. Word 2007 Click MS Office Button/Prepare/Properties. In the Title field enter the Document Name. In the Subject field enter the Project Name. In the Author field enter Your Name. Save the document. Update Fields You must now update these fields in the document. Click on a field and then the F9 key. Ensure you update fields on the cover page and headers in all sections of your document.

Document Identification File name: 95832609.doc

Information Technology Services

Gap Analysis

Document Identification Version: Status: Date: Prepared by: Contributors:

The status field should indicate whether the document is Draft or Approved. Contributors are stakeholders that have contributed directly to the contents of this document.

Responsible Authorities Project Sponsor: Project Manager: Senior User: Senior Supplier Service Owner System Owner

Add or delete Authorities as required.

Page 2 of 14

Gap Analysis

StakeholdersThe Stakeholders section is used to capture the details of any stakeholder who has contributed to the gap analysis presented in this document. All contributors listed here should also appear in the projects Stakeholder Analysis spreadsheet. The initials of each stakeholder will appear besides the statements that they have been the source of. The Position is sometimes referred to as title. Examples of this are Director, Project Services, ITS and Associate Dean, MDHS. You should provide each contributors phone number in the contact details section. You may also provide their email address if you wish. An appendix has also been provided that can be used to capture the meetings you have had with the contributors. The following stakeholders have contributed to this Gap Analysis. The full list of stakeholders is in the Stakeholder Analysis spreadsheet for this project.Name Position Contact Details Initials

ReviewersName Position Contact Details Date

ApprovalsThe Approvals section is used to capture the details of those stakeholders who are responsible for approving the contents of this document. Their details should be added here during the early draft stages of the document. The Approved checkbox should be checked and the date entered only when an approval has been provided by the stakeholder in the form of an email or an actual signature. Checking the Approved checkbox is most easily achieved by double-clicking the box to open the Properties dialog and changing the Default value option to Checked. It is recommended to have an email approval stored within the project repository.Name Position Approved Date

Page 3 of 14

Gap Analysis

Document purposeGap Analysis is a comparison of the current state and desired future state of an organisation in order to identify differences that need to be addressed. - A Guide to the Business Analysis Body of Knowledge. IIBA.version 2.0 Any reference to the use of a specific technology or interface design elements is entirely inappropriate in a gap analysis document. This document captures the difference between the current state and desired state of a system. This Gap Analysis will drive the targets of the relevant project. It is designed to fulfil several purposes: As a means to identify the gaps in the current state As a means to help define the problem that is to be solved by the project As a means to help define the desired future state of the project.

This document is solution independent. It is intended to be a statement of the difference between two states, not how the target future state will be achieved.

Table of contents1 Introduction............................................................................................................................................5 1.1 Audience.....................................................................................................................................5 1.2 References..................................................................................................................................5 2 Gap analysis overview...........................................................................................................................6 2.1 Document scope.........................................................................................................................6 2.2 Assumptions................................................................................................................................6 2.3 Recommendation........................................................................................................................6 3 Gap analysis...........................................................................................................................................7 3.1 Identified gaps.............................................................................................................................7 4 current state.........................................................................................................9 4.1 Overview.....................................................................................................................................9 5 System/process> target future state................................................................................................10 5.1 Overview...................................................................................................................................10 6 Conclusion............................................................................................................................................11 7 Appendices...........................................................................................................................................12 7.1 Glossary....................................................................................................................................12 7.2 Gap analysis elicitation record...................................................................................................12 8 Document control.................................................................................................................................13

Page 4 of 14

Gap Analysis

1

Introduction

You should provide here a brief overview of the project and the purpose for the Gap Analysis. This should be no more than two paragraphs long and present in as few words as possible the background, aims of the project and the purpose for Gap analysis. This section must reflect the content in the Concept Proposal/Project Brief / Business Case (depending on which stage the Gap Analysis is at). While this may seem needlessly repetitive, keep in mind that the audience may not have seen the preceding project documents for months if at all.

1.1

Audience

You are free to leave the text below as is or alter it according to your needs. The typical audience for a Gap Analysis document such as this is: Project Sponsor The project sponsor could use this as a supplementary information document ideally prior to the project mandate

Business Subject Matter Experts These people are key contributors to the contents of this document and will be asked to review and validate that what has been captured accurately represents the Gap Analysis.

Project Manager The project manager could use this document as a basis for the project mandate.

Business Analysts Business analysts may use this document as a basis for gap analysis gathering, baseline for feasibility studies and for requirements gathering purposes.

Other ITS Staff Other staff may refer to this document to help them improve their understanding of the project and how it may relate to work they are undertaking.

1.2

References

Some of the following documents types may be available: Project Initiation Document Feasibility Study Project Brief Stakeholder Analysis If these documents have been created for your project, they should be listed in this section. It is important to list all relevant documents here so add as many entries as needed. Other documents such as meeting minutes and those created by external parties may also be referenced. The reference structure provided below is a guide only. Include as much information as makes sense for each document. We generally do not include the location of documents as these are typically not very stable and are often inaccessible to the audience anyway. 1. 2. , , , , , , , ,

Page 5 of 14

Gap Analysis

22.1

Gap analysis overviewDocument scope

This section explicitly states which types of information are included and excluded from this