Traditional Gap Analysis Template - Procept Associates Ltd.
Document Information
|Related Documents: |Provide the file names of the related documents |
|Author: | |
| |
|Change Record: |Version |Changed By |Date |Revision Description |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| |
|Document Contributors: |Name |Role |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| |
|Document Approvers: |Name |Role |
| | | |
| | | |
| |
| |
Table of Contents
Document Information 2
Objective/Purpose 4
Overview 4
Current Environment 4
Methodology 4
Scope 4
Matrix Definitions 4
Gap Analysis and Resolution Matrix 4
Follow Up/Action Items 5
Glossary 5
Objective/Purpose
• Describe the objective or purpose for creating this document
• Identify the audience for this document
• Outline the rationale for this document, for example:
• To identify process or functionality differences between the current and proposed system
• To determine how to eliminate or minimize the gap between the current and proposed systems
Overview
• Briefly describe and provide background information about the project
• Outline the objectives of the project and what it is trying to achieve
Current Environment
• Briefly explain what technology or processes are in place today and why it needs to be changed
Methodology
• Describe the method used to create this document (e.g., research, workshops, interview including who was interviewed)
Scope
• List at a high level the components of the project that are in/out of scope
Matrix Definitions
• Define the column headings used in the gap and resolution matrix tables to ensure readers understand the purpose of the information that has been provided
• For example:
|Ref: |A unique numeric identifier |
|Topic: |Optional column used to categorize the components in larger gap documents, a functionality |
|Priority: |Optional column used to prioritize each component (e.g., high, medium, low) |
|Current: |Briefly describe each component of the existing process or system for the current system |
|Proposed: |Briefly describe the corresponding component(s) of the proposed process or system |
|Difference: |Determine the difference between the current and proposed systems (where a difference exists). A loss in functionality can be |
| |identified by a “–“ symbol, whereas, a gain or a positive gap can be identified by a “+” symbol. No change in functionality can|
| |be noted as “no gap” |
|Resolution: |Outline the proposed steps towards resolving the gap. This can also be called an Action Plan. The proposed steps can be |
| |categorized (e.g., system change, hardware, configuration, change management, no resolution required) |
Gap Analysis and Resolution Matrix
• This section captures the key information about the current and proposed application or functionality and its resolution
|Ref |Topics |Priority |Current |Proposed |Gap |Resolution |
Follow Up/Action Items
• While completing the gap and resolution analysis, keep a list of items that are outstanding or being followed up on
• The items should be completed or included where appropriate within the document by the time this document is finalized
Glossary
• Define technical terms or acronyms used in this document
-----------------------
Customer Name
Traditional Gap Analysis Template
Project Name
October 20, 2010
v1.0
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.