Scribd
Upload
38 views27 pages

Babok Review l0 Upd v1.0

BABOK review L0

Uploaded by

riki.nurhidayat91
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
38 views27 pages

Babok Review l0 Upd v1.0

BABOK review L0

Uploaded by

riki.nurhidayat91
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 27

Business Analysis Body Of Knowledge

Lesson 0—BABOK Guide v3

BABOK® is a registered trademark owned by International Institute of Business Analysis.

Copyright 2014, Simplilearn, All rights


BABOK v2 is 271 pages BABOK v3 is 514 pages
What’s New!?
• Improved readability, consistency, and usability
• Revised definitions of “Business Analysis” and “Requirements”
• Inclusion of the Business Analysis Core Concept Model™
(BACCM™)
• Inclusion of Perspectives which describe specialized ways in
which business analysis professionals provide unique value to the
enterprise
• New techniques that have emerged in the practice of business
analysis
• Expanded scope of the role of business analysis in creating better
business outcomes
• New and expanded Underlying Competencies to better reflect
the diverse skill sets of the business
Business Analysis
BABOK v2:
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 v3:
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.
HELPS ORGANIZATION CHANGE
Requirements Definition

BABOK v2:
1. A condition or capability needed by a stakeholder to solve a problem or
achieve an objective.
2. A condition or capability that must be met or 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 capability as in 1 or 2.

BABOK v3:
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.
Business Analysis Competency Model

6 Knowledge
Areas

6 Underlying
Competencies

50 Techniques
Business Analysis Core Concept Model™

• Need • Change • Solution• Value• Stakeholder• Context


BABOK covers these Perspectives
• Agile
• Business Intelligence
• Information Technology
• Business Architecture
• Business Process Management

Each perspective covers:


• Change Scope
• Business Analysis Scope
• Frameworks, Methodologies,
Techniques
• Underlying competencies
• Impact on Knowledge areas
Five Perspectives
“Provide ways to approach business analysis work in a
more focused manner suitable to the content.”
Agile

Strategy Analysis

Elicitation &
Collaboration

Requirements Analysis & Solution Evaluation


Design Definition
Agile
Business Analysis Positions
• As a team member participating
in all sprint activities
• As a product owner, possibly
temporarily, creating and
grooming the backlog
• As an advisor to the team to the
product owner supporting all
business activities from vision to
deployment
Agile
Business Analysis Outcomes
• Open collaboration
• Product vision and
strategic alignment
• Just enough and Just-in-
time documentation
• User Stories
.
Agile BA Opportunity
Individuals and interactions over processes and tools
BA opportunity: Collaboratewithin a smallerteam and with much fewer
stakeholders on a continuous basis, early and often (discussion of incomplete
Agile Manifesto

thoughts and concepts are acceptable), using simple tools during conversations
Working software over comprehensivedocumentation
BA opportunity: Understandthat scope is smaller with less of a need for formal
documentation but still balancing this with governance and other business policy or
regulatoryaudit needs
Customer collaboration over contract negotiation
BA Opportunity: Working toward a shared definition of “done”, understanding that
you don’t get into the detail until you have to (just-in-time analysis), and focusing on
business value
Responding to change over following a plan
BA Opportunity: Acknowledge that changes will occur and are acceptable,think
customer first
www.agilemanifesto.org
Business Intelligence

Data Enterprise Data View Decision Business


Integration Support Intelligence
Operational

Data System Dashboard


Sources
Transformation Analytics
Scorecard
External
Quality
Management BIG DATA Delivery Queries

Internal Warehouse
Reports

Alerts
Data Marts Analytics Platform
Business Intelligence Business
Analysis Positions
• As a primary liaison between
stakeholders & solution providers
• As a functional analyst for data mining
and predictive analytic techniques
• As a data analyst for defining source
systems
• As a data modeler or architect defining
information structures
Business Intelligence Business
Analysis Outcomes
• Business process coverage
• Decision models
• Source logical data model and quality
assessment
• Target logical data model
• Data dictionaries (source and target)
• Business analytic requirements
• Dashboards
• Prescriptive and predictive models
• Output specifications
• Decision support architecture
• Data transformation requirements
Information Technology Sample
Predictive Approach
Information Technology
Business Analysis Positions
• As a primary liaison between technical team
and business group users
• As a subject matter expert on current software
implementation
• As a systems analyst with domain knowledge
• As an experienced usability expert
• As a business process owner with in- depth
business capabilities and processes
• As a technical person or software package
representative understanding the nuances of
the software
Information Technology Business
Analysis Outcomes
• Based on solution
development life cycle
• Requirements
(various types and states)
• Use cases
• Analysis results
(gap, interfaces processes,
etc.)
• Various business and scope
models
Business Architecture
Business Business
Architecture Scenarios
Blueprints

Merger
Acceptable Concerns &
Artifacts Interests
Globalization

Divestiture
BusinessArchitecture
Knowledgebase New Product
Reusable Views
Artifacts Investment

Cost
Reduction
Business Architecture Business
Analysis Positions
• As a business architect to provide a
holistic and understandable view of the
entire enterprise from a functional and
organizational context
• As a strategic advisor, to support groups
that need to make decisions regarding
changes to the enterprise
• As a solution architect, to understand the
interconnectivity between the different
architectural layers and to make
enterprise wide solution
recommendations
Business Architecture Business
Analysis Outcomes
• Alignment maps (strategies, capabilities, etc.)
• Blueprints (value streams, organizational charts,
process maps, etc.)
• Architectural views
Business Process Management
1.
Process
Identification
Process Architecture
Current State Model
Insights on 2.
Executed Model
Process
Discovery
6.
3.
Process
Process
Monitoring &
Analysis
Controlling
Ready Process Model Opportunities Identified

5. 4.
Process Process
Implementation Redesign
Future State Model
Business Process Management
Business Analyst Position
• As a process architect or analyst that
has continuous responsibility for
modeling and optimizing business
processes
• As a process modeler that
documents the
• business processes with a repository
Business Process Management
Business Analyst Outcomes
• Business models and associated rules
• Performance measures and assessment
• Business decisions
V3 has 50 Techniques – up from 34 Techniques in v2

You might also like