WELCOME

Certified Business Analysis

Manage
Develop
Prepare

Professional
Direct
Need

Study Guides
BY:
PM Tutor
 COURSE STRUCTURE
BA Key Analysis &
Introduction
Concept Monitoring
Module 1
Module 2 Module 3
Manage
Develop
Prepare
Direct
Need

Elicitation & Requirement Strategy

Collaboration Lifecycle Analysis
Module 4 Module 5 Module 6
 COURSE STRUCTURE
Requirements Solution
Analysis Evaluation
Module 7 Module 8
Manage
Develop
Prepare
Direct
Need

Underlying
Techniques Perspectives
Competencies
Module 10 Module 11
Module 9
 COURSE OBJECTIVE
At the end of this course, you will
understand what business analysis is all
about, why it is essential to the success of
Manage
Develop
Prepare

any project and how to perform it on your

Direct
Need

projects...
 Certified Business Analysis Professional

Elicitation and
Manage
Develop
Prepare

Collaboration
Direct
Need

Module 4
 MODULE OBJECTIVE

Prepare for Elicitation

Manage
Develop

Conduct Elicitation
Prepare
Direct
Need

Confirm Elicitation Results

Communicate Business Analysis Information

Manage Stakeholder Collaboration

 The BACCM Elicitation and Collaboration

Prepare
Conduct
Develop
Direct
 Elicitation and Collaboration
The Elicitation and Collaboration knowledge area is composed of the following tasks:

• Prepare for Elicitation: involves ensuring that the stakeholders have the information they need to
provide and that they understand the nature of the activities they are going to perform

• Conduct Elicitation: describes the work performed to understand stakeholder needs and identify
Conduct

potential solutions that may meet those needs.

Develop

Prepare
Direct

• Confirm Elicitation Results: involves ensuring that stakeholders have a shared understanding of
the outcomes of elicitation, that elicited information is recorded appropriately, and that the business
analyst has the information sought from an elicitation activity.

• Communicate Business Analysis Information: provides stakeholders with the information they
need, at the time they need it.

• Manage Stakeholder Collaboration: describes working with stakeholders to engage them in the
overall business analysis process and to ensure that the business analyst can deliver the outcomes
needed.
Conduct Elicitation and Collaboration Input/Output Diagram
Develop

Prepare
Direct
 Prepare for Elicitation
Purpose
The purpose of Prepare for Elicitation is to understand the scope of the elicitation activity, select
appropriate techniques, and plan for (or procure) appropriate supporting materials and resources.

Description
Conduct
Develop

Business analysts prepare for elicitation by defining the desired outcomes of the activity, considering

Prepare
Direct

the stakeholders involved and the goals of the initiative.

Inputs
Needs: guides the preparation in terms of the scope and purpose of elicitation activities. Elicitation
can be used to discover the needs, but in order to get started there must be some need that exists—
even if it has not yet been fully elicited or understood.

• Stakeholder Engagement Approach: understanding stakeholders' communication and

collaboration needs helps plan and prepare appropriate and effective elicitation events.
Conduct Prepare for Elicitation Input/Output Diagram
Develop

Prepare
Direct
 Elements
.1 Understand the Scope of Elicitation
To determine the type of business analysis information to be discovered during the elicitation
activity and the techniques that may be used.

.2 Select Elicitation Techniques

In most cases, multiple techniques are used during an elicitation activity. The techniques used
Conduct
Develop

depend on cost and time constraints, the types of business analysis information sources and their

Prepare
Direct

access, the culture of the organization, and the desired outcomes.

3 Set Up Logistics are planned prior to an elicitation activity.

.4 Secure Supporting Material Business analysts identify sources of information that are needed to
conduct the elicitation activity. There might be a great deal of information needed to conduct
elicitation including people, systems, historical data, materials and documents.

.5 Prepare Stakeholders Business analysts may need to educate stakeholders on how an elicitation
technique works or what information is needed. It may be helpful to explain an elicitation technique
to stakeholders not involved in the activity to help them understand the validity and relevance of the
information elicited.
 Guidelines and Tools
• Business Analysis Approach: sets the general strategy to be used to guide the business
analysis work. This includes the general methodology, types of stakeholders and how they
should be involved, list of stakeholders, timing of the work, expected format and level of
detail of elicitation results, and identified challenges and uncertainties.
Conduct
Develop

Prepare
• Business Objectives: describe the desired direction needed to achieve the future state.
Direct

They can be used to plan and prepare elicitation events, and to develop supporting
materials.

