In this presentation, I am going to provide you a glimpse of what’s inside IIBA BABOK guide version 3. Version 3 of the guide has been released recently. It’s possible that you might not have laid your hands on to it so far.

1. IIBA BABOK Guide v3
What’s inside?

2. Core/Key Concepts
Knowledge Areas and Tasks
Underlying Competencies
Techniques
Perspectives
BABOK® v3 Guide Architecture
Chapter 2
Chapter 3-8
Chapter 9
Chapter 10
Chapter 11
Chapter 1 - Introduction
Appendix A to D

3. BABOK® v3 Guide – Summary
BABOK v3 Elements Count
Number of pages 514
Knowledge Areas 6
Tasks 30
Underlying Competencies 6/29
Techniques 50
Perspectives 5

4. BABOK® Knowledge Areas

5. BABOK 3 & Knowledge Areas
 Knowledge areas are covered from chapter 3 to 8
 Knowledge areas are decomposed into tasks
 Tasks as well as Knowledge areas are described as process
 Each task is described and explained using a standard template

6. Task 1
Knowledge
Areas
Task..n
Purpose
Description
Inputs
Elements
Guidelines/Tools
Techniques
Stakeholders
Outputs
Knowledge Areas and Tasks

7. BA Core
Concepts

8. Core Concept Model
 All the core concepts have equal weightage
 Six core concepts constitute the BABOK BACCM model
 BACCM was conceptualized in May 2011 when BABOK v3 was kicked off
 The first iteration had 4 concepts, Value & Context were added later

9. Core Concept Model
Need
 A problem, opportunity or constraint with potential value to a stakeholder (s)
 Need can be thought of as the reason which starts a project.
Example - The need to automate the sales, marketing & customer service processes.

10. Core Concept Model
Solution
 A way to address the need of the stakeholder (s) for the given organization,
scenario and geography etc. (Context is important)
 Organizational needs can only be satisfied or addressed through a solution
Example: Implementing a Software as a service (SaaS) CRM system, rather
than a COTS (commercial off the shelf) CRM product.

11. Core Concept Model
Change
 A change is needed to successfully address the need of the stakeholders, the
overall effort of taking the organization from unimplemented state to a
transformed state (improved state)
 A change has to take place in the organization to address the need
Example – This change refers to the fact that a solution implementation may need
a mindset change of employees as they will shift from manual system to an
automated system.

12. Core Concept Model
Context
The background, budget, timelines, organization structure may influence the
way change is to be brought about
Example: Extending the CRM example in the solution section. If Software as a service
(SaaS) CRM system is suitable for Organization A, it is possible that a customized software
is more suitable for Organization B. The reason can be very specialized business processes
for organization B as compared to the almost standard business processes in organization
A.

13. Core Concept Model
Value
 Value can be seen as potential or realized returns, gains, and
improvements.
 The value is an anticipated outcome of implementing a solution.
 Value can be tangible or intangible
Example – By implementing a CRM solution, a business can look forward to
increase its revenue or to improve customer service standards. This is what is
meant by “Value”.

14. Core Concept Model
Stakeholder
 A stakeholder is an individual or group who can influence the project or can
get influenced by the project as a user.
 The stakeholders can be from the customer organization, the solution provider
or an external organization.
Example – In our example of CRM solution, the stakeholders can be
marketing manager, Marketing head, you as a business analyst, the project
manager and so on.

15. 15
THANKS!
Any questions?
You can contact us at
▸ info@techcanvass.com
▸ 022-40155 175
▸ 7738 7731 08
www.techcanvass.com