Online Mind Mapping and Brainstorming

Create your own awesome maps

Online Mind Mapping and Brainstorming

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account? Log In

BABOK®3 Guide study guide mind map by Mind Map: BABOK®3 Guide study guide
mind map
5.0 stars - 49 reviews range from 0 to 5

BABOK®3 Guide study guide mind map

IIBA®, the IIBA® logo, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis. Trademarks are properties of the holders, who are not affiliated with mind map author.

Business Analysis is the practice of enabling change in an organizational context, by defining needs and recommending solutions that deliver value to stakeholders. The set of tasks and techniques that are used to perform business analysis are defined in A Guide to the Business Analysis Body of Knowledge® (BABOK®Guide).

BABOK v1.6 was published in 2006

BABOK v2 was published in 2009

BABOK v3 was published in 2015


Business Analyst

Change Control Board (CCB)


Domain Subject Matter Expert (SME)

End User

Implementation Subject Matter Expert (SME) - examples

Change Manager

Configuration Manager

Database Administrator

Developer / Software Engineer

Information Architect

Organizational Change Management Professionals

Project Librarian

Solution Architect

System Architect


Usability Analyst

Usability Professional

Operational Support

Project Manager





Techniques (46)

Acceptance and Evaluation Criteria Definition (10.1)

Backlog Management (10.2)

Balanced Scorecard (10.3)

Benchmarking and Market Analysis (10.4)

Brainstorming (10.5)

Business Capability Analysis (10.6)

Business Model Canvas (10.7)

Business Rules Analysis (10.8)

Collaborative Game (10.9)

Data Dictionary (10.10)

Data Flow Diagrams (10.11)

Data Modeling (10.12)

Decision Analysis (10.13)

Decision Modeling (10.14)

Document Analysis (10.15)

Estimation (10.16)

Focus Groups (10.17)

Functional Decomposition (10.18)

Glossary (10.19)

Interface Analysis (10.20)

Interviews (10.21)

Item Tracking (10.22)

Lessons Learned (10.23)

Metrics and Key Performance Indicators (KPIs) (10.24)

Non-functional Requirements Analysis (10.25)

Observation (10.26)

Organization Modeling (10.27)

Priortization (10.28)

Process Analysis (10.29)

Process Modeling (10.30)

Prototyping (10.31)

Reviews (10.32)

Risk Analysis and Management (10.33)

Roles and Permissions Matrix (10.34)

Root Cause Analysis (10.35)

Scenarios (10.36)

Scope Modeling (10.37)

Sequence Diagrams (10.38)

Stakeholder List, Map, or Personas (10.39)

State Modeling (10.40)

Survey or Questionnaire (9.41)

SWOT Analysis (10.42)

User Cases (10.43)

User Stories (10.44)

Vendor Assessment (10.45)

Workshops (10.46)

Knowledge Areas (6)

Business Analysis Planning and Monitoring (Chapter 3)

Elicitation and Collaboration (Chapter 4)

Requirements Life Cycle Management (Chapter 5)

Strategy Analysis (Chapter 6)

Requirements Analysis and Design Definition (Chapter 7)

Solution Evaluation (Chapter 8)

Underlying Competencies (Chapter 9)

Tasks (30)

Task characteristics

Has a purpose

Has inputs

Is complete

Uses techniques

Involves stakeholders

Has outputs / results

Tasks may be performed formally or informally.

Tasks may be performed in any order.

Tasks are grouped into Knowledge Areas (6)

Business Analysis Planning and Monitoring (Chapter 3), 3.1 Plan Business Analysis Approach, 3.2 Plan Stakeholder Engagement, 3.3 Plan Business Analysis Information Management, 3.4 Plan Business Analysis Governance, 3.5 Identify Business Analysis Performance Improvements

Elicitation and Collaboration (Chapter 4), 4.1 Prepare for Elicitation, 4.2 Conduct Elicitation, 4.3 Confirm Elicitation Results, 4.4 Communicate Business Analysis Information, 4.5 Manage Stakeholder Collaboration

Requirements Life Cycle Management (Chapter 5), 5.1 Trace Requirements, 5.2 Maintain Requirements, 5.3 Prioritize Requirements, 5.4 Assess Requirements Changes, 5.5 Gain Consensus

Strategy Analysis (Chapter 6), 6.1 Analyze Current State, 6.2 Define Future State, 6.3 Assess Risks, 6.4 Define Change Strategy

Requirements Analysis and Design Definition (Chapter 7), 7.1 Specify and Model Requirements, 7.2 Verify Requirements, 7.3 Validate Requirements, 7.4 Define Requirements Architecture, 7.5 Define Solution Options, 7.6 Analyze Potential Value and Recommend Solution

Solution Evaluation (Chapter 8), 8.1 Measure Solution Performance, 8.2 Analyze Performance Measures, 8.3 Assess Solution Limitations, 8.4 Assess Enterprise Limitations, 8.5 Recommend Actions to Increase Solution Value

What's new in the upcoming BABOK®3? 25.03.2014, IIBA Austria Chapter Meeting

Underlying Competencies of Business Analyst (6)

Analytical Thinking and Problem Solving

Behavioral Characteristics

Business Knowledge

Communication Skills

Interaction Skills

Software Applications

The Business Analysis Core Concept Model™ (BACCM™)

The Business Analysis Core Concept Model™ (BACCM™) - Business Analysis Framework (a.k.a. The Turtle)

6 core recurring concepts

Uniting a community of practitioners requires common terminology

6 major questions (six Core Concepts) need to be answered (central questions in business analysis)

Change, What is the kind of change we're doing?, A controlled transformation of the organization / enterprise.

Need, What are the need we're trying to satisfy?, A problem, opportunity, or constraint with potential value to a stakeholder.

Solution, What are the solutions we're trying to satisfy?, A specific way of satisfying one or more needs in a context.

Value, What do stakeholders consider to be of value?, The worth, importance, or usefulness of something to a stakeholder within a context.

Stakeholder, Who are the stakeholders involved?, A group or individual with a relationship to the change or the solution.

Context, What is the context in which we and the solution are in?, The circumstances that form the setting for a change and allows for further understanding and assessment of the change.

Perspectives (5)

What is it?

Perspectives describe specialized disciplines within the practice of business analysis. A Perspective is a set of behaviours, terminology, and attitudes used by a business analyst within their specific type of business analysis work.

Perspectives have the following structure

Change Scope

Business Analysis Scope

Impact on Knowledge Areas

Methodologies and Techniques

Underlying Competencies


Business Intelligence

Information Technology

Business Architecture

Business Process Management

Interactive BABOK®3 Glossary

Interactive BABOK®3 Glossary

BABOK®3 consists of: 6 Knowledge Areas, 30 Tasks, 46 Techniques, 6 Underlying Competencies of Business Analyst, 1 Business Analysis Core Concept Model (BACCM), 5 Perspectives.

Download BABOK®3 Knowledge Areas vs Techniques (PDF)

Requirements Classification Schema

Business requirements

Stakeholder requirements

Solution requirements

Transition requirements

This freeware, non-commercial mind map (aligned with the newest version of BABOK®) was carefully hand crafted with passion and love for learning and constant improvement as well for promotion the BABOK® and business analysis profession and as a learning tool for candidates wanting to gain CBAP® qualification. (please share, like and give feedback - your feedback and comments are my main motivation for further elaboration. THX!)

Questions / issues / errors? What do you think about my work? Your comments are highly appreciated. Please don't hesitate to contact me for :-) Mirosław Dąbrowski, Poland/Warsaw.


BABOK V3 Promotional Vide

BABOK v3 Demystified