• Existing Business Analysis Information: may provide a better understanding of the goals
of the elicitation activity, and aid in preparing for elicitation.

• Potential Value: describes the value to be realized by implementing the proposed future
state, and can be used to shape elicitation events.
 Techniques

• Brainstorming
• Data Mining
• Document Analysis
Conduct
Develop

Prepare
• Estimation
Direct

• Interviews
• Mind Mapping
• Risk Analysis and Management
• Stakeholder List, Map, or Personas
 Stakeholders
• Domain Subject Matter Expert: provides supporting materials as well as guidance
about which other sources of business analysis information to consult. May also help to
arrange research, experiments, and facilitated elicitation

Project Manager: ensures that the appropriate people and resources are available to
Conduct
Develop

Prepare
conduct the elicitation.
Direct

• Sponsor: has the authority to approve or deny a planned elicitation event, and to
authorize and require the participation of specific stakeholders.

Outputs
• Elicitation Activity Plan: used for each elicitation activity. It includes logistics, scope of
the elicitation activity, selected techniques, and supporting materials.
 Conduct Elicitation
The purpose of Conduct Elicitation is to draw out, explore, and identify information
relevant to the change.

Description
There are three common types of elicitation:
• Collaborative: involves direct interaction with stakeholders, and relies on their
experiences, expertise, and judgment.

Conduct
Confirm

Prepare
Direct

• Research: involves systematically discovering and studying information from materials

or sources that are not directly known by stakeholders involved in the change.
Stakeholders might still participate in the research. Research can include data analysis of
historical data to identify trends or past results.

• Experiments: involves identifying information that could not be known without some
sort controlled study (Proof of Concept)

