Back to Guides

EA gap analysis

This guide clarifies the methodology for analyzing gaps between current and target EA components within the EA component development cycle, and for identifying solutions to close those gaps in line with the entity's strategic objectives.

Per the DGA EA gap analysis guide: two steps (identify gaps, propose and approve solutions), guidance considerations, illustrative templates, and expected outputs in one document.

What is EA gap analysis?

2
steps
6
domains

What is EA gap analysis?

It aims to identify the gap between the target future state and the current state of the EA so that mechanisms to close it can be studied, then to propose and approve solutions as a basis for building the EA implementation roadmap. It is carried out in two main steps.

Done per domain; results are consolidated and linked to the roadmap.

Steps for EA gap analysis

Two main steps per the DGA guide: identify EA gaps, then propose and approve solutions to close them.

1

Identify EA gaps

Identify the gap between the target future state and the current state so that mechanisms to close it can be studied.
2

Propose and approve solutions for EA gaps

Identify solutions to be implemented to close the gaps and achieve the target EA, as a basis for building the EA implementation roadmap.

Step 1 details

Inputs: EA development cycle charter; EA requirements; documented current state of components and views for all EA domains; documented target state of components and views for all EA domains.

Outputs: List of EA gaps; RACI matrix.

Review and analyze

Review and analyze EA components: the Chief EA and EA team review and analyze documented current and target state per domain. For each domain in scope: identify components to retain, to retire, to update, and new components to create.

Identify gaps

Identify gaps, then discuss, refine, and decide: merge gaps that are similar in cause; or split a gap that spans more than one domain into separate gaps per domain; or remove gaps that do not relate to EA components (e.g. lack of qualified staff).

Step 2 details

Inputs: List of EA gaps and target state.

Outputs: List of solutions to close EA gaps; RACI matrix.

Propose solutions

Propose and document initial solutions (description and key milestones, e.g. new application, data restructuring, external provider). Discuss impact on other gaps and whether to merge similar or dependent solutions for higher efficiency and lower cost.

Evaluate solutions

Evaluate solutions by expected impact and ease of implementation: quick wins (short duration, high impact); medium-term solutions (medium duration, high to medium impact); long-term solutions (long duration, medium to low impact).

Final list

Prepare the final list of solutions with scope and gaps linked to each solution; discuss with business and IT stakeholders and update as needed.

Guidance considerations for EA gap analysis

Classify gaps into groups (e.g. improving beneficiary experience, cloud adoption, improving a unit's performance) to make it easier to find solutions.

Document each gap: code, related requirement, definition, description, owner, priority (high/medium/low), affected domain(s), affected components, related views, related project (to be set in the roadmap phase).

Consider expected changes in the operating environment and the need for transitional or phased solutions to ensure continuity until the target state is reached.

Ensure proposed solutions do not conflict with strategic business directions.

One solution can address one or more gaps; multiple solutions can be proposed for the same gap; all are subject to final evaluation.

When evaluating impact: number and priority of gaps addressed; effect on performance, beneficiary experience, business improvement, or data quality.

When evaluating ease of implementation: expected cost, duration, number of stakeholders involved.

Document each solution: code, definition, description, priority, linked gaps, affected domain(s).

Illustrative models for documenting gaps and proposed solutions

EA gap list

EA gap list: gap code, related requirement, definition, description, owner, priority, affected domains, affected components, related views, related project.

Link gaps to project cards

Linking gaps to project cards: record gaps linked to each project or include them in each project's definition card to track which gaps each project closes.

Proposed solutions list

Proposed solutions list: solution code, definition, description, priority, linked gaps, affected domains.

Expected outputs

The entity must document EA gap analysis for all EA domains, link gaps to projects and initiatives, and document the list of proposed solutions to address gaps, in a single document that includes: (1) list of gap details, (2) list of proposed solutions to address gaps, (3) link gaps to initiative/project cards.

Inputs and outputs summary

Gap analysis uses specific inputs and produces outputs that feed the roadmap development phase.

Inputs (Step 1)

EA development cycle charter, EA requirements, documented current state (components and views per domain), documented target state (components and views per domain).

Outputs

Step 1: list of EA gaps and RACI matrix. Step 2: list of solutions to close gaps and RACI matrix. Final deliverable: a single document with gap details, proposed solutions list, and link of gaps to initiative/project cards; it feeds the roadmap development phase.

RACI matrix

Responsible (R): EA team. Accountable (A): Chief EA. Consulted (C) and Informed (I): business and IT stakeholders; senior management.

A

Chief EA: Accountable (A)

R

EA team: Responsible (R)

C/I

Business and IT stakeholders and senior management: Consulted and Informed (C / I)

Related topics

National methodology

Six domains

EA requirements management