Learning and Knowledge Management

Introduction & Business

Analysis Key Concepts

Accenture CSI Confidential Material. Do not duplicate or distribute

Module Objectives

At the end of this module, you will be able to describe:

• The structure and purpose of the BABOK® Guide

• The role and responsibilities of a business analyst

• Relationships between different knowledge areas

• Exam blueprint of Level 1, Level 2 and Level 3

• Key terminologies

• Business Analysis Core Concept Model™ (BACCM™)

• Types of requirements and stakeholders

• Requirements vs. Design

Copyright © 2016 Accenture All Rights Reserved.

Agenda
• Purpose of the BABOK® Guide

• What is Business Analysis?

• Who is a Business Analyst?

• Structure of the BABOK® Guide

• The Business Analysis Core Concept

Model™

• Key Terms

• Requirements Classification Schema

• Stakeholders

• Requirements and Designs

Copyright © 2016 Accenture All Rights Reserved.

 Purpose of the BABOK® Guide

Copyright © 2016 Accenture All Rights Reserved.

Purpose of the BABOK® Guide
The primary purpose of the BABOK® guide is to define the profession of business
analysis and provide a set of commonly accepted practices.
• It helps practitioners discuss and define the skills necessary to effectively perform business analysis
work
• BABOK® Guide also helps people who work with and employ business analyst to understand skills
and knowledge they should expect from a skilled practitioner
• It is a common framework for all perspectives, describing business analysis tasks that are performed
to
properly analyze a change or evaluate the necessity for a change
• The BABOK® Knowledge Areas describe the practice of business analysis as it is applied within
the boundaries of a project or throughout enterprise evolution and continuous improvement

Business Analysis Beyond

Projects
Copyright © 2016 Accenture All Rights Reserved.
 What is Business Analysis?

Copyright © 2016 Accenture All Rights Reserved.

What is Business Analysis?
Business Analysis is the practice of enabling change in an enterprise by defining needs
and recommending solutions that deliver value to the stakeholders. It enables an
enterprise to articulate needs and rationale for change, and to design and describe
solutions that can deliver value.
• Business Analysis is performed on a variety of initiatives within an enterprise - strategic, tactical
or operational
• Business Analysis may be performed within the boundaries of a project or throughout enterprise
evolution
and continuous improvement
• It can be used to understand the current state, to define the future state, and determine activities to
move from current state to future state
• It can be performed from a diverse array of perspectives:
• Agile
• Business Intelligence
• Information Technology
• Business Architecture
• Business Process Management

Copyright © 2016 Accenture All Rights Reserved.

 Who is a Business Analyst?

Copyright © 2016 Accenture All Rights Reserved.

Who is a Business Analyst
A business analyst in any person who performs business analysis tasks described in the
BABOK guide, irrespective of the job title or organizational role.
• Business Analysts are responsible for:
• Discovering, synthesizing and analyzing information from a variety of enterprise sources,
including tools, processes and documentation, and stakeholders
• Eliciting actual needs of the stakeholders – which frequently involves investigating and clarifying
their
expressed desires – in order to determine underlying issues and causes
• Aligning the designed and delivered solutions with the needs of the stakeholders

• Activities performed by a Business

Job Titles for a Business Analyst:
Analyst:
• Understanding enterprise problems and goals • Business Architect
• Analyzing needs and solutions • Business Systems Analyst
• Devising strategies • Data Analyst
• Driving change • Enterprise Analyst
• Management Consultant
• Facilitating stakeholder collaboration
• Process Analyst
• Product Manager
• Product Owner
• Requirements Engineer
• Systems Analyst

Copyright © 2016 Accenture All Rights Reserved.

 Structure of the BABOK® Guide

Copyright © 2016 Accenture All Rights Reserved.

Structure of BABOK® Guide
• The core is composed of BA tasks organized into knowledge areas (KA)
BABOK Core • Knowledge Area – A collection of logically (but not sequentially) related tasks
Content • Task – Describe specific activities that accomplish the purpose of the associated
KAs This structure is elaborated more in the next two slides

Business Analysis • Define the key terms needed to understand all other content, concepts and ideas within the BABOK® guide
Key Concepts

Underlying • Provide a description of the behaviors, characteristics, skills, knowledge, and personal qualities that support effective
practice of business analysis
Competencies • The UC has the following structure – Purpose, Definition, Effectiveness Measures

• Provide additional information on ways that a task may be performed

Technique • Multiple techniques or in conjunction with other techniques can be applied to perform a task
• Techniques have the structure – Purpose, Description, Elements and Usage Considerations
s

• Describe views of business analysis and help BAs working from different point of view to better perform BA tasks
specific to the context of the initiative
• Perspectives included in BABOK® – Agile, Business Intelligence, Information Technology, Business Architecture,
Perspectives Business Process Management
• Perspectives follow the structure – Change Scope, Business Analysis Scope, Methodologies, Approaches and
Techniques, Underlying Competencies, Impact on KA

Copyright © 2016 Accenture All Rights Reserved.

Structure of BABOK® Guide
Knowledge Areas

Knowledge areas represent areas of specific business analysis expertise that encompass
several tasks
Business
Analysis
Planning and
Monitoring

Requirements
Strategy Analysis and
Analysis Design Definition

Elicitation and Requirements Life

Collaboration Cycle
Management

Solution Evaluation

Copyright © 2016 Accenture All Rights Reserved.

Structure of BABOK® Guide
Tasks
• A discrete piece of work that may be performed formally or informally as part of business analysis. The
definition of a given task is universally applicable to business analysis efforts, independent of the
initiative type.
• Tasks are grouped into knowledge areas. Business analysts perform tasks from all knowledge
areas sequentially, iteratively, or simultaneously.
• Tasks may be performed in any order.

Each task in the BABOK® Guide is presented in the following format:

• Purpose
• Description
• Inputs
• Elements
• Guidelines/Tools
• Techniques
• Stakeholders
• Outputs

Copyright © 2016 Accenture All Rights Reserved.

 Exam Blueprint of
Level 2 and Level 3

Copyright © 2016 Accenture All Rights Reserved.

Exam Blueprint of Level 2 and Level 3
Level 1, 2 & 3

• Level 1 certificate recognizes the foundational knowledge of individuals entering the field of business
analysis.
• Level 2 recognizes BA professionals who have two to three years of business analysis experience.
Current professionals with their CCBA® designation will be grandfathered into Level 2.
• Level 3 recognizes BA professionals who manage and lead with over 5 years of business analysis
experience. Current professionals with their CBAP® designation will be grandfathered into Level 3.
• Aligned to the BABOK® Guide v3 Knowledge Areas, the Level 1, Level 2 and 3 exams will be weighted as
follows:
Domain Level 1 Level 2 Level3

Business Analysis Planning and Monitoring 5% 12% 14%

Elicitation and Collaboration 20% 20% 12%

Requirements Life Cycle Management 20% 18% 15%

Strategy Analysis 5% 12% 15%

Requirements Analysis and Design 24% 32% 30%

Definition
Solution Evaluation 1% 6% 14%

Copyright © 2016 Accenture All Rights Reserved.

 Business Analysis
Core Concept Model™
(BACCM™)

Copyright © 2016 Accenture All Rights Reserved.

Business Analysis Core Concept Model™
(BACCM™)
The Business Analysis Core Concept Model™ (BACCM™) is a conceptual framework for
Business Analysis. It encompasses
• What business analysis is
• What business analysis means to those performing business analysis tasks regardless of
industry, methodology and organizational level

BACCM can be used to –

• Describe the profession and domain of business analysis
• Communicate about business analysis with common terminology
• Evaluate relationship of key concepts in business analysis
• Perform better business analysis by holistically evaluating the relationships among these six
concepts

Six Core Concepts: ===> More details in subsequent slides

• Each concept is an idea fundamental to the practice of business analysis
• All concepts and equal and necessary
• Each concept is defined by other five concepts
• No single concept holds greater importance or significance over the other

Copyright © 2016 Accenture All Rights Reserved.

Business Analysis Core Concept Model™
(BACCM™)
Core Concepts can be used by
business analysts to consider
the quality and completeness of
the work being done.

Copyright © 2016 Accenture All Rights Reserved.

 Key
Terms

Copyright © 2016 Accenture All Rights Reserved.

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

• Business Analysis is described ad defined as the practice of enabling change in an

enterprise by defining needs and recommending solutions that deliver value to stakeholders.

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

• Design is a usable representation of a solution. Design focuses on understanding how

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

• Enterprise is a system of one or more organizations and the solutions (organizational

capabilities) they use to pursue a shared set of common goals. An enterprise may include any
number of business, government, or any other type of organization

Copyright © 2016 Accenture All Rights Reserved.

Key Terms
• Organization is an autonomous group of people under the management of a
single individual or board, that works towards common goals and objectives.

• Plan is a proposal for doing or achieving something. Plans describe a set of events,
the dependencies among the events, the expected sequence, the schedule, the
results or outcomes, the materials and resources needed, and the stakeholders
involved.

• Requirement is a usable representation of a need. Requirements focus on

understanding what kind of value could be delivered if a requirement is fulfilled.

• Risk is the effect of uncertainty on the value of a change, a solution, or the enterprise.

Copyright © 2016 Accenture All Rights Reserved.

 Requirements
Classification Schema

Copyright © 2016 Accenture All Rights Reserved.

Requirements Classification Schema
Requirements Classification:
• Business requirements: Statements of goals, objectives, and outcomes that describe why a change
has been initiated
• Stakeholder requirements: Describe the needs of stakeholders that must be met in order to achieve
the business requirements. They may serve as a bridge between business and solution requirements.
• Solution requirements: Describe the capabilities and qualities of a solution that meets the stakeholder
requirements. Solution requirements can be divided into two sub-categories:
a) Functional requirements: Describe the capabilities that a solution must have in terms of the
behavior
and information that the solution will manage.
b) Non-functional requirements or quality of service requirements: 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.
• Transition requirements: Describe the capabilities that the solution must have and the conditions 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.

Copyright © 2016 Accenture All Rights Reserved.

 Stakeholders

Copyright © 2016 Accenture All Rights Reserved.

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

• Business analyst • Operational support

• Customer • Project manager
• Domain subject matter expert • Regulator
• End user • Sponsor
• Implementation subject matter • Supplier
Expert • Tester

Copyright © 2016 Accenture All Rights Reserved.

 Requirements and
Designs

Copyright © 2016 Accenture All Rights Reserved.

Requirements and Design
Requirements are focused on the need; designs are focused on the solution.

The following table provides some basic examples of how information may be viewed as either a
requirement or a design

Requirement Design
View six months sales data across A sketch of a dashboard.
multiple Organizational units in a single
view.
Reduce amount of time required to pick and Process model.
pack a customer order.
Record and access a medical patient’s history. Screen mock-up showing
specific data fields.
Develop business strategy, goals, Business Capability Model.
and objectives for a new business.
Provide information in English and French. Prototype with text displayed
in English and French.

Copyright © 2016 Accenture All Rights Reserved. Copyright © 2014 Accenture All rights 5
Requirements and Design
• A requirement (or set of requirements) may be used to define a design. That design may then be used
to elicit additional requirements that are used to define more detailed designs.

Business
Requirements
Why do
I want
it?

Transition Stakeholder
Cycle continues until
Requirements requirements are met Requirements
What are the What are the
conditions? needs?

Solution
Requirements
What do I
want?

Requirements and
Design Cycle

Copyright © 2016 Accenture All Rights Reserved.

 Copyright © 2014 Accenture All rights reserved.

Questions
Thank
You