Please enable JavaScript.
Coggle requires JavaScript to display documents.
Define, 1/Prepare for Elicitation, 4/Communicate Business Analysis…
Define
Elicitation
is the drawing forth or receiving of information from stakeholders or
other sources.
Collaboration
is the
act of two or more people working together towards a common goal.
Elicitation and Collaboration
knowledge area describes how business analysts identify and reach agreement on the mutual understanding of all types of business analysis information.
1/Prepare for Elicitation
1/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
2/Description
prepare for elicitation by defining the desired outcomes of the
activity, considering the stakeholders involved and the goals of the initiative.
deciding which techniques are best suited to produce those results
establishing the elicitation logistics, identifying any supporting materials needed,
determining which work products will be produced using the elicitation
results
understanding circumstances to foster collaboration during an elicitation
activity
3/Input
Stakeholder Engagement Approach
understanding stakeholders'
communication
collaboration needs helps plan and prepare appropriate
and effective elicitation events
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
5/Guidelines and Tools
Business Objectives
Existing Business Analysis Information
Business Analysis Approach
Potential Value
4/Elements
Select Elicitation Techniques
Set Up Logistics
Understand the Scope of Elicitation
Secure Supporting Materia
Prepare Stakeholders
how an elicitation
technique works or what information is needed
An agenda might be provided in advance to support stakeholders in coming prepared to the activity with the necessary frame of mind and information
7/ Stakeholders
Project Manager
Sponsor
Domain Subject Matter Expert
6/Techniques
Brainstorming
4/Communicate Business Analysis Information
1/Purpose
ensure
stakeholders have a shared understanding of business analysis information
2/Description
must communicate appropriate information to stakeholders at
the right time and in formats that meet their needs.
Multiple
forms of communication might be required for the same information
Consideration is given to expressing the information in language, tone, and style that is appropriate to the audience.
3/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.
4/Elements
Determine Objectives and Format of Communication
Communicate Business Analysis Package
Group collaboration
Individual collaboration
E-mail or other non-verbal methods
5/Guidelines and Tools
Business Analysis Approach
Information Management Approach
6/Techniques
Interviews
Reviews
Workshops
7/ Stakeholders
End User
Customer
Domain Subject Matter Expert
Implementation Subject Matter Expert
Tester
Any stakeholder
8/Outputs
Business Analysis Information (communicated):
business analysis information is considered communicated when the target stakeholders have reached an understanding of its content and implications.
3/Confirm Elicitation Results
4/Elements
1/Compare Elicitation Results Against Source Information
The business analyst may lead follow-up meetings where stakeholders correct the elicitation results.
Stakeholders may also confirm the elicitation results independently.
2/Compare Elicitation Results Against Other Elicitation Results
As comparisons are drawn, business analysts identify variations in results and resolve
them in collaboration with stakeholders.
Inconsistencies in elicitation results are often uncovered when business analysts develop specifications and models.
1/Purpose
The purpose of Confirm Elicitation Results is to check the information gathered
during an elicitation session for accuracy and consistency with other information.
2/Description
Elicited information
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
Collaboration with stakeholders might be necessary
to ensure their inputs are correctly captured and that they agree with the results
of non-facilitated elicitation
.
Confirming the elicitation results is a much less rigorous and formal review than
occurs during analysis.
3/Inputs
Elicitation Results (unconfirmed)
capture information in a format specific to
the elicitation activity.
5/Guidelines and Tools
Elicitation Activity Plan:
used to guide which alternative sources and which elicitation results are to be compared
Existing Business Analysis Information:
can be used to confirm the results of elicitation activities or to develop additional questions to draw out more detailed information.
6/Techiques
Interviews
Reviews
Document Analysis
Workshops
7/Stakeholders
Domain Subject Matter Experts
8/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.
5/Manage Stakeholder Collaboration
1/Purpose
The purpose of Manage Stakeholder Collaboration is to encourage stakeholders
to work towards a common goal
2/Description
Business analysis work lends itself to many collaboration opportunities between
groups of stakeholders on the business analysis work products.
Poor relationships with stakeholders can have many detrimental effects on
business analysis, including:
failure to provide quality information
strong negative reactions to setbacks and obstacles
resistance to change
lack of support for, and participation in, business analysis work, and
business analysis information being ignored
Business analysts actively manage relationships
with stakeholders who
provide services to the business analyst, including inputs to business analysis
tasks and other support activities
depend on services provided by the business analyst, including outputs of
business analysis tasks, and
participate in the execution of business analysis tasks.
3/Input
Stakeholder Engagement Approach
expected engagement with stakeholders
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.
4/Elements
1.Gain Agreement on Commitments
time and resource commitments.
The business analyst and stakeholders identify and agree
upon these commitments as early in the initiative as possible.
Effective negotiation, communication, and conflict resolution skills are important to effective stakeholder management
2.Monitor Stakeholder Engagement
Collaboration
Stakeholders are more likely to support change if business analysts collaborate
with them and encourage the free flow of information, ideas, and innovations.
5/Guidelines and Tools
Business Analysis Approach
Business Objectives
Future State Description
Recommended Actions
Risk Analysis Results
6/Techniques
Collaborative Games
Lessons Learned
Risk Analysis and Management
Stakeholder List, Map, or Personas
7/Stakeholders
All stakeholders:
all types of stakeholders who might be involved in collaboration during change
8/Outputs
Stakeholder Engagement:
willingness from stakeholders to engage in business analysis activities and interact with the business analyst when necessary
The Elicitation and Collaboration knowledge area is composed of the following
tasks:
2/Conduct Elicitation:
the work performed to understand stakeholder needs and identify potential solutions that may meet those needs
5/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.
4/Communicate Business Analysis Information:
provides stakeholders with the information they need, at the time they need it. The information is presented in a useful form, using the right terminology and concepts.
1/Prepare for Elicitation:
that they understand the nature of
the activities they are going to perform
set of expectations regarding the outcomes of the activity.
involves ensuring that the stakeholders have the
information they need to provide
3/Confirm Elicitation Results:
This task also involves comparing the information received with other information to look for inconsistencies or gaps.
2/Conduct Elicitation
1/Purpose
The purpose of Conduct Elicitation is to draw out, explore, and identify
information relevant to the change.
2/Description
Research:
involves systematically discovering and studying information from materials or sources that are not directly known by stakeholders involved in the change.
Experiments:
Some information cannot be drawn
from people or documents—because it is unknown.
Collaborative:
involves direct interaction with stakeholders, and relies on
their experiences, expertise, and judgment
3/Inputs
Elicitation Activity Plan:
includes the planned elicitation activities and
techniques, activity logistics (for example, date, time, location, resources, agenda), scope of the elicitation activity, and available sources of background
information
8/Outputs
• Elicitation Results (unconfirmed):
captured information in a format that is
specific to the elicitation activity.
4/Elements
4.1 Guide Elicitation Activity
• what other representations the activity results will support,
• how the output integrates into what is already known,
• what forms of output the activity will generate,
• who provides the information,
• scope of the change,
• who will use the information, and
• the elicitation activity goals and agenda,
• how the information will be used
4.2 Capture Elicitation Outcomes
State Diagram
1/Purpose
State modelling is used to describe and analyze the different possible states of an
entity within a system
how that entity changes from one state to another
what can happen to the entity when it is in each state.
2/Desciption
• a set of possible states for an entity
• the sequence of states that the entity can be in,
• how an entity changes from one state to another
• the events and conditions that cause the entity to change states
• the actions that can or must be performed by the entity in each state as it
moves through its life cycle
3/Elements
1 State
2 State Transition
3 State Diagram
4 State Tables
https://app.diagrams.net/#G19cDmP3Qcxl_eCXf6DsDHQ6oAmrbWBJIl
4/Usage Considerations
1 Strengths
• Identifies business rules and information attributes that apply to the entity
being modelled
• Identifies and describes the activities that apply to the entity at different states
of the entity
• Identifies and describes the activities that apply to the entity at different states
of the entity
2 Limitations
• Is usually only used to understand and communicate about information entities
that are perceived to be complex;
Building a state model appears simple at the start, but achieving a consensus among domain SMEs about the details required by the model can be difficult and time-consuming
• A high degree of precision about states and transitions is required to build a
state diagram;