KA Task Purpose Description

Business analysis approaches describe the overall

To define an appropriate method that will be followed when performing
BAPM Plan Business Analysis Approach method to conduct business analysis work on a given initiative, how
business analysis activities. and when the tasks will be performed, and the
deliverables that will be produced.
 To plan an approach for
Plan Stakeholder Engagement involves conducting
establishing and
a thorough stakeholder analysis to identify all of
BAPM Plan Stakeholder Engagement maintaining effective
the involved stakeholders and analyse their
working relationships with
characteristics
the stakeholders.

to define how decisions

Business Analysts ensure that a governance
are made about process is in place and clarify any ambiguities
requirements and designs,
BAPM Plan Business Analysis Governance within it. A governance process identifies the
including reviews, change
decision makers, process and information required
controls, approvals, and
for decisions to be made.
prioritization
 Business analysis information is comprised of all
the information business analysts elicit, create,
compile and disseminate in the course of
to develop an approach
performing business analysis. Information
BAPM Plan Business Analysis Information Management for how the business management helps ensure that business analysis
analysis information will
information is organized in functional and useful
be stored and assessed
manner, is easily accessible to appropriate
personnel and is stored for the necessary length of
time

to assess business analysis To monitor and improve performance, it is

Identify Business Analysis Performance Improvements work and to plan to necessary to establish the performance measures,
BAPM conduct the performance analysis, report on the
improve processes where
results of the analysis, and identify any necessary
required.
preventive, corrective or developmental actions.
 to understand the scope
of the elicitation
Business analysts prepare for elicitation by
activity, select appropriate
defining the desired outcomes of the
techniques, and plan for
E&C • Prepare of Elicitation activity, considering the stakeholders involved and
(or procure) appropriate the goals of the initiative.
supporting materials and
resources.

The purpose of Conduct

Elicitation is to draw out, Collaborative
E&C • Conduct Elicitation explore, and identify Research
information relevant to Experiments
the change.
 The purpose of Confirm
Elicitation Results is to Elicited information is confirmed to identify any
check the information problems and resolve them before resources are
E&C • Confirm Elicitation Results gathered during an committed to using the information. This review
elicitation session for may discover errors, omissions, conflicts and
accuracy and consistency ambiguity.
with other information

is to ensure that
stakeholders have a Business analysts must communicate appropriate
E&C • Communicate Business Analysis Information shared understanding of information to stakeholders at the right time and
business analysis in formats that meet their needs
information

to encourage stakeholders Business analysis work lends itself to many

collaboration opportunities between group of
E&C • Manage Stakeholder Collaboration to work towards a
stakeholders on the business analysis work
common goal.
products
 ensure that requirements
and designs at different Requirements traceability identifies and
levels are aligned to one documents the lineage of each requirement,
RLM • Trace Requirements another, and to manage including its backward traceability, its forward
the effects of change to traceability, and its relationship to other
one level on related requirements
requirements

retain requirement
accuracy and consistency
throughout and beyond
A requirement that represents an ongoing need
the change during the
RLM • Maintain Requirements must be maintained to ensure that it remains valid
entire requirements life
over time
cycle, and to support reuse
of requirements in other
solutions
 The purpose of Prioritize Prioritization is the act of ranking requirements to
Requirements is to rank determine their relative importance to
RLM • Prioritize Requirements the requirements in the stakeholders. Priority can refer to the relative
order of relative value of a requirement, or to the sequence in
importance which it will be implemented

The Assess Requirements Changes task is

to evaluate the performed as new needs or possible solutions are
implications of proposed defined. Assessment must be performed to
RLM • Assess Requirements Changes
changes to requirements determine whether a proposed change will
and designs increase the value of a solution, and if so, what
action will be taken.
 to obtain agreement on
and approval of BAs are responsible for ensuring clear
requirements and designs
communication of requirements, designs, and
for business analysis work
RLM • Approve Requirements other business analysis information to the key
to continue and/or
stakeholders responsible for approving that
solution construction to
information
proceed.
 to understand the reasons
The starting point for any change is an
why an enterprise needs
understanding of why the change is needed.
to change some aspect of
Potential change is triggered by problems or
how it operates and what
SA • Analyze Current State opportunities that cannot be addressed without
would be directly or
altering the current state. The scope of the current
indirectly affected by the state describes the important existing
change. It sets a baseline characteristics of the environment.
and context for change
 defines goals and
objectives that will
demonstrate that the Business Analysts work to ensure that the future
business need has been state of the enterprise is well defined, that it is
SA • Define Future State satisfied and defines what achievable with the resources available, and that
parts of the enterprise key stakeholders have a shared consensus vision
need to change in order to of the outcome.
meet those goals and
objectives.
 about understanding the
uncertainties around a
change, considers the Assessing Risks includes analyzing and managing
effect those uncertainties them. Risks might be related to the current state, a
SA • Assess Risks may have on the ability to desired future state, a change itself, a change
deliver value through a strategy, or any task being performed by the
change, and recommends enterprise.
actions to address risks
where appropriate.
 gap analysis between
current and future state,
Developing a change strategy is simpler when the
assessing options for
current state and the future state are already
SA • Define Change Strategy achieving the future state,
defined because they provide some context for
and recommending the
the change.
highest value approach for
reaching the future state.
 to analyze, synthesize, and
Specify and Model Requirements describes the
refine elicitation results
RADD • Specify and Model Requirements practices for analyzing elicitation results and
into requirements and
creating representations of those results
designs.
 The purpose of Verify
Requirements is to ensure Verifying Requirements ensures that the
that requirements and requirements and designs have been defined
RADD • Verify Requirements designs specification and correctly. Requirements verification constitutes a
models meet quality check by the BA and key stakeholders to
standards and are usable determine that the R&D are ready for validation.
for the purpose they serve

ensure that all R&D align

ongoing process to ensure that stakeholder,
to the business
solution and transition requirements align to the
RADD • Validate Requirements requirements and support
business requirements and that the designs satisfy
the delivery of needed
the requirements
value

Requirements architecture is the structure of all

the requirements of a change.
to ensure that the -Understand which models are appropriate for
requirements collectively domain, solution scope, and audience.
RADD • Define Requirements Architecture support one another to -Organize requirements into structures relevant to
fully achieve the different stakeholders
objectives. -Ensure the requirements work together to
achieve the overall objectives
 to define the solution
approach, identify
opportunities to improve
the business, allocate When designing a solution, there may be one or
RADD • Define Design Options requirements across more design options identified. Each design option
solution components and represents a way to satisfy a set of requirements
represent design options
that achieve the desired
future state.
 to estimate the PV for
each design option and to
establish which one is how to estimate the potential value delivered by a
RADD • Analyze Potential Value and Recommend Solution
most appropriate to meet set of requirements, designs or design option.
the enterprise’s
requirements.
 to define performance
measures and use the data Performance measures determine the value of a
collected to evaluate the newly deployed or existing solution. The measures
SE Measure Solution Performance
effectiveness of a solution used depend on the solution itself, the context and
in relation to the value it how the organization defines value
brings
 to provide insights into the In order to meaningfully analyze performance
performance of a solution measures, business analysts require a thorough
SE Analyze Performance Measures
in relation to the value it understanding of the potential value that
brings. stakeholders hope to achieve with the solution.

to determine the factors

Assessing solution limitations identifies the root
internal to the solution
SE Assess Solution Limitations causes for under-performing and ineffective
that restrict the full solutions and solution components
realization of value.
 Solutions may operate across various organizations
to determine how factors within an enterprise, and therefore have many
external to the solution interactions and interdependencies. Assessing
SE Assess Enterprise Limitations
are restricting value enterprise limitations identifies root causes and
realization. describes how enterprise factors limit value
realization
 to Increase Solution Value
is to understand the
factors that create This focuses on understanding the aggregate of
differences between the performed assessments and identifying
SE Recommend Actions to Increase Solution Value
potential value and actual alternatives and actions to improve solution
value, and recommend a performance and increase value realization.
course of action to align
them.
Input Output Output description Elements Guidelines and Tools Techniques

Brainstorming
Business Cases
Document Analysis
It identifies business
Estimation
analysis approach and • Planning Approach Financial Analysis
activities that will be • Formality and Level of • Business Analysis Functional
performed across an
Detail of Business Performance Assessment Decomposition
initiative including who
Analysis Deliverables • Business Policies Interviews
will perform the
Business Analysis • Business Analysis • Expert Judgement Item Tracking
Needs activities, the timing of
Approach Activities • Methodologies and Lessons Learned
the work, the
• Timing of Business Frameworks Process Modelling
deliverables that will be
Analysis Work • Stakeholder Engagement Reviews
produced and the
• Complexity and Risk Approach Risk Analysis and
business analysis
• Acceptance Management
techniques that will be Scope Modelling
used
Survey or
Questionnaire
Workshops
 Brainstorming
Business Rules Analysis
Document Analysis
Interviews
Lessons Learned
It contains a list of the Perform Stakeholder Mind Mapping
stakeholders, their Analysis Organizational
characteristics which Define Stakeholder • Business Performance Modelling
Needs Stakeholder were analysed, and a Collaboration Assessment Process Modelling
BA Approach Engagement Approach listing of the roles and Stakeholder • Change Strategy Risk Analysis and
responsibilities for the Communication Needs • Current State Description Management
change. Scope Modelling
Stakeholder List, Map
or Personas
Survey or
Questionnaire
Workshops

Brainstorming
It identifies the Document Analysis
stakeholders who will Interviews
have the responsibility • Business Analysis Item Tracking
Business Analysis and authority to make Decision Making Lessons Learned
Approach decisions about business Change Control Process Performance Assessment Organizational
• Business Policies
Stakeholder Governance Approach analysis work including Plan Prioritization Modelling
• Current State Description
Engagement who will be responsible Approach Process Modelling
• Legal/Regulatory
Approach for setting priorities and Plan for Approvals Reviews
Information
who will approve the Survey or
changes to business Questionnaire
analysis information. Workshops
 • Organization of Brainstorming
Business Analysis
It includes the defined Interviews
Business Analysis Information • Business Analysis
approach for how Item Tracking
Approach • Level of Abstraction Performance Assessment
business analysis Lessons Learned
Stakeholder • Storage and Access • Business Policies
Engagement Information information will be • Requirements • Information Management Mind Mapping
Management Approach stored, accessed, and Process Modelling
Approach Attributes Tools
utilized during the change Survey or
Business Analysis and after the change is • Plan Traceability • Legal/Regulatory Questionnaire
Approach complete. Approach Information Workshops
• Plan for Requirements
Reuse

Brainstorming
Interviews
Item Tracking
It includes a comparison
Lessons Learned
of planned vs actual
Metrics and Key
performance, identifying
Performance
the root cause of
Business Analysis variances from the • Performance Analysis Indicators(KPIs)
Approach Business Analysis expected performance, • Assessment Measures Organizational Performance Observation
Performance • Analyze Results Process Analysis
Performance proposed approaches to
Assessment • Recommend Actions for Standards Process Modelling
Objectives(external) address issues, and other
Improvement Reviews
findings to help Risk Analysis and
understand the
Management
performance of business
Root Cause Analysis
analysis processes.
Survey or
Questionnaire
Workshops
 • Understand the scope
of elicitation
• Select Elicitation
Needs It includes logistics, scope
Techniques
Stakeholder of the elicitation activity,
Elicitation Activity Plan • Set Up Logistics
Engagement selected techniques and • Secure Supporting
Approach supporting materials
Material
• Prepare Stakeholders

Benchmarking and
Market Analysis
Brainstorming
Business Rules Analysis
Collaborative Games
Concept Modelling
Data Mining
Business Analysis Approach Data Modelling
• Guide Elicitation Existing Business Analysis Document Analysis
It captures information in Focus Groups
Elicitation Activity Elicitation
a format that is specific Activity
Information
Interface Analysis
Plan Results(unconfirmed) • Capture Elicitation Stakeholder Engagement
to the elicitation activity Interviews
Outcomes Approach Mind Mapping
Supporting Materials
Observation
Process Analysis
Process Modelling
Prototyping
Survey or
Questionnaire
Workshops
 Integrated output that
the business analyst and • Compare Elicitation
Document Analysis
other stakeholders agree Results Against Source
Elicitation Activity Plan Interviews
Elicitation Elicitation correctly reflects Information
Existing Business Analysis Reviews
Results(unconfirmed Results(confirmed) captured information and • Compare Elicitation Information Workshops
confirms that it is Results Against Other
relevant and useful as an Elicitation Results
input for further work.

BAI is considered • Determine Objectives

Business Analysis
communicated when the and Format of
Information Business Analysis Business Analysis Approach Interviews
target stakeholders have Communication
Stakeholder Information(Communica • Information Management Reviews
Engagement ted) reached an Approach Workshops
understanding of its • Communicate Business
Approach
content and implications Analysis Package

Stakeholder Willingness of the Collaborative Games

• Gain Agreement on • Business Analysis Approach
Engagement stakeholders to engage in Commitments • Business Objectives Lessons Learned
Approach Stakeholder business analysis Risk Analysis and
• Monitor Stakeholder • Future State Description
Business Analysis Engagement activities and interact Management
Engagement • Recommended Actions
Performance with the business analyst Stakeholder List, Map
• Collaboration • Risk Analysis Results
Assessment when necessary. or Personas
 To have clearly defined
• Domain Knowledge
relationships to other
• Information Management Business Rules Analysis
requirements, solution
Approach Functional
components, or releases, • Level Of Formality
Requirements Requirements(traced) • Legal/Regulatory Decomposition
phases or iterations • Relationships
Design Designs(traced) Information Process Modelling
within a solution scope • Traceability Repository
• Requirements Scope Modelling
such that coverage and Management
the effects of change are
Tools/Repository
clearly identifiable

Business Rules Analysis

Data Flow Diagrams
They are defined once
and available for long Data Modelling
Document Analysis
Requirements(maintain term usage by the • Maintain Requirements
Requirements Information Management Functional
ed) organization. They may • Maintain Attributes
Design Approach Decomposition
Designs(maintained) become organizational • Reusing Requirements
Process Modelling
process assets or be used
Use Cases and
in future initiatives.
Scenarios
User Stories
 Backlog Management
• Business Constraints Business Cases
• Basis of
Prioritized or ranked • Change Strategy Decision Analysis
Prioritization( Benefit ,
requirements/designs are • Domain Knowledge Estimation
Requirements(prioritize available for additional Penalty, Cost, Risk, • Governance Approach Financial Analysis
Requirements Dependencies, Time
d) work, ensuring that the • Requirements Architecture Interviews
Design Sensitivity)
Designs(prioritized) highest valued • Challenges of • Requirements Item Tracking
requirements are Prioritization Management Prioritization
addressed first. Tools/Repository Risk Analysis and
• Continual Prioritization
• Solution Scope Management
Workshops

Business Cases
Business Rules Analysis
Decision Analysis
• Assessment Formality • Change Strategy Document Analysis
Requirements Change The recommendation to • Impact Analysis • Domain Knowledge Estimation
Requirements
Assessment approve, modify or deny (Benefit,Cost , Impact, • Governance Approach Financial Analysis
Design
Designs Change a proposed change to • Legal/Regulatory Approach Interface Analysis
Propopsed change Schedule,Urgency )
Assessment requirements • Requirements Architecture Interviews
• Impact Resolution
• Solution Scope Item Tracking
Risk Analysis and
Management
Workshops
 • Understand
They are agreed to by Stakeholder Roles Acceptance and
stakeholders and are • Requirements Evaluation Criteria
Requirements(verifie Requirements(approved • Conflict and Issue
ready for use in Management Decision Analysis
d) ) Management
subsequent Business Tools/Repository Item Tracking
Designs Designs (approved • Gain Consensus
Analysis or solution • Solution Scope: Reviews
Track and Communicate
development efforts. Workshops
Approval
 Benchmarking and
Market Analysis
Business Capability
Analysis
Business Model Canvas
Business Cases
Concept Modelling
Data Mining
Document Analysis
The context of the Financial Analysis
enterprise’s scope, Focus Groups
capabilities, resources, Functional
• Business Needs
performance, culture, • Business Analysis Approach Decomposition
• Organizational
dependencies , • Enterprise Limitation Interviews
Structure and Culture
infrastructure , external • Organizational Strategy: • Item Tracking
• Capabilities and
influences, and significant Solution Limitation Lessons Learned
Current state Processes
Elicitation Results relationships between • Solution Performance Metrics and Key
Description • Technology and
Needs these elements Goals. Performance Indicators
Business requirements Infrastructure
Business Requirements : • Policies • Solution Performance Mind Mapping
The problem, • Business Architecture Measures Observation
opportunity, or constraint • Stakeholder Analysis Organizational
• Internal Assets
which is defined based on Results Modelling
understanding of the • External Influencers Process Analysis
current state. Process Modelling
Risk Analysis and
Management
Root Cause Analysis
Scope Modelling
Survey or
Questionnaire
SWOT Analysis
Vendor Assessment
Questionnaire
 Acceptance and
Evaluation Criteria
Balanced Scorecard
Benchmarking and
Market Analysis
Brainstorming
Business Capability
BO: The desired direction Analysis
• Business Goals and
that the business wished Business Cases
Objectives
to pursue in order to Business Model Canvas
• Scope of Solution Scope
achieve the future state. Decision Analysis
• Constraints
FS: It includes boundaries Decision Modelling
• Organizational
of the proposed new, Financial Analysis
Structure and Culture
removed, and modified • Current State Description Functional
Business Objectives • Capabilities and
Business components of the • Metrics and Key Decomposition
Future State Description Processes
Requirements enterprise and potential Performance Indicators Interviews
Potential Value • Technology and
value expected from the Infrastructure. • Organizational Strategy Lessons Learned
future state. • Policies Metrics and Key
PV: The value that may Performance Indicators
• Business Architecture
be realized by Mind Mapping
implementing the • Internal Assets Organizational
proposed future state. • Identify Assumptions Modelling
• Potential Value Process Modelling
Prototyping
Scope Modelling
Survey or
Questionnaire
SWOT Analysis
Vendor Assessment
Workshops
 Brainstorming
Business Cases
an understanding of the Decision Analysis
Business Objectives: risks associated with Business Analysis Approach Document Analysis
Elicitation achieving the future Business Policies Financial Analysis
Unknowns
Results(confirmed) state, and the mitigation Change Strategy Interviews
Internal Assets
Influences strategies which will be Current State Description Lessons Learned
Risk Analysis Results Negative Impact to Value
Potential Value used to prevent those Future State Description Mind Mapping
Risk Tolerance
Requirements(prioriti risks, reduce the impact Identified Risks Risk Analysis and
zed) of the risk, or reduce the Recommendation Stakeholder Engagement Management
likelihood of the risk Approach Root Cause Analysis
occurring. Survey or
Questionnaire
Workshops
 Balanced Scorecard
Benchmarking and
Market Analysis
Brainstorming
Business Capability
Analysis
Business Cases
Business Model Canvas
Change Strategy: The
Decision Analysis
Current State approach that the Solution Scope Estimation
Description organization will follow to
Gap Analysis Financial Analysis
Future State guide change.
Change Strategy Enterprise Readiness Business Analysis Approach Focus Groups
Description Solution Scope: The
Solution Scope Assessment Design Options Functional
Risk Analysis Results solution scope that will
Change Strategy Solution Recommendation Decomposition
Stakeholder be achieved through
Engagement execution of the change Transition States and Interviews
Release Planning Lessons Learned
Approach strategy.
Mind Mapping
Organizational
Modelling
Process Modelling
Scope Modelling
SWOT Analysis
Vendor Assessment
Workshops
 Acceptance and
Evaluation Criteria
Business Capability
Analysis
Business Model Canvas
Business Rules Analysis
Concept Modelling
Data Dictionary
Data Flow Diagrams
Data Modelling
Decision Modelling
Functional
Decomposition
Glossary
Model Requirements Modelling Interface Analysis
Any combination of Analyze Requirements Notations/Standards Non- Functional
requirements and/or Represent Requirements Modelling Tools Requirements Analysis
Elicitation Results Requirements(specified
designs in the form of and Attributes Requirements Architecture Organizational
(any state) and modelled)
text, matrices and Implement the Requirements Lifecycle Modelling
diagrams Appropriate Levels of Management Tools Process Modelling
Abstraction Solution Scope Prototyping
Roles and Permission
Matrix
Root Cause Analysis
Scope Modelling
Sequence Diagrams
Stakeholder List, Map
or Personas
State Modelling
Use Cases and
Scenarios
User Stories
 Acceptance and
Characteristics of
It is a set of requirements Evaluation Criteria
Requirements and Design
or designs that is of Item Tracking
Requirements(specifi Quality Requirements Life Cycle
Requirements(Verified) sufficient quality to be Metrics and Key
ed and modelled) Verification Activities Management Tools
used as a basis for further Performance
Checklists
work. Indicators(KPIs)
Reviews

Acceptance and
Evaluation Criteria
Document Analysis
Identify Assumptions Financial Analysis
Business Objectives
They deliver benefit to Define Measurable Item Tracking
Requirements(specifi Requirements(Validated stakeholders and align Future State Description
Evaluation Criteria Metrics and Key
ed and modelled): ) Potential Value
with business goals. Evaluate Alignment with Performance
Solution Scope
Solution Scope Indicators(KPIs)
Reviews
Risk Analysis and
Management

Requirements Viewpoints Data Modelling

Information and Views Functional
Template Architecture Architecture Management Decomposition
Management
Approach Requirements The requirements and Completeness Software Interviews
the interrelationships Relate and Verify Legal Regulatory Information Organizational
Requirements(any Architecture
between them Requirements Methodologies and Modelling
state)
Relationships(CoCoNUD) Frameworks Scope Modelling
Solution Scope Business Analysis Workshops
Information Architecture
 Benchmarking and
Market Analysis
Brainstorming
Document Analysis
Define Solution
Change Strategy Interviews
Approaches Existing Solutions
Requirements(validat They describe various Lessons Learned
Identify Improvement Future State Description
ed, prioritized) Design Options ways to satisfy one or Mind Mapping
Opportunities Requirements(traced)
Requirements more needs in a context Root Cause Analysis
Assess Design Options Solution Scope
Architecture and Recommend Solution Survey or
Questionnaire
Vendor Assessment
Workshops.
 Acceptance and
Evaluation Criteria
Backlog Management
Brainstorming
Business Case
Business Model Canvas
Decision Analysis
It identifies the
Estimation
suggested, most Expected Benefits Business Objectives
Financial Analysis
appropriate solution Expected Costs Current State Description
Potential Value Solution Focus Groups
based on an evaluation of Determine Value Future State Description
Design Options Recommendation all defined design Assess Design Options Risk Analysis Results Interviews
Metrics and Key
options. and Recommend Solution Solution Scope
Performance
Indicators(KPI)
Risk Analysis and
Management
Survey or
Questionnaire
SWOT Analysis
Workshops
 Acceptance and
Evaluation Criteria
Benchmarking and
Market Analysis
Business Cases
Data Mining
Decision Analysis
Define Solution Focus Groups
The measures that
Performance Measures Change Strategy Metrics and Key
Business Objectives provide information on
Solution Performance Validate Performance Future State Description Performance
Implemented how well the solution is
Measures Measures Requirements(validated) Indicators(KPI)
Solution(external) performing or potentially
Collect Performance Solution Scope Non-Functional
could perform
Measures Requirements Analysis
Observation
Prototyping
Survey or
Questionnaire
Use Cases and
Scenarios
Vendor Assessment
 Acceptance and
Evaluation Criteria
Benchmarking and
Market Analysis
The results of the
Data Mining
analysis of Solution Performance
Interviews
measurements collected versus Desired Value Change Strategy
Potential Value Metrics and Key
Solution Performance and recommendations to Risks Future State Description
Solution Performance Performance
Analysis solve performance gaps Trends Risk Analysis Results
Measures Indicators(KPI)
and leverage Accuracy Solution Scope
Observation
opportunities to improve Performance Variances
value Risk Analysis and
Management
Root Cause Analysis
Survey or
Questionnaire

Acceptance and
Evaluation Criteria
Benchmarking and
Market Analysis
Business Rules Analysis
Identify Internal Solution
Data Mining
Implemented A description of the Component
Change Strategy Decision Analysis
Solution(External) current limitations of the Dependencies
Solution Limitation Risks Analysis Results Interviews
Solution Performance solution including Investigate Solution Solution Scope Item Tracking
Analysis constraints and defects. Problems
Lessons Learned
Impact Assessment
Risk Analysis and
Management
Root Cause Analysis
Survey or
Questionnaire
 Benchmarking and
Market Analysis
Brainstorming
Data Mining
Decision Analysis
Document Analysis
Interviews
Item Tracking
Lessons Learned
Current State Enterprise Culture
Observation
Description current limitations of the Assessment Business Objectives
Implemented(or enterprise including how Stakeholder Impact Change Strategy Organizational
Modelling
Constructed) Enterprise Limitation the solution performance Analysis Future State Description
Process Analysis
Solution(external) is impacting the Organizational Structure Risk Analysis Results Process Modelling
Solution Performance enterprise. Changes Solution Scope Risk Analysis and
Analysis Operational Assessment
Management
Roles and Permissions
Matrix
Root Cause Analysis
Survey or
Questionnaire
SWOT Analysis
Workshops
 Data Mining
Decision Analysis
Financial Analysis
Focus Groups
The recommendation of Organizational
what should be done to Adjust Solution Business Objectives Modelling
Enterprise Limitations
Recommended Actions improve the value of the Performance Measures Current State Description Prioritization
Solution Limitation
solution within the Recommendations Solution Scope Process Analysis
enterprise. Risk Analysis and
Management
Survey or
Questionnaire
Stakeholders Mnemonics

ASGImPi
A -Plan Business
Analysis Approach
S -Plan Stakeholder
SME Engagement
PM G- Plan Business
Regulator Analysis Governance
Sponsor Im - Plan Business
Analysis Information
Management
Pi - Identify Business
Analysis Performance
Improvements
Customer
SME
End User
PM
Regulator
Sponsor
Supplier

SME
PM
Regulator
Sponsor
SME
Requirement
Regulator Attributes-
Sponsor
CARAS SOUPS

Domain
Subject Matter
Expert
Project
Manager
Sponsor
 Pre Conduct
Confirmation Coll

Customer
Domain
Subject Matter
Expert
End User
Implementatio
n Subject
Matter Expert
Sponsor
Any
Stakeholders
Domain
Subject Matter
Expert
Any
Stakeholder

End User
Customer
Domain
Subject Matter
Expert
Implementatio
n Subject
Matter Expert
Tester
Any
Stakeholder

All
Stakeholders
Customers
Domain
Subject Matter
Expert
End User
Implementatio
n Subject
TiMe PAss App
Matter Expert
Operational
Support
Project
Manager
Sponsor

Domain
Subject Matter
Expert
Implementatio
n Subject
Matter Expert
Operational
Support
Regulator
Tester
Customer
End User
Implementatio
n Subject
Matter Expert
Project
Manager
Regulator
Sponsor

Customer
Domain
Subject Matter
Expert
End User
Operational
Support
Project
Manager
Regulator
Sponsor
Tester
Customer
Domain
Subject Matter
Expert
End User
Operational
Support
Project
Manager
Regulator
Sponsor
Tester
Customer
Domain
Subject Matter
Expert
End User
Implementatio ACDFall ARCS
n Subject AC- Analyze Current
Matter Expert State
Operational DF- Define Future State
Support AR- Assess Risks
Project CS- Define Change
Manager Strategy
Regulator
Sponsor
Supplier
Tester
Customer
Domain
Subject Matter
Expert
End User
Implementatio
n Subject
Matter Expert
Operational
Support
Project
Manager
Regulator
Sponsor
Supplier
Tester
Domain
Subject Matter
Expert
Implementatio
n Subject
Matter Expert
Operational
Support
Project
Manager
Supplier
Tester
Regulator
Sponsor
Customer
Domain
Subject Matter
Expert
End User
Implementatio
n Subject
Matter Expert
Operational
Support
Project
Manager
Regulator
Sponsor
Supplier
Tester
Any
stakeholder Cap of PRADa
Any
stakeholders

All Specifc model VeVa

stakeholders RADO recommended

Domain SME,
Implementatio
n SME, Project
Manager,
Sponsor,
Tester
Any
stakeholder
Domain
Subject Matter
Expert
Implementatio
n Subject
Matter Expert
Operational
Support
Project
Manager
Supplier
Customer
Domain
Subject Matter
Expert
End User
Implementatio
n Subject
Matter Expert
Project
Manager
Regulator
Sponsor
Customer
Domain
Subject Matter
MAAARS
Expert
Measure, Analyze,
End User
Assess, Assess,
Project
recommend
Manager
Regulator
Sponsor
Domain
Subject Matter
Expert
Project
Manager
Sponsor

Customer
Domain
Subject Matter
Expert
End User
Regulator
Sponsor
Tester
Customer
Domain
Subject Matter
Expert
End User
Regulator
Sponsor
Customer
Domain
Subject Matter
Expert
End User
Regulator
Sponsor

( Requirement
Schema)
BSFNT-
Business requirements,
stakeholder
requirements, Solution
requirements
( Functiona and non-
functional), Transition
Knowledge Areas-
P E RL S RAD S
P- Business Analysis
Planning and
monitoring
E - Elicitation and
collaboration
RL- Requirements
Lifecycle management
S - Strategy analysis
RAD - Requirement
analysis and design
definition
S - Solution assessment
and Validation.

Perspectives- BAABIIT
BPM- Business
architecture, Agile, BI,
IT, BPM

BACCM-
ChaNgeS SVC
Ch- Change,
N- Need
S – Solution
S- Stakeholders
V- Value
C- Context
 TTEAA
Trustwort
Underlying
hiness
Competencies
BA Be,CommITed Organizati
on and
Business Knowledge,
Time
Analytical Thinking,
Managem
and problem solving
ent
Behavioral
Ethics
Characterstics(T2EA2), Personal
Communition skills,
Accountab
Interaction Skills, ility
Tools and technology
Adaptabili
ty
Techniques
Name Don’t Know Know Used Points to remember
Brainstorming
Data Dictionary
Data Flow Diagrams
Data Mining
Glossary
Risk Analysis and Management
Roles and Permissions Matrix
Root Cause Analysis
Stakeholder List, Map or Personas
SWOT Analysis
Vendor Assessment
Workshops
Acceptance and Evaluation Criteria
Backlog Management
Balanced Scorecard
Benchmarking and Market Analysis
Business Capability Analysis
Business Cases
Business Model Canvas
Business Rules Analysis
Collaborative Games
Concept Modelling
Data Modelling
Decision Analysis
Decision Modelling
Document Analysis
Estimation
Financial Analysis
Focus Groups
Functional Decomposition
Interface Analysis
Interviews
Item Tracking
Lessons Learned
Metrics and Key Performance Indicators
Mind Mapping
Non-Functional Requirement Analysis
Observation
Organizational Modelling
Prioritization
Process Analysis
Process Modelling
Prototyping
Reviews
Scope Modelling
Sequence Diagrams
State Modelling
Survey or Questionnaire
Use Cases and Scenarios
User Stories
URLs

https://designabetterbusiness.com/2017/11/02/how-to-use-the-business-model-canvas-for-innovation/

http://www.brcommunity.com/articles.php?id=b779