GAP Analysis in

Business Analysis

(Professional Business Analyst Training

organisation)

•Gap Analysis is a technique that clearly defines

states the difference between the current state and

the proposed state / future state of any business

entity to streamline its functionalities.

•In other words, a technique that businesses need to

determine what is the course of action to be taken to

move from the current or existing stage to the

desired state or future state.

Need Gap analysis:

This can be also called as Need Gap Analysis or Need

Analysis or Need Assessment.

This is the technique will be used at Enterprise Analysis

being done by the top business managers before taking /

accepting new assignments or projects.

Traditional BA (Waterfall) Agile BA

Requirements are documented in Use Cases,Business Requirements, Functional requirements, UI Specifications, Business Rules.

Requirements are documented in Epics, User Stories and optionally Business (or Essential) Use cases.

   

Focuses on completeness of requirement and spends time in ensuring the requirement is unambiguous and has all the details.

Focuses on understanding the problem and being the domain expert so that s/he can answer questions from the development team swiftly and decisively.

Focuses on getting a ‘sign off’ on the requirements.

Focuses on ensuring the requirements meet the currentbusiness needs, even if it requires updating them.

Often there is a wall between the BA/Business and the Development team.

Agile BA (Often called as Product Owner) is part of the team.

Tends to dictate solutions.Has to remain in the problem domain, leaving the development team ‘space’ to explore different solutions.

Long turnaround. Quick turnaround.

Focus on what the requirements document said. In other words, output (Artifact) is a well written thorough requirements document.

Focus on the functionality of the developed software. In other words, output (Artifact) is the software that meets thebusiness needs.

   

In Gap Analysis approach, certain parameters need to assess to jump to a conclusion.

1. Listing out the key factors - Attributes, Competencies, Performance levels etc of the present situation.2. Listing out factors which need to achieve future objectives.3. Highlighting the identified gaps which need to be plugged.

Gap analysis forces companies to act upon to handle the future shocks with care and responsibility.

GAP Analysis is one of the best approaches to streamline organisations to think about improvement and enhancements of their processes.

Organisation need to acknowledge and approve the gaps being identified and act upon in the larger interest of an organisation to address future needs and current competencies.

In the Agile methods every iteration involves a team

working through a full software development cycle,

including planning, requirements analysis, design, coding,

unit testing, and acceptance testing when a working

product is demonstrated to stakeholders.

CONCLUSION:

Gap Analysis helps organisations in getting comprehensive outlook of an entire organization or respective function or process within the organization and to assess and reassure the current available resources which are apt to meet the future expectations, this result in the decreased project cost, and strict timelines on the other hand

GAPanalysis is an esteemed and most acceptable approach

which need to be followed by organizations at all levels of

hierarchy to get help in allocation of resources efficiently,

crisp planning the budgets and effective prioritizing the

needs and requirements.