Business

Analysis
Fundamentals
By Leila Hamid
VentureDive
Intern-BA 2020
Agenda
Outline of Topics

1. Who Is BA?

2. Responsibilities And Behavioral Characteristics Of

BA.

3. Role Of A BA In Project Phases

4. Tools For BA

5. Elements for Agile Projects

Who is BA?

A Brief Introduction
The business analyst is responsible for eliciting the
actual needs of stakeholders which frequently
involves investigating and clarifying their expressed
desires.
Responsibilities Behavioral
of a BA Characteristics
• Understanding enterprise problems and • Ethics
goals, • Personal Accountability
• Analyzing needs and solutions, • Trustworthiness
• Driving change, • Time Management and Organizational Skills
• Facilitating stakeholder collaboration • Adaptability
 Role of a BA in Project
DeploymentPhase
20%
Phases
RequirementPhase
30% Requirement phase
To take the requirements

Design phase
TestingPhase
Develop flows & wireframes
20%
Development phase
Discuss user stories with the developer

Testing phase
Verification of final release
DesignPhase
DevelopmentPhase 20%
Deployment phase
Creation of technical documents, product manuals etc.
15%
Must have tools for
a BA
Wireframing Project Management Tool
• Balsamiq • Basecamp

• Figma • Jira

• Trello

User Flows Meeting tools

• Overflow • Google meet

• Draw.io • Zoom

• Visio • Slack

• MS Teams
Elements for Agile Projects
Techniques
 Requirements elicitation techniques
 Wireframing/Prototyping
 Product backlogs
 User stories
 Mapping techniques
 Decision modeling
 Retrospective
1. Backlog Management
Purpose:
“The backlog is used to record, track, and prioritize remaining
work items”

Benefits:
 what work items should be formally included in the backlog.
 how to describe the work items.
 how the work items should be tracked.
2. Backlog Refinement
Backlog Refinement is used to ensure there is enough detail
and clarity for items in the backlog.

Backlog Refinement Meeting

An ordered list of features, requirements, The output of the refinement meeting is
or items. backlog items ready for the next iteration.

Backlog Item Definition of Ready

An item on the backlog which represents Set of criteria the team agrees must be
one or more requirements satisfied to consider an item "ready" for
the next iteration
3.Wireframes

 Wireframes are facets of the early stage of the

design process

 Wireframes typically do not include any styling,

color, or graphics.
4. Prototyping

Purpose
used to create a working or non-working model of
a possible solution.

 It works by providing an early model of the final

result, known as a prototype
5. User Stories- INVEST
Criteria
6. Personas
Personas are fictional characters or archetypes that
exemplify the way that typical users interact with a
solution
7. User Stories
Purpose
A user story represents a small, concise statement of functionality
or quality needed to deliver value to a specific

CARD

CONFIRMATION CONVERSATION

3C Format BDD Format

8. Acceptance Criteria
Acceptance criteria define the boundaries of a
user story.
9. Job Stories
Job Stories are used to represent a product backlog item (PBI)
or requirement in terms of a job to be done by a stakeholder.
10. Story Mapping
Story Mapping is used to assist in creating understanding of product
functionality, the flow of usage, and to assist with prioritizing product
delivery.
11. Impact Mapping
Impact organizational goals Mapping is used to align stakeholders with
and the creation of customer value.

Benefits:
 Gives large context with little information.
 Impact maps can be created in a short period of time.
12. Decision Modeling
Decision models show how data and knowledge are combined to make a specific decision.

Most common models are Decision Table and Decision Matrix.

Decision Table: Decision Tree

 Each row is a rule. Decision trees are used to represent a set of business rules.
 Each column represents one of the conditions of that  Each path on a decision tree leaf node is a single rule.
rule.  Each level in the tree represents a specific data element.
 13. State Modeling
State modeling is used to specify the different states of a part
of the solution throughout a life cycle, in terms of the events
that occur.
1. State
2. State Transition
3. State Diagram
14. Requirements and Design Cycle
15. Minimal Viable Product
It is used to prioritize the allocation of resources and to increase the speed of
organizational learning.

Benefits:
 Reduces cost and risk by gaining customer feedback before engaging in a full
solution.
 Tests actual usage scenario instead of relying on market research.
16. Retrospectives
Retrospectives are used to continuously improve by reflecting on
1. What went well.
2. What could be better
3. What to improve the processes.

Benefits:
 Allows continuous improvement of the team.
 Empowers the team.
 BABOK V3
A GUIDE TO THE BUSINESS
ANALYSIS BODY OF
KNOWLEDGE

Agile Extension to References

the BABOK V2
BOOKS