ECBA Practice
Why is it important for a business analyst to know the role of stakeholders?
In order to understand sign-off authority
(BACCM Core Concept) Change
The act of transformation in response to a need.
Change works to improve the performance of an enterprise. These improvements are
deliberate and controlled through business analysis activities.
(BACCM Core Concept) Need
A problem or opportunity to be addressed.
Needs can cause changes by motivating stakeholders to act. Changes can also cause
needs by eroding or enhancing the value delivered by existing solutions.
(BACCM Core Concept) Solution
A specific way of satisfying one or more needs in a context.
A solution satisfies a need by resolving a problem faced by stakeholders or enabling
stakeholders to take advantage of an opportunity.
(BACCM Core Concept) Stakeholder
A group or individual with a relationship to the change, the need, or the solution.
Stakeholders are often defined in terms of interest in, impact on, and influence over the
change. Stakeholders are grouped based on their relationship to the needs, changes,
and solutions.
(BAACM Core Concept) Value
The worth, importance, or usefulness of something to a stakeholder within a context.
(BAACM Core Concept) Context
The circumstances that influence, are influenced by, and provide understanding of the
change.
What is business Analysis?
The BABOK® Guide describes and defines business analysis as the practice of
enabling change in an enterprise by defining needs and recommending solutions that
deliver value to stakeholders.
Design
A 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
An enterprise is a system of one or more organizations and the solutions they use to
pursue a shared set of common goals.
Organization
An autonomous group of people under the management of a single individual or board,
that works towards common goals and objectives.
Plan
A plan is a proposal for doing or achieving something.
Requirement
A requirement is a usable representation of a need.
Risk
Risk is the effect of uncertainty on the value of a change, a solution, or the enterprise.
Business Requirements
,statements of goals, objectives, and outcomes that describe why a change has been
initiated. They can apply to the whole of an enterprise, a business area, or a specific
initiative.
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
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
Customer
A customer uses or may use products or services produced by the enterprise and may
have contractual or moral rights that the enterprise is obliged to meet.
Domain Subject Matter Expert
A domain subject matter expert is any individual with in-depth knowledge of a topic
relevant to the business need or solution scope. This role is often filled by people who
may be end users or people who have in-depth knowledge of the solution such as
managers, process owners, legal staff, consultants, and others.
End User
End users are stakeholders who directly interact with the solution. End users can
include all participants in a business process, or who use the product or solution.
Implementation Subject Matter Expert
An implementation subject matter expert is any stakeholder who has specialized
knowledge regarding the implementation of one or more solution components.
While it is not possible to define a listing of implementation subject matter expert roles
that are appropriate for all initiatives, some of the most common roles are: project
librarian, change manager, configuration manager, solution architect, developer,
database administrator, information architect, usability analyst, trainer, and
organizational change consultant.
Operational Support
Operational support is responsible for the day-to-day management and maintenance of
a system or product.While it is not possible to define a listing of operational support
roles that are appropriate for all initiatives, some of the most common roles are:
operations analyst, product analyst, help desk, and release manager.
Project Manager
Project managers are responsible for managing the work required to deliver a solution
that meets a business need, and for ensuring that the project's objectives are met while
balancing the project factors including scope, budget, schedule, resources, quality, and
risk.While it is not possible to completely define a listing of project management roles
that are appropriate for all initiatives, some of the most common roles are: project lead,
technical lead, product manager, and team leader.
Regulator
, Regulators are responsible for the definition and enforcement of standards. Standards
can be imposed on the solution by regulators through legislation, corporate governance
standards, audit standards, or standards defined by organizational centers of
competency. Alternate roles are government, regulatory bodies, and auditor.
Sponsor
Sponsors are responsible for initiating the effort to define a business need and develop
a solution that meets that need. They authorize the work to be performed, and control
the budget and scope for the initiative. Alternate roles are executive and project
sponsor.
Supplier
A supplier is a stakeholder outside the boundary of a given organization or
organizational unit. Suppliers provide products or services to the organization and may
have contractual or moral rights and obligations that must be considered. Alternate roles
are providers, vendors, and consultants.
Tester
Testers are responsible for determining how to verify that the solution meets the
requirements defined by the business analyst, as well as conducting the verification
process. Testers also seek to ensure that the solution meets applicable quality
standards, and that the risk of defects or failures is understood and minimized. An
alternate role is quality assurance analyst.
Business Analysis Planning and Monitoring (Key knowledge area)
The Business Analysis Planning and Monitoring knowledge area tasks organize and
coordinate the efforts of business analysts and stakeholders. These tasks produce
outputs that are used as key guidelines for the other tasks throughout the BABOK®
Guide.
Brainstorming
Brainstorming is an excellent way to foster creative thinking about a problem. The aim
of brainstorming is to produce numerous new ideas, and to derive from them themes for
further analysis. Brainstorming is a technique intended to produce a broad or diverse
set of options.
It helps answer specific questions such as (but not limited to):
What options are available to resolve the issue at hand?
What factors are constraining the group from moving ahead with an approach or option?
What could be causing a delay in activity 'A'?
What can the group do to solve problem 'B'?
Brainstorming works by focusing on a topic or problem and then coming up with many
possible solutions to it. This technique is best applied in a group as it draws on the
experience and creativity of all members of the group. In the absence of a group, one
could brainstorm on one's own to spark new ideas. To heighten creativity, participants
are encouraged to use new ways of looking at things and freely associate in any
direction. When facilitated properly, brainstorming can be fun, engaging, and productive.
Business Cases
used to understand whether elements of the problem or opportunity are especially time-
sensitive, high-value, or whether there is any particular uncertainty around elements of
the possible need or solution.
Document Analysis
Why is it important for a business analyst to know the role of stakeholders?
In order to understand sign-off authority
(BACCM Core Concept) Change
The act of transformation in response to a need.
Change works to improve the performance of an enterprise. These improvements are
deliberate and controlled through business analysis activities.
(BACCM Core Concept) Need
A problem or opportunity to be addressed.
Needs can cause changes by motivating stakeholders to act. Changes can also cause
needs by eroding or enhancing the value delivered by existing solutions.
(BACCM Core Concept) Solution
A specific way of satisfying one or more needs in a context.
A solution satisfies a need by resolving a problem faced by stakeholders or enabling
stakeholders to take advantage of an opportunity.
(BACCM Core Concept) Stakeholder
A group or individual with a relationship to the change, the need, or the solution.
Stakeholders are often defined in terms of interest in, impact on, and influence over the
change. Stakeholders are grouped based on their relationship to the needs, changes,
and solutions.
(BAACM Core Concept) Value
The worth, importance, or usefulness of something to a stakeholder within a context.
(BAACM Core Concept) Context
The circumstances that influence, are influenced by, and provide understanding of the
change.
What is business Analysis?
The BABOK® Guide describes and defines business analysis as the practice of
enabling change in an enterprise by defining needs and recommending solutions that
deliver value to stakeholders.
Design
A 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
An enterprise is a system of one or more organizations and the solutions they use to
pursue a shared set of common goals.
Organization
An autonomous group of people under the management of a single individual or board,
that works towards common goals and objectives.
Plan
A plan is a proposal for doing or achieving something.
Requirement
A requirement is a usable representation of a need.
Risk
Risk is the effect of uncertainty on the value of a change, a solution, or the enterprise.
Business Requirements
,statements of goals, objectives, and outcomes that describe why a change has been
initiated. They can apply to the whole of an enterprise, a business area, or a specific
initiative.
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
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
Customer
A customer uses or may use products or services produced by the enterprise and may
have contractual or moral rights that the enterprise is obliged to meet.
Domain Subject Matter Expert
A domain subject matter expert is any individual with in-depth knowledge of a topic
relevant to the business need or solution scope. This role is often filled by people who
may be end users or people who have in-depth knowledge of the solution such as
managers, process owners, legal staff, consultants, and others.
End User
End users are stakeholders who directly interact with the solution. End users can
include all participants in a business process, or who use the product or solution.
Implementation Subject Matter Expert
An implementation subject matter expert is any stakeholder who has specialized
knowledge regarding the implementation of one or more solution components.
While it is not possible to define a listing of implementation subject matter expert roles
that are appropriate for all initiatives, some of the most common roles are: project
librarian, change manager, configuration manager, solution architect, developer,
database administrator, information architect, usability analyst, trainer, and
organizational change consultant.
Operational Support
Operational support is responsible for the day-to-day management and maintenance of
a system or product.While it is not possible to define a listing of operational support
roles that are appropriate for all initiatives, some of the most common roles are:
operations analyst, product analyst, help desk, and release manager.
Project Manager
Project managers are responsible for managing the work required to deliver a solution
that meets a business need, and for ensuring that the project's objectives are met while
balancing the project factors including scope, budget, schedule, resources, quality, and
risk.While it is not possible to completely define a listing of project management roles
that are appropriate for all initiatives, some of the most common roles are: project lead,
technical lead, product manager, and team leader.
Regulator
, Regulators are responsible for the definition and enforcement of standards. Standards
can be imposed on the solution by regulators through legislation, corporate governance
standards, audit standards, or standards defined by organizational centers of
competency. Alternate roles are government, regulatory bodies, and auditor.
Sponsor
Sponsors are responsible for initiating the effort to define a business need and develop
a solution that meets that need. They authorize the work to be performed, and control
the budget and scope for the initiative. Alternate roles are executive and project
sponsor.
Supplier
A supplier is a stakeholder outside the boundary of a given organization or
organizational unit. Suppliers provide products or services to the organization and may
have contractual or moral rights and obligations that must be considered. Alternate roles
are providers, vendors, and consultants.
Tester
Testers are responsible for determining how to verify that the solution meets the
requirements defined by the business analyst, as well as conducting the verification
process. Testers also seek to ensure that the solution meets applicable quality
standards, and that the risk of defects or failures is understood and minimized. An
alternate role is quality assurance analyst.
Business Analysis Planning and Monitoring (Key knowledge area)
The Business Analysis Planning and Monitoring knowledge area tasks organize and
coordinate the efforts of business analysts and stakeholders. These tasks produce
outputs that are used as key guidelines for the other tasks throughout the BABOK®
Guide.
Brainstorming
Brainstorming is an excellent way to foster creative thinking about a problem. The aim
of brainstorming is to produce numerous new ideas, and to derive from them themes for
further analysis. Brainstorming is a technique intended to produce a broad or diverse
set of options.
It helps answer specific questions such as (but not limited to):
What options are available to resolve the issue at hand?
What factors are constraining the group from moving ahead with an approach or option?
What could be causing a delay in activity 'A'?
What can the group do to solve problem 'B'?
Brainstorming works by focusing on a topic or problem and then coming up with many
possible solutions to it. This technique is best applied in a group as it draws on the
experience and creativity of all members of the group. In the absence of a group, one
could brainstorm on one's own to spark new ideas. To heighten creativity, participants
are encouraged to use new ways of looking at things and freely associate in any
direction. When facilitated properly, brainstorming can be fun, engaging, and productive.
Business Cases
used to understand whether elements of the problem or opportunity are especially time-
sensitive, high-value, or whether there is any particular uncertainty around elements of
the possible need or solution.
Document Analysis
