BABOK

v3:

Whats new?

Agenda
Some history about BABoK
Quick overview of changes
Deep dive what has changed
Conclusions

BABOK Guide
Core product for IIBAserves as basis for all IIBA related services
including certification and competency model.

Globally recognized standard for business analysis:

Development began in 2004
First Major Release was v1.6 in 2006

Updated to v2 in 2009

Provides a framework for structuring business analysis activities.

Collective wisdom of many Business Analysis professionals, from all
around the world.
Every IIBA member gets a free of charge copy for his own use.
3

A first tangible change

BABoK 2.0 was 271 pages

BABoK 3.0 is 514 pages

So where do these new pages come from?

Framework

Techniques

Business Analysis Core

Concept Model (BACCM)

Changes &
Additions

15

Requirements vs
Design

Perspectives
Underlying
Competencies

- Agile
- Business Intelligence
- Information Technology
- Business Architecture
- Business Process Management

NEW

BUSINESS ANALYSIS KEY CONCEPTS

Business Analysis definition changed

BABoK 2.0
Business analysis is the set of
tasks and techniques used to
work as a liaison among
stakeholders in order to
understand the structure,
policies, and operations of an
organization,
and to recommend solutions
that enable the organization to
achieve its goals.

HELPS ORGANIZATION
ACHIEVE ITS GOALS

BABoK 3.0
Business analysis is the practice of enabling
change in an enterprise by defining needs
and recommending solutions that deliver
value to stakeholders. Business
analysis enables an enterprise to articulate
needs and the rationale for change, and to
design and describe solutions that can deliver
value. HELPS ORGANIZATION
7
CHANGE

Requirement definition changed

BABoK 2.0
A requirement is:
1. Condition of capability
needed by a stakeholder to
solve a problem or achieve
an objective.
2. A condition or capability
that must be met of
possessed by a solution or
solution component to
satisfy a contract, standard,
specification or other
formally imposed
documents.
3. A documented
representation of a
condition or 3. capability as
in 1) or 2).
IEEE definition

BABoK 3.0
A requirement is a usable
representation of a need. Requirements
focus on understanding what kind of
value could be delivered if a
requirement is fulfilled

Core Concepts and Unified Terminology

BACCM
6 core concepts kept
recurring
Creates common
language for BAs

Relevant from
enterprise strategy to
tactical implementation
9

It is important to expand the

object of many business
analysis activities from
'requirements' to BA
information' to ensure that
all inputs and outputs of
business analysis are subject
to the tasks and activities
described in the BABOK
Guide.
10

Perspectives
Agile

Information
Technology

Merely examples of
environments in
which a change
initiative can take
place.

Business Intelligence

Often combination of
perspectives is
needed for real-time
projects.

Business Process
Management

Good introduction for

newcomers

Business
Architecture

Handy checklist for

senior professionals

11

Requirements vs Designs
Requirements the
usable representation
of a need.
Problem domain
needs

reqs

Designs usable
representation of a
Solution. A new task
Define Design
Options has been
added to focus on
the BA work in
designing solutions

designs

Solution domain
12

Changes to

BUSINESS ANALYSIS FRAMEWORK KNOWLEDGE AREAS

13

Revised Knowledge Area Structure

Enterprise
Analysis

Requirements
Analysis

Elicitation
Solution Assessment
and Validation

Requirements
Management and
Communication
14

3. Business Analysis Planning and

Monitoring
BABoK 2.0

BABoK 3.0

15

4 Elicitation and Collaboration

BABoK 2.0

BABoK 3.0

16

5 Requirements Life Cycle

Management
BABoK 2.0

BABoK 3.0

17

6 Strategy Analysis
BABoK 2.0

BABoK 3.0

18

7 Requirements Analysis and

Design Definition
BABoK 2.0

BABoK 3.0

19

8 Solution Evaluation
BABoK 2.0

BABoK 3.0

20

Changes in task description

Purpose of the task
Description what the task at hand is
Inputs for the task
Elements key concepts BA needs to understand before he
performs a task

Guidelines and Tools New! Additional resources that might

be needed to perform the task at hand
Techniques that can be used
Stakeholders who are likely to participate

Outputs produced by performing a task

21

Changes to

TECHNIQUES & COMPETENCIES

22

Changes in naming, but not only

34

50

v2.0 Benchmarking Benchmarking and Market

Analysis
v2.0 Data Dictionary and Glossary split into two
techniques:
Data Dictionary
Glossary

v2.0 Structured Walkthrough Reviews

v2.0 Risk Analysis Risk Analysis and Management
v2.0 Scenarios and Use Cases Use Cases and
Scenarios
v2.0 Requirements Workshop Workshops

23

15 new Techniques
1 Backlog Management
2 Balanced Scorecard
3 Business Capability
Analysis
4 Business Case
5 Business Model Canvas
6 Collaborative Games
7 Concept Modelling
8 Data Mining
9 Decision Modelling

10 Financial Analysis
11 Mind Mapping
12 Prioritization
13 Process Analysis
14 Roles and Permissions
Matrix
15 Stakeholder List, Map, or
Personas

24

New competencies
Analytical Thinking and Problem Solving
NEWConceptual Thinking
NEWVisual Thinking

Behavioural Characteristics
NEWPersonal Accountability
NEWAdaptability Business Knowledge

Business Knowledge
NEWMethodology Knowledge
NEWNon-verbal Communication
NEWListening

Interactions Skills
NEWNegotiation and Conflict Resolution

Tools and Technology

NEWCommunication Tools and Technology
25

Competencies:
Removals and Additions
Behavioural Characteristics:
Personal Organizationrenamed and expanded Organization and
Time Management

Business Knowledge
Business Principles and Practicesrenamed Business Acumen

Communication Skills
Oral Communicationsrenamed Verbal Communication

Interaction Skills
Facilitation and Negotiationsplit competencies and renamed
Facilitation

Software Applications (Version 2.0 name) is now Tools and

Technology (Version 3 name)
General-Purpose Applicationsrenamed Office Productivity Tools
and Technology
Specialized Applicationsrenamed Business Analysis Tools and
Technology
26

Conclusions
BABoK 3.0 has become broadly applicable, and as consequence
more generic

Perspectives help with tailoring BABoK to different application

domains
Business Analysts can be responsible for design too, however
remember that design belongs to the solution domain.
Common terminology with Business Analysis Core Concept
Model
Remember it is not only about requirements!
27

Shaping the Global Direction

of Business Analysis
Experience the new BABOK Guide v3
iiba.org