Introduction to

Business Analysis
CCBATM/CBAPTM CERTIFICATION BOOTCAMP
According to BABOK® v3
 Declaration
IIBA®, the IIBA® logo, BABOK® Guide and Business Analysis Body of Knowledge® are registered
trademarks owned by International Institute of Business Analysis. These trademarks are used with
the express permission of International Institute of Business Analysis.
Learning Objectives

What is Business Analysis

Who is a Business Analyst
Business Analysis Beyond Projects
Business Analysis Core Concept Model (BACCM)

Business Analysis Perspectives

Business Analysis Knowledge Areas
Business Analysis Underlying Competencies

Requirements Classification
Requirements and Designs

Who is a Stakeholder

Key Terms
What is Business Analysis

➢ 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

➢ It can be performed within the boundaries of a project or throughout enterprise evolution and
continuous improvement

➢ Can be used to understand the current state, to define future state and determine activities
required to move from the current to future state
➢ Business analysis is performed on a variety of initiatives within an enterprise. Initiatives may
be strategic, tactical, or operational
The Business Analyst

Any individual who performs business analysis tasks described in the BABOK®
Guide, no matter their job title or organizational role.
The Business Analyst

Business analysts are responsible for discovering, synthesizing, and analyzing information.

• Understanding enterprise problems and goals

The activities that • Analyzing needs and solutions
business analysts
perform include: • Devising strategies
• Driving change, and
• Facilitating stakeholder collaboration
The Business Analyst…

As a CHANGE ENABLER
✓ Understands the Business context, Stakeholders
✓ Elicits Needs and Concerns
✓ Define the Problems, creates alignment
✓ Identifies the root causes
✓ Defines the solution, Innovates
✓ Describes the solutions, assesses the full impact and risks
✓ Communicates and ‘sells’ (for consensus) thesolution
✓ Motivates people to work towards the solutions
✓ Works with the people to implement the solution
✓ Validates the solution
✓ Evaluates the performance of the solution
Common BA Job Titles

Business Business Enterprise

Data Analyst
Architect Systems Analyst Analyst

Management Product
Process Analyst Product Owner
Consultant Manager

Pre-Sale
Requirement
Systems Analyst Support Analyst Consultant/
Engineer
Analyst

Business
Customer
Transformation Business Analyst
Insight Analyst
Analyst
Business Analysis Beyond Project
 Business Analysis Beyond Project
How does a Business Analyst support Change?

Board Strategy Strategic BA as Management Consultant to support setting company

controls
strategy/goals

Business needs Change BA to understand Business Requirements and deliver Business Cases
(Cost/ Benefit) to recommend suitable projects

Sponsor provides Budget BA to support effort estimation for all product and process related
Hands over to/assigns

changes, in order to determine required budget

Project Manager Project BA to manage the product scope (requirements) within project scope
manages

Product/Process BA to recommend and conceptualize solutions, interface Dev to

Developer creates
Business. E.g. as acting Product Owner

Tester assure Product/Process BA to support testing and quality assurance, assess and
validate the solution, support transition
Project

End User use Product/Process BA to assess performance, determine delivered value – after
project end.
Business Analysis Core Concept Model

BACCM, defines a conceptual framework for the business

analysis profession.

• Each core concept is defined by the other five

core concepts and cannot be fully understood
until all the concepts are understood.
Business Analysis Core Concept Model

Describe the profession and domain of business analysis

Communicate about business analysis with a common

terminology

The BACCM can be used to: Evaluate the relationships of key concepts in business
analysis

Perform better business analysis by holistically evaluating

the relationships among these six concepts, and

Evaluate the impact of these concepts and

relationships at any point during a work effort in order to
establish both a foundation and a path forward
Business Analysis Core Concept Model

Core Concept Description

CHANGE The act of transformation in response to a need.

NEED A problem or opportunity to be addressed.
SOLUTION A specific way of satisfying one or more needs in a context.

STAKEHOLDER A group or individual with a relationship to the change, the need,

or the solution.
CONTEXT The circumstances that influence, are influenced by, and
provide understanding of the change. Changes occur within a
context.
VALUE The worth, importance, or usefulness of something to a
stakeholder within a context.

Value is potential or realized returns, gains, and improvements.

Questions Through The BACCM

While planning or performing a task or technique, business analysts can consider how each core
concept is addressed by asking questions such as:

➢ What are the kinds of changes we are doing?

➢ What are the needs we are trying to satisfy?
➢ What are the solutions we are creating or changing?
➢ Who are the stakeholders involved?
➢ What do stakeholders consider to be of value?
➢ What are the contexts that we and the solution are in?
Knowledge Areas

Business Analysis Planning 1 Elicitation and Collaboration

