Learning path
Business Analyst learning path: everything to study, topic by topic
Comprehensive business analyst assessment covering requirements engineering, process analysis, data analysis and visualization, stakeholder management, solution design, Agile delivery, and expert BA practice including enterprise architecture and strategic roadmapping.
Short answer
To learn Business Analyst, work through 7 modules and 20 topics in the order they build on each other. It starts with Requirements Engineering, then moves on to Process Analysis and Data Analysis & Visualization. Use the map as a checklist, or measure your level and study only what is missing.
What you will study
Topics are grouped by module. Open one to see its objectives and key concepts.
1 · Requirements Engineering3 topics
Requirements Elicitation
Techniques for gathering requirements from stakeholders including interviews, workshops, observation, prototyping, surveys, and document analysis
Objectives
- Select appropriate elicitation techniques based on stakeholder type and project context
- Plan and facilitate a structured requirements workshop
Key concepts
- interviews
- workshops
- observation
- prototyping
- surveys
- document analysis
- elicitation planning
BRD & FRD Writing
Authoring Business Requirements Documents and Functional Requirements Documents with proper structure, traceability, and version control
Objectives
- Author a BRD that aligns business objectives to measurable requirements
- Build a requirements traceability matrix linking BRD to FRD to test cases
Key concepts
- BRD structure
- FRD structure
- requirements traceability matrix
- version control
- sign-off process
- scope statement
User Stories & Acceptance Criteria
Writing effective user stories in the standard format with INVEST criteria and testable acceptance criteria using Given-When-Then
Objectives
- Write user stories that satisfy all INVEST criteria
- Define acceptance criteria that are testable and unambiguous
Key concepts
- user story format
- INVEST criteria
- acceptance criteria
- Given-When-Then
- story mapping
- story splitting
2 · Process Analysis3 topics
BPMN Process Modeling
Creating business process models using BPMN 2.0 notation including pools, lanes, gateways, events, and subprocess decomposition
Objectives
- Model an end-to-end business process using correct BPMN 2.0 notation
- Decompose complex processes into subprocesses for clarity
Key concepts
- BPMN 2.0
- pools and lanes
- gateways
- events
- sequence flows
- subprocesses
Gap Analysis
Performing current-state vs future-state analysis, identifying gaps, and recommending solutions to bridge process, capability, and technology gaps
Objectives
- Conduct a structured fit-gap analysis for a system implementation
- Prioritize gaps by business impact and recommend actionable solutions
Key concepts
- current state
- future state
- gap identification
- fit-gap analysis
- capability mapping
- remediation planning
Use Case Diagrams
Creating UML use case diagrams with actors, use cases, system boundaries, include/extend relationships, and detailed use case specifications
Objectives
- Model system interactions using UML use case diagrams with correct notation
- Write detailed use case specifications with preconditions, flows, and exceptions
Key concepts
- actors
- use cases
- system boundary
- include relationship
- extend relationship
- use case specification
3 · Data Analysis & Visualization3 topics
Data Modeling (ERD)
Creating entity-relationship diagrams, defining entities, attributes, relationships, cardinality, and normalization to support solution design
Objectives
- Design an ERD that accurately represents business domain entities and relationships
- Apply normalization rules to eliminate data redundancy
Key concepts
- entities
- attributes
- relationships
- cardinality
- normalization
- primary keys
- foreign keys
SQL Querying for Analysis
Writing SQL queries for business analysis including JOINs, aggregation, subqueries, window functions, and data validation
Objectives
- Write SQL queries to extract and validate business data for analysis
- Use aggregation and window functions to identify trends and anomalies
Key concepts
- SELECT statements
- JOINs
- GROUP BY
- HAVING
- subqueries
- window functions
- data validation queries
Dashboard Design
Designing effective business dashboards with KPI selection, visualization best practices, data storytelling, and audience-appropriate layouts
Objectives
- Design a dashboard that communicates key business metrics to the target audience
- Select appropriate visualization types for different data patterns and messages
Key concepts
- KPI selection
- visualization types
- data storytelling
- dashboard layout
- drill-down hierarchy
- audience segmentation
4 · Stakeholder Management3 topics
Stakeholder Mapping
Identifying, analyzing, and mapping stakeholders using power-interest grids, RACI matrices, influence diagrams, and communication planning
Objectives
- Build a stakeholder map using a power-interest grid and define engagement strategies
- Create a RACI matrix that clarifies decision-making authority across project roles
Key concepts
- power-interest grid
- RACI matrix
- influence diagram
- communication plan
- stakeholder register
- engagement strategy
Facilitation Techniques
Facilitating productive meetings, workshops, and JAD sessions using structured techniques including brainstorming, affinity diagrams, MoSCoW prioritization, and conflict resolution
Objectives
- Plan and facilitate a JAD session that produces actionable decisions
- Apply MoSCoW prioritization to resolve conflicting stakeholder requirements
Key concepts
- JAD sessions
- brainstorming
- affinity diagrams
- MoSCoW prioritization
- dot voting
- conflict resolution
UAT Planning
Planning and coordinating user acceptance testing including test strategy, test case design, defect triage, entry/exit criteria, and sign-off procedures
Objectives
- Design a UAT plan with clear entry/exit criteria and defect triage process
- Coordinate business users through UAT execution and formal sign-off
Key concepts
- UAT strategy
- test cases
- entry criteria
- exit criteria
- defect triage
- sign-off procedure
5 · Solution Design3 topics
Feasibility Studies
Conducting technical, operational, economic, and schedule feasibility assessments to evaluate solution alternatives and make go/no-go recommendations
Objectives
- Evaluate solution alternatives across four feasibility dimensions
- Present a structured go/no-go recommendation to executive stakeholders
Key concepts
- technical feasibility
- operational feasibility
- economic feasibility
- schedule feasibility
- solution alternatives
- go/no-go decision
Cost-Benefit Analysis
Quantifying costs and benefits of proposed solutions including ROI, NPV, payback period, TCO, and intangible benefit assessment
Objectives
- Build a cost-benefit model with ROI, NPV, and payback period calculations
- Quantify intangible benefits and present a compelling business case
Key concepts
- ROI
- NPV
- payback period
- TCO
- intangible benefits
- sensitivity analysis
Root Cause Analysis
Applying root cause analysis techniques including 5 Whys, Ishikawa diagrams, Pareto analysis, and fault tree analysis to diagnose business problems
Objectives
- Apply structured RCA techniques to identify systemic causes of business problems
- Design corrective actions that address root causes rather than symptoms
Key concepts
- 5 Whys
- Ishikawa diagram
- Pareto analysis
- fault tree analysis
- causal loop
- corrective action
6 · Agile & Project Delivery3 topics
Agile/Scrum BA Practices
Performing the BA role within Scrum teams including sprint ceremonies, continuous discovery, incremental elaboration, and collaboration with Product Owner
Objectives
- Integrate BA activities seamlessly into Scrum sprint ceremonies
- Balance just-enough upfront analysis with incremental elaboration during sprints
Key concepts
- sprint planning
- backlog refinement
- continuous discovery
- incremental elaboration
- definition of ready
- definition of done
Backlog Management
Structuring and maintaining a product backlog including epic decomposition, prioritization frameworks (WSJF, value vs effort), and dependency mapping
Objectives
- Decompose epics into well-sized stories and prioritize using WSJF
- Manage cross-team dependencies and communicate release scope to stakeholders
Key concepts
- epic decomposition
- WSJF
- value vs effort
- dependency mapping
- backlog grooming
- release planning
Change Management
Managing organizational change through impact assessment, training plans, communication strategies, adoption metrics, and resistance management
Objectives
- Design a change management plan using the ADKAR model for a major system rollout
- Measure adoption and proactively address resistance patterns
Key concepts
- change impact assessment
- training plan
- communication strategy
- adoption metrics
- resistance management
- ADKAR model
7 · Expert BA Practice2 topics
Enterprise Architecture Basics
Understanding enterprise architecture frameworks (TOGAF, Zachman), business capability models, application portfolio rationalization, and technology roadmaps from a BA perspective
Objectives
- Map business capabilities to applications and identify rationalization opportunities
- Contribute to enterprise architecture decisions using BA domain knowledge
Key concepts
- TOGAF
- Zachman framework
- business capability model
- application portfolio
- technology roadmap
- architecture decision records
Strategic Roadmapping
Building multi-quarter product and transformation roadmaps aligned to business strategy, OKR cascading, investment theme prioritization, and portfolio-level trade-offs
Objectives
- Build a multi-quarter roadmap that cascades from corporate OKRs to delivery epics
- Facilitate portfolio-level investment trade-offs across competing business initiatives
Key concepts
- product roadmap
- transformation roadmap
- OKR cascading
- investment themes
- portfolio prioritization
- horizon planning
Levels: Junior, Mid, Senior, and Expert
Explain it in your own words
Graded by AI · no account · 1 questionNo options to guess from: you write, the AI grades against the topic's rubric and tells you what level your answer reads at.
Already studying Business Analyst?
The assessment measures topic by topic, and your plan skips what you already know.
Open to read. An account is only needed to be measured.
Frequently asked questions
Where should I start studying Business Analyst?
Start with Requirements Engineering: Requirements Elicitation, BRD & FRD Writing, and User Stories & Acceptance Criteria. The map orders topics by what they depend on, so each one prepares the next.
How long does a full Business Analyst assessment take?
A full assessment of this path takes about 50 minutes. Study time depends on where you start; a diagnostic shows which topics you can skip.
Do I need an account to use this page?
No. The map, objectives and key concepts are open. You only need an account to be measured, get your gap by topic and receive a plan.