Gap Analysis Report

Parent Previous Next

Gap Analysis Report

1. Information about the Deliverable



Date Last Reviewed:

27 August 2007


Document describing gaps.  Sometimes it is supplemented and/or replaced with a Gap analysis presentation.  A Gap is typically defined as a mismatch between desired and current, often expressed as a degree of mismatch.

Deliverable Type:

Report and/or Presentation



2. How to construct the deliverable using the eaMindShare CE approach


High level Action

A. Engagement

Orientate with current situation; the area that the Gap Analysis must cover and the particular Business/Technology context.  Is this part of a bigger due diligence excercise or can this be as simpel as a basic SWOT analysis?

B. Calibration

Validate time periods.  When must this be done and proper understanding of general timeline.

C. Discovery

Identify the known/recorded Issues.  Identify the not-known issues by facilitating one or more workshops

D. Envisioning

Rank Review gaps and perform a level of assessment

E. Validation

Iteratively refine using a validation/buy-in cycle.  Ideally develop mitigations for Gaps

F. Realisation

Publish Gap Analysis Report

3.  Template/s & Samples




Export Views

Map View

Template/s are disabled for eaMindShare Community Edition due to document sizes.  Rather use  eaMindShare Professional  Edition  and/or eaMindShare Workgroup Edition if you want to access the templates.

Ideally export and further refine in:

4. Additional Information

Fundamentally Gap Analysis is a very simple concept. For each attribute, the difference between the expectation and delivery is measured and sorted from highest to lowest. It effectively highlights the attributes you need to focus on.

Created with the Personal Edition of HelpNDoc: Easily create Help documents