and Monitoring (BAPM) 2 (E&C)

6 Requirements Life Cycle

KNOWLEDGE
Solution Evaluation (SE) AREAS Management (RLM)
3

Requirements Analysis and 5

Design Definition (RADD) 4 Strategy Analysis (SA)
Business Analysis Knowledge Areas

1. Plan & Monitor the BA effort,

Identify the stakeholders

2. Model the needs for change,

4. 4. Detail the strategy, verify,
5.
the future state & the change validate, describe the solution
strategy characteristics

2. Understand stakeholder’s 6. Manage & maintain the strategy,

3.
needs and concerns Communicate and obtain
consensus
5.
6. Assess the performance and
value of a solution.
Tasks

A task is a discrete piece of work that may be performed formally or informally as part of business Analysis.

01 02 03 04

Purpose Description Inputs Elements

Task

05 06 07 08

Guidelines and tools Techniques Stakeholders Output

Tasks and Knowledge Areas

Knowledge Area Number of Tasks

Business Analysis Planning & 5
Monitoring (BAPM)
Elicitation & Collaboration 5
Requirement Lifecycle 5
Management
Strategy Analysis 4
Requirement Analysis & Design 6
Definition
Solution Evaluation 5
Total Number of Tasks 30
Perspectives

Business Analysis can be performed from a diverse array of perspectives.

Perspectives

Perspective Description
Agile Agile Mindset, Principles and Values,
Progressive elaboration
Business Intelligence Transformation, Integration and
Enhancement of data into valuable
information for better decision making

Business Architecture Business Transformation across

structures, operations etc.
Information Technology Change on IT Systems in the organization,
upgrade, replace or enhance IT systems

Business Process Management Development and improvement of

business processes across multiple
functions within the organization
Underlying Competencies

Key Elements

1. Purpose: Describes why it is beneficial for business analyst to have this underlying competency.

2. Definition: Describes the skills and expertise involved in the application of this competency.

3. Effectiveness Measures: Describes how to determine whether a person is demonstrating skills in

this underlying competency.

The Underlying Competencies

Analytical Behavioral Business Communication Interaction Tools and

Thinking and Characteristics Knowledge Skills Skills Technology
Problem Solving

• Creative • Ethics • Business • Verbal • Facilitation • Office

Thinking • Personal Acumen Communication • Leadership Productivity
&
• Decision Making Accountability • Industry • Non - Verbal Influencing Tools &
Learning • Trustworthiness Knowledge Communication • Teamwork Technology
• Problem Solving • Organization and • Organization • Written • Negotiation • Business
& Conflict
Systems Time Knowledge Communication Resolution Analysis Tools
Thinking Management • Solution • Listening • Teaching & Technology
• Conceptual • Adaptability Knowledge • Communication
Thinking • Methodology Tools &
• Visual Thinking Knowledge Technology
Techniques

Techniques provide additional information on ways that a task may be performed.

Key elements include:

1. Purpose: What the technique is used for and the circumstances under which it is most likely
to be applicable.
2. Description: What the technique is and how it is used.
3. Elements: Key concepts that are needed to understand how to use the technique.
4. Usage Considerations: Conditions under which the technique may be effective.
Techniques

✓ Acceptance and Evaluation Criteria ✓ Business Rules Analysis

✓ Backlog Management ✓ Collaborative Games
✓ Balanced Scorecard ✓ Concept Modeling
✓ Benchmarking and Market Analysis ✓ Data Dictionary
✓ Brainstorming ✓ Data Flow Diagrams
✓ Business Capability Analysis ✓ Data Mining
✓ Business Case ✓ Data Modeling
✓ Business Model Canvas ✓ Decision Analysis
Techniques

✓ Decision Modeling ✓ Item Tracking

✓ Document Analysis ✓ Lessons Learned
✓ Estimation ✓ Metrics and KPIs
✓ Financial Analysis ✓ Mind Mapping
✓ Focus Groups ✓ Non-Functional Requirements Analysis
✓ Functional Decomposition ✓ Observation
✓ Glossary ✓ Organizational Modeling
✓ Interface Analysis ✓ Prioritization
✓ Interviews
Techniques

✓ Process Analysis ✓ Sequence Diagrams

✓ Process Modeling ✓ Stakeholder List, Map, Personas

✓ Prototyping ✓ State Modeling

✓ Reviews ✓ Survey or Questionnaire

✓ Risk Analysis and Management ✓ SWOT Analysis

✓ Roles and Permissions Matrix ✓ User Stories

✓ Root Cause Analysis ✓ Vendor Assessment

✓ Scenarios & Use Cases ✓ Workshops

✓ Scope Modeling
Business Analysis Key Concepts