Inputs
• Elicitation Activity Plan: includes the planned elicitation activities and techniques,
activity logistics (for example, date, time, location, resources,
 Conduct Elicitation Input/Output Diagram

Conduct
Confirm

Prepare
Direct
 Elements

.1 Guide Elicitation Activity Understanding the proposed

representations of business analysis information, which were defined
in planning, helps ensure that the elicitation activities are focused on
producing the intended information at the desired level of detail.

Conduct
Confirm

Prepare
Direct

.2 Capture Elicitation Outcomes Conducting elicitation is frequently

iterative and takes place in a series of sessions—in parallel or in
sequence—according to the scope of the elicitation activity
 Guidelines and Tools
• Business Analysis Approach: influences how each elicitation activity is performed, as
it identifies the types of outputs that will be needed based on the approach.

• Existing Business Analysis Information: may guide the questions posed during
elicitation and the approach used to draw out information from various stakeholders.

Conduct
Confirm

Prepare
• Stakeholder Engagement Approach: provides collaboration and communication
Direct

approaches that might be effective during elicitation.

• Supporting Materials: includes any materials to prepare both the business analyst and
participants before elicitation, as well as any information, tools, or equipment to be
used during the elicitation.
 Techniques

• Benchmarking and Market Analysis • Business Rules Analysis

• Brainstorming • Interviews
• Collaborative Games • Mind Mapping
Confirm

• Concept Modelling • Observation

Prepare
Direct

• Data Mining • Process Analysis

• Data Modelling. • Process Modelling
• Document Analysis • Prototyping:
• Focus Groups • Survey or Questionnaire
• Interface Analysis • Workshops
 Techniques
• Benchmarking and Market Analysis: used as a source of business analysis information by comparing a specific
process, system, product, service, or structure with some external baseline, such as a similar organization or baseline
provided by an industry association. Market analysis is used to determine what customers want and what competitors
provide.

• Brainstorming: used to generate many ideas from a group of stakeholders in a short period, and to organize and
prioritize those ideas.

• Business Rules Analysis: used to identify the rules that govern decisions in an organization and that define,
constrain, or enable organizational operations.
Confirm

Prepare
Direct

• Collaborative Games: used to develop a better understanding of a problem or to stimulate creative solutions.

• Concept Modelling: used to identify key terms and ideas of importance and define the relationships between them.

• Data Mining: used to identify relevant information and patterns.

• Data Modelling: used to understand entity relationships during elicitation.

• Document Analysis: used to review existing systems, contracts, business procedures and policies, standards, and
regulations.

• Focus Groups: used to identify and understand ideas and attitudes from a group.

• Interface Analysis: used to understand the interaction, and characteristics of that interaction, between two entities,
such as two systems, two organizations, or two people or roles.
 Techniques
• Interviews: used to ask questions of stakeholders to uncover needs, identify problems, or discover
opportunities.

• Mind Mapping: used to generate many ideas from a group of stakeholders in a short period, and to organize
and prioritize those ideas.

• Observation: used to gain insight about how work is currently done, possibly in different locations and in
different circumstances.
Confirm

Prepare
Direct

• Process Analysis: used to understand current processes and to identify opportunities for improvement in
those processes.

• Process Modelling: used to elicit processes with stakeholders during elicitation activities.

• Prototyping: used to elicit and validate stakeholders' needs through an iterative process that creates a model
of requirements or designs.

• Survey or Questionnaire: used to elicit business analysis information, including information about customers,
products, work practices, and attitudes, from a group of people in a structured way and in a relatively short
period of time.

• Workshops: used to elicit business analysis information, including information about customers, products,
work practices, and attitudes, from a group of people in a collaborative, facilitated way.
 Stakeholders
• Customer: will provide valuable business analysis information during elicitation.
• Domain Subject Matter Expert: has expertise in some aspect of the situation and can provide
the required business analysis information. Often guides and assists the business analyst in
identifying appropriate research sources, and may help to arrange research, experiments, and
facilitated elicitation.

• End User: the user of existing and future solutions, who should participate in elicitation.

Conduct
Confirm

Prepare
Direct

• Implementation Subject Matter Expert: designs and implements a solution and provides
specialist expertise, and can participate in elicitation by asking clarifying questions and offering
alternatives.

• Sponsor: authorizes and ensures that the stakeholders necessary to participate in elicitation
are involved.
• Any stakeholders: could have relevant knowledge or experience to participate in elicitation
activities.

Outputs
• Elicitation Results (unconfirmed): captured information in a format that is specific to the
elicitation activity.
 Confirm Elicitation Results

Purpose
The purpose of Confirm Elicitation Results is to check the information gathered during an elicitation
session for accuracy and consistency with other information.

Description

Conduct
Analysis

Confirm
Prepare
Elicited information is confirmed to identify any problems and resolve them before resources are
committed to using the information. This review may discover errors, omissions, conflicts, and
ambiguity. The elicitation results can be compared against their source and other elicitation results
to ensure consistency.

Inputs
• Elicitation Results (unconfirmed): capture information in a format specific to the elicitation activity.
Analysis
Confirm Elicitation Results

Prepare
Confirm
Conduct
 Elements
.1 Compare Elicitation Results Against Source Information Task Conduct
Elicitation describes sources from which elicitation results may be derived,
including documents and stakeholder knowledge. The business analyst may
lead follow-up meetings where stakeholders correct the elicitation results.

Conduct
Analysis

Confirm
Prepare
.2 Compare Elicitation Results Against Other Elicitation Results Business
analysts compare results collected through multiple elicitation activities to
confirm that the information is consistent and accurately represented. As
comparisons are drawn, business analysts identify variations in results and
resolve them in collaboration with stakeholders. Comparisons may also be
made with historical data to confirm more recent elicitation results.
 Guidelines and Tools

• Elicitation Activity Plan: used to guide which alternative

sources and which elicitation results are to be compared.

Conduct
• Existing Business Analysis Information: can be used to
Analysis

Confirm
Prepare
confirm the results of elicitation activities or to develop
additional questions to draw out more detailed information.
 Techniques
• Document Analysis: used to confirm elicitation results against source
information or other existing documents.

• Interviews: used to confirm the business analysis information and to

confirm that the integration of that information is correct.

Conduct
Analysis

Confirm
Prepare
• Reviews: used to confirm a set of elicitation results. Such reviews could
be informal or formal depending on the risks of not having correct,
useful, and relevant information.

• Workshops: used to conduct reviews of the drafted elicitation results

using any level of formality. A predetermined agenda, scripts, or scenario
tests may be used to walk through the elicitation results, and feedback is
requested from the participants and recorded.
 Stakeholders
• Domain Subject Matter Experts: people with substantial knowledge, experience,
or expertise about the business analysis information being elicited, or about the
change or the solution, help to confirm that elicitation results are correct, and can
help to identify omissions, inconsistencies and conflicts in elicitation results.

Conduct
Analysis

Confirm
Prepare
• Any stakeholder: all types of stakeholders may need to participate in confirming
elicitation results.

Outputs
• Elicitation Results (confirmed): integrated output that the business analyst and
other stakeholders agree correctly reflects captured information and confirms that
it is relevant and useful as an input to further work.
 Communicate Business Analysis Information
Purpose
The purpose of Communicate Business Analysis Information is to ensure stakeholders have a shared
understanding of business analysis information

Description

Conduct
Business analysts must communicate appropriate information to stakeholders at the right time and
Manage

Confirm
Prepare
Analysis
in formats that meet their needs. Consideration is given to expressing the information in language,
tone, and style that is appropriate to the audience.

Inputs
• Business Analysis Information: any kind of information at any level of detail that is used as an
input or output of business analysis work. Business analysis information becomes an input for this
task when the need is discovered to communicate the information to additional stakeholders.

• Stakeholder Engagement Approach: describes stakeholder groups, roles, and general needs
regarding communication of business analysis information.
 Communicate Business Analysis Information
Input/Output Diagram

Conduct
Manage

Confirm
Prepare
Analysis
 Elements
.1 Determine Objectives and Format of Communication Business analysis information
packages may be prepared for a number of reasons

Consideration is given to the best way to combine and present the materials to convey a
cohesive and effective message to one or more stakeholder groups. Packages can be

Conduct
Manage

Confirm
Prepare
Analysis
stored in different online or offline repositories, including documents or tools.

.2 Communicate Business Analysis Package The purpose of communicating the business

analysis package is to provide stakeholders with the appropriate level of detail about the
change so they can understand the information it contains.
 Guidelines and Tools

• Business Analysis Approach: describes how the various types of

information will be disseminated rather than what will be disseminated. It
describes the level of detail and formality required, frequency of the
communications, and how communications could be affected by the

Conduct
Manage

Confirm
Prepare
Analysis
number and geographic dispersion of stakeholders.

• Information Management Approach: helps determine how business

analysis information will be packaged and communicated to stakeholders.
 Techniques

• Interviews: used to individually communicate information to stakeholders.

• Reviews: used to provide stakeholders with an opportunity to express

feedback, request required adjustments, understand required responses and

Conduct
actions, and agree or provide approvals.
Manage

Confirm
Prepare
Analysis
• Workshops: used to provide stakeholders with an opportunity to express
feedback and to understand required adjustments, responses, and actions.
They are also useful for gaining consensus and providing approvals. Typically
used during group collaboration.
 Stakeholders
• End User/Customer: needs to be communicated with frequently so they are aware of relevant
business analysis information.

Domain Subject Matter Expert: needs to understand the business analysis information as part of
confirming and validating it throughout the change initiative.

• Implementation Subject Matter Expert: needs to be aware of and understand the business

Conduct
Manage

Confirm
Prepare
Analysis
analysis information, particularly requirements and designs, for implementation purposes.

• Tester: needs to be aware of and understand the business analysis information, particularly
requirements and designs for testing purposes.
• Any stakeholder: all types of stakeholders will likely need to be communicated with at some
point during the change initiative.

Outputs
• Business Analysis Information (communicated): business analysis information is considered
communicated when the target stakeholders have reached an understanding of its content and
implications.
 Manage Stakeholder Collaboration
Purpose
The purpose of Manage Stakeholder Collaboration is to encourage stakeholders to work towards a common
goal.

Description
Business analysis work lends itself to many collaboration opportunities between groups of stakeholders on

Conduct
the business analysis work products. Stakeholders hold various degrees of influence and authority over the

Confirm
Manage
Prepare
Analysis
approval of work products, and are also an important source of needs, constraints, and assumptions.

As the business analysis work progresses, the business analyst identifies stakeholders, confirms their roles,
and communicates with them to ensure that the right stakeholders participate at the right times and in the
appropriate roles.

Inputs
• Stakeholder Engagement Approach: describes the types of expected engagement with stakeholders and
how they might need to be managed.
• Business Analysis Performance Assessment: provides key information about the effectiveness of business
analysis tasks being executed, including those focused on stakeholder engagement.
Manage Stakeholder Collaboration
Input/Output Diagram

Conduct
Confirm
Manage
Prepare
Analysis
 Elements
.1 Gain Agreement on Commitments Stakeholders participate in business analysis activities that may require
time and resource commitments. The business analyst and stakeholders identify and agree upon these
commitments as early in the initiative as possible. The specific details of the commitments can be
communicated formally or informally, as long as there is explicit understanding of the expectations and
desired outcomes of the commitment.

.2 Monitor Stakeholder Engagement Business analysts monitor the participation and performance of

Conduct
Confirm
Manage
Prepare
Analysis
stakeholders to ensure that: • the right subject matter experts (SMEs) and other stakeholders are participating
effectively, • stakeholder attitudes and interest are staying constant or improving, • elicitation results are
confirmed in a timely manner, and • agreements and commitments are maintained. Business analysts
continually monitor for such risks as: • stakeholders being diverted to other work, • elicitation activities not
providing the quality of business analysis information required, and • delayed approvals.

.3 Collaboration Stakeholders are more likely to support change if business analysts collaborate with them and
encourage the free flow of information, ideas, and innovations. Genuine stakeholder engagement requires
that all stakeholders involved feel that they are heard, their opinions matter, and their contributions are
recognized.
 Guidelines and Tools
• Business Analysis Approach: describes the nature and level of collaboration required from each
stakeholder group to perform planned business analysis activities.

• Business Objectives: describe the desired direction needed to achieve the future state. They can
be used to focus diverse stakeholders on a common vision of the desired business outcomes.

Conduct
Confirm
Manage
Prepare
Analysis
• Future State Description: defines the desired future state and the expected value it delivers which
can be used to focus diverse stakeholders on the common goal.

• Recommended Actions: communicating what should be done to improve the value of a solution
can help to galvanize support and focus stakeholders on a common goal.

• Risk Analysis Results: stakeholder-related risks will need to be addressed to ensure stakeholder
collaboration activities are successful.
 Techniques
• Collaborative Games: used to stimulate teamwork and collaboration by temporarily immersing
participants in a safe and fun situation in which they can share their knowledge and experience on
a given topic, identify hidden assumptions, and explore that knowledge in ways that may not occur
during the course of normal interactions.

• Lessons Learned: used to understand stakeholders' satisfaction or dissatisfaction, and offer them

Conduct
Confirm
Manage
Prepare
Analysis
an opportunity to help improve the working relationships.

• Risk Analysis and Management: used to identify and manage risks as they relate to stakeholder
involvement, participation, and engagement.

• Stakeholder List, Map, or Personas: used to determine who is available to participate in the
business analysis work, show the informal relationships between stakeholders, and understand
which stakeholders should be consulted about different kinds of business analysis information.
 Stakeholders

• All stakeholders: all types of stakeholders who might be involved in

collaboration during change.

Conduct
Confirm
Manage
Prepare
Analysis
Outputs
• Stakeholder Engagement: willingness from stakeholders to engage in
business analysis activities and interact with the business analyst when
necessary.
 Check
Knowledge

Introduction
Q &A
Integrate
Monitor
Direct
Develop
Manage
Charter
 Knowledge Check
1. All of the following tasks are performed during elicitation except:

A. Select elicitation techniques

Integrate
Introduction
B. Confirm elicitation results

Develop
Monitor
Manage
Charter
C. Prepare for elicitation

Q &A
Direct
D. Conduct elicitation activity

A. Select elicitation techniques

 Knowledge Check

2. You are reviewing documents for the current system in order to confirm the
existing requirements. Document analysis is an effective technique for doing this
work as long as the documents being reviewed are

Integrate
Introduction
Develop
Monitor
Manage
Charter
A. Not current and invalid

Q &A
Direct
B. Not current, but valid
C. Current, but not valid
D. Both current and valid

D. Both current and valid

 Knowledge Check

3. What is the proper sequence for conducting a brainstorming session?

A. Reduce, reuse, and recycle

Integrate
Introduction
B. Prepare, conduct, and wrap up

Develop
Monitor
Manage
Charter
Q &A
Direct
C. Prepare, analyze, and reduce
D. Generate, reduce, and assess

B. Prepare, conduct, and wrap up

 Knowledge Check
4. During an active observation session, the business analyst watches the user
carefully, asks them probing questions, and:

A. Acts as an apprentice

Integrate
Introduction
Develop
Monitor
B. Reviews the findings

Manage
Charter
Q &A
Direct
C. detailed notes
D. Studies the process

C. detailed notes
 Knowledge Check

5. What prototype allows you to learn about user interface needs and then to
evolve the requirements into a fully functioning system?
A. Throw- away

Integrate
Introduction
B. Horizontal

Develop
Monitor
Manage
Charter
C. Evolutionary

Q &A
Direct
D. Vertical

C. Evolutionary
 Knowledge Check

6. Who may participate in requirements elicitation activities?

A. Any stakeholder

Integrate
Introduction
B. Stakeholder list

Develop
Monitor
Manage
Charter
Q &A
C. Subject matter experts

Direct
D. Project team

A. Any stakeholder
 Knowledge Check

7. “Does the existing functionality currently meet your needs? ” is an example of

what type of structured interview question?

Integrate
Introduction
A. Closed- ended

Develop
Monitor
Manage
Charter
B. Open - ended

Q &A
Direct
C. Research
D. Meta question

A. Closed- ended
 You
Thank

Introduction
Q &A
Integrate
Monitor
Direct
Develop
Manage
Charter