Business Analysis Core Concept Model™ (BACCM™): Defines a conceptual framework for the
business analysis profession.

Key Terms: Provides definitions of essential concepts, which are highlighted because of their
importance to the BABOK® Guide.

Requirements Classification Schema: Identifies levels or types of requirements that assist the
business analyst and other stakeholders in categorizing requirements.

Stakeholders: Defines roles, and characteristics of groups or individuals participating in or

affected by the business analysis activities within a change.

Requirements and Designs: Describes the distinction between— and the importance of—
requirements and designs as they relate to business analysis.
Key Terms

Describes as the practice of enabling change in an enterprise by defining

Business Analysis
needs and recommending solutions that deliver value to stakeholders.

Business Analysis Refers to the broad and diverse sets of information that business analysts
Information analyze, transform, and report.

A design is a usable representation of a solution. Design focuses on

Design
understanding how value might be realized by a solution if it is built.

An enterprise is a system of one or more organizations and the

Enterprise
solutions they use to pursue a shared set of common goals.
Key Terms

Organization An autonomous group of people under the management of a single

individual or board, that works towards common goals and objectives.

Plans describe a set of events, the dependencies among the events, the
Plan expected sequence, the schedule, the results or outcomes, the materials
and resources needed, and the stakeholders involved.

Requirement A requirement is a usable representation of aneed.

Business analysts collaborate with other stakeholders to identify,

Risk assess, and prioritize risks, and to deal with those risks by altering the
likelihood of the conditions or events that lead to the uncertainty.
Requirements Classification Schema

Statements of goals, objectives, and outcomes that describe why a

Business requirements
change has been initiated.

Describe the needs of stakeholders that must be met in order to

Stakeholder requirements
achieve the business requirements.
Requirements Classification Schema

Describe the capabilities and qualities of a solution that meets the

stakeholder requirements.
➢ Functional requirements: Describe the capabilities that a solution
Solution requirements must have in terms of the behavior and information that the solution
will manage
➢ Non-functional requirements (QoS): Do not relate directly to the
behavior of functionality of the solution, but rather describe conditions
under which a solution must remain effective or qualities that a solution
must have

Describe the capabilities that the solution must have and the conditions
Transition requirements the solution must meet to facilitate transition from the current state to
the future state, but which are not needed once the change is
complete.
Stakeholders

A stakeholder is an individual or group that a business analyst is likely to interact with directly or
indirectly.
Stakeholders
For the purpose of the BABOK® Guide, the generic list of stakeholders includes the following roles:
Business analyst

Tester Customer

Supplier
Domain subject
matter expert

Sponsor

End-users

Regulator

Implementation
Project subject matter
manager Operational experts
support
Stakeholders

Business Analyst: Responsible and Accountable for the execution of all BA activities.
Customer: Uses or may use products or services produced by the enterprise.
Domain Subject Matter Expert: An individual with in-depth knowledge of a topic relevant to the
business need or solution scope.
End User: Can include all participants in a business process, or who use the product or solution.
Implementation Subject Matter Expert: Any stakeholder who has specialized knowledge regarding
the implementation of one or more solution components.
Operational Support: Responsible for the day-to-day management and maintenance of a system,
solution or product.
Stakeholders

Project Manager: Responsible for managing the work required to deliver a solution that meets
a business need or ensuring that the project's objectives are met.
Regulator: Regulators are responsible for the definition and enforcement of standards and policy.
Sponsor: Responsible for initiating the effort to define a business need and develop a solution
that meets that need.
Supplier: A stakeholder outside the boundary of a given organization or organizational unit.
Tester: Responsible for determining how to verify that the solution meets the requirements
defined by the business analyst, as well as conducting the verification process.
Requirements and Designs
Key Notes

NEEDS REQUIREMENTS

SOLUTION DESIGN

➢ Eliciting, Analyzing, Validating, and Managing Requirements are key activities of business
analysis.
➢ Business analysts are also responsible for the definition of design in initiatives.
➢ Classification as a REQUIREMENT or a DESIGN may become less significant as the
business analyst's work progresses to a greater understanding of and eventual fulfillment of
the need.
➢ Business analysis can be complex and recursive. A requirement (or set of requirements) may
be used to define a design.
Requirements and Designs

Requirements Designs
View six months sales data across multiple A sketch of a dashboard
organizational units in a single view

Reduce amount of time required Process model

to pick and pack a customer order

Record and access a medical patient’s Screen mock-up showing specific

history data fields.

Develop business strategy, goals, and Business Capability Model

objectives for a new business

Provide information in English and French Prototype with text

displayed in English and
French
Requirements and Designs Life cycle
 Thank You!

Copyright © Knowledgehut., All rights reserved

Confidential Information, intended for approved distribution list of Knowledgehut