BABOK Knowledge Areas
Business Analysis planning and Monitoring
AGENDA
▪ Introduction to Knowledge area
Business
Analysis ▪ Tasks
Planning ▪ Details of each task
and
Monitoring ▪ Case studies
(BAPM)
Key concepts
Key Concepts
Plan for:
▪ Approach & Method
▪ Time/Schedule/Cost
Planning ▪ Identify Risks, Constraints
Re-plan
BAPM
Control By:
Controlling Monitoring
▪ Taking actions to Collect data to Monitor for:
correct ▪ Plan
▪ Progress of project
▪ Actual Vs Planned
Key Concepts
An approach is a way of dealing with something
or somebody. Reactive Vs Preventive
Approach
A method is the process used or the steps
taken to execute/implement an approach. An
Method approach may be defined by a methodology.
Waterfall Vs Scrum
Key
Concepts
Technique An efficient way of doing something. UML Vs
User stories
Plan
A detailed course of action to achieve a goal
Business Analysis Planning and Monitoring
Deals with the definition and planning
of BA approach, governance and
monitoring
Describes how to improve business
BUSINESS ANALYSIS PLANNING analysis performance
& MONITORING
Know ledge Area
Produces outputs that are guidelines to
other tasks
Business Analysis Planning & Monitoring
01 Plan business analysis
approach 02 Plan Stakeholder
engagement
03 Plan Business analysis
governance 04 Plan Business Analysis
Information Management
05 Identify Business Analysis
Performance Improvements
Business Analysis Planning & Monitoring
1 Purpose
2 Inputs/Outputs
3 Elements
3.1 Plan Business Analysis Approach
4 Guidelines & Tools
TASK
5 Techniques
6 Stakeholders
Purpose, Inputs and Outputs
Defines appropriate
Approach defines the
method to conduct overall method, which Business Analysis
business analysis will be followed for an Needs
approach
activities on a given initiative
initiative.
Purpose Description Inputs Outputs
3.1
Plan Business
analysis
approach
Planning Approaches
Predictive Approach Adaptive
Defined before implementation to maximize Planning is overall and detailed for an iteration.
control and minimize risk Gets adapted based on iterations results
Formal approach - documented Informal – Team interactions vs documentation
Iterative approach, iterations are key to
WBS approach is used
division of tasks
Iterative delivery approach. Solution gets
Phase wise delivery approach
built iteratively
Plan Business Analysis Approach
P Planning Approach Predictive, Adaptive but mostly in continuum
Elements
Formality and Level of
Level of formality required for approaching and planning the
F Detail of Business Analysis
Deliverables initiative – Predictive or adaptive
B Business analysis activities Deliverable activities/ Iteration activities
I
Plan Business Analysis Approach
T Timing of BA Work When will the BA activities be performed. Phase wise execution
Elements
or iterative execution
C Complexity & Risk Complexity, size and risk are important considerations in
deciding the BA approach
A Acceptance Is the acceptance of BA approach formal/structured
Business analysis
performance assessment Expert Judgement
Guidelines & Tools
Business Policies Methodologies & Frameworks
Stakeholder engagement approach
Brainstorming. Lessons Learned Functional Decomposition
Business cases Process Modelling Interviews
Techniques
Document Analysis Reviews Item Tracking
Estimation Risk Analysis and
Survey or Questionnaire
Management
Financial Analysis Scope Modelling Workshops
Sponsor Regulator
Stakeholders
Domain Subject Matter Project Manager
Expert
Case Study
Case Study
V-COMMERCE.COM
An e-commerce startup believes that voice enabled e-
commerce platform is the future. Its business plan is
approved and squadron global has agreed to fund it for USD
300 million for the development and launch of this platform.
The project comprises of two distinct components
Developing e-commerce software platform
Developing voice enabled platform
An adaptive approach for voice enabled and more hybrid
V-Commerce.com approach for e-commerce
A plan is created with POCs and activities for iterations for
the voice enabled module. An MMF based plan is created
for releases
Risk profile is created considering the voice API accuracy
and feasibility aspects
Business Analysis Planning & Monitoring
1 Purpose
2 Inputs/Outputs
3 Elements
3.2 Plan Stakeholder Engagement
4 Guidelines & Tools
TASK
5 Techniques
6 Stakeholders
Purpose, Inputs and Outputs
Plan an approach to Identify stakeholders,
have an effective analyze their Needs,
characteristics, Define Stakeholder engagement
continued relationship Business Analysis
best collaboration approach
approach
with the stakeholders approach
.
Purpose Description Inputs Outputs
3.2
Plan stakeholder
engagement
approach
Plan Stakeholder engagement
An on-going activity. Finding stakeholder roles, their attitudes
Perform Stakeholder
P Analysis
towards the project, Decision making authority and level of
Elements
power or influence.
Define Stakeholder A planned activity to ensure stakeholder’s engagement with the
D Collaboration change initiative.
Stakeholder
S Communication Needs
What and how a stakeholder needs to be communicated through
the project.
Stakeholder Lists, Maps and Personas
3.2 PLAN STAKEHOLDER ENGAGEMENT
A list of stakeholders Depicts the
Shows responsibility of A fictional character to
to be used for relationship of
stakeholders in the show how a user
stakeholder analysis stakeholders with each
Summarizing
project activities interacts with a product
and further planning other and with solution
Stakeholder Lists Stakeholder Maps RACI Matrix Persona
Stakeholder
Analysis & Stakeholder characteristics: Roles, Attitudes
Stakeholder collaboration: Timing & frequency of
Collaboration Decision Making authority, Level of power and
collaboration, Location, Collaboration mechanism,
Delivery methods, Preferences of the stakeholders Influence
Business analysis
Change Strategy
performance assessment
Guidelines & Tools
Current state description
Brainstorming. Mind Mapping Stakeholder list, Map or
personas
Business Rules Analysis Organizational Modelling Survey or Questionnaire
Techniques
Document Analysis Process Modelling Workshops
Interviews Risk Analysis and
Management
Lessons Learned Scope Modelling
Customers Supplier Regulator
Stakeholders
Domain Subject Matter Project Manager
Expert
End Users Sponsor
Case Study
Case Study
Trac Suppliers LLC
Trac suppliers is an automobile spare parts manufacturing plant. They supply
the spare parts to the car manufacturing companies. The company wants to
implement SAP (Top ERP product) for managing its production as well as
inventory.
It has hired AG software Inc to implement the modules. AG Software has
given a timeline of 10 months and has submitted the implementation plan.
Robert Weiss is the Business Analyst of the project. Robert has been asked
to create the stakeholder communication and management plan.
Trac Suppliers – Stakeholder Matrix
Influence of Stakeholders
General Manager
CFO
Project Manager
Supplier
Tester Shop floor manager
Warehouse Manager
Impact on Stakeholders
Stakeholder communication plan
Communication Frequency Communication Delivery Audience Responsibility
action format Method
▪ Purchase Manager
Email/ ▪ Shop floor manager Project
Status Report Weekly Word document
Distribution List ▪ CFO Manager
▪ Project Manager
Business
Weekly Calls Every Friday Oral Call • General Manager
Analyst
Business Analysis Planning & Monitoring
1 Purpose
2 Inputs/Outputs
3 Elements
3.3 Plan Business Analysis Governance
4 Guidelines & Tools
TASK
5 Techniques
6 Stakeholders
Purpose, Inputs and Outputs
Define how decisions are
Governance process – Stakeholder engagement
taken about change Decision maker, process, approach,
control, reviews, info required for decision Governance approach
Business Analysis
prioritization, approvals... making approach
.
Purpose Description Inputs Outputs
3.3
Plan Business
Analysis
governance
Plan Business Analysis Governance
A stakeholder may be an approver or a reviewer of decision or
D Decision Making be providing input to decision making
Elements
It involves defining the process of requesting, analysing, documenting and
authorizing change requests.
C Change Control Process
▪ Impact Analysis
▪ Estimation of changes
Plan Prioritization
P Approach
How the prioritization will be decided.
P Plan for Approvals Plan to have appropriate approval process for a change
Business analysis
performance assessment Current state description
Guidelines & Tools
Business Policies Legal/Regulatory information
Brainstorming. Lessons Learned Survey or Questionnaire
Techniques
Document Analysis Process Modelling Workshops
Interviews Organizational Modelling
Item Tracking Reviews
Sponsor Regulator
Stakeholders
Domain Subject Matter Project Manager
Expert
Business Analysis Planning & Monitoring
1 Purpose
2 Inputs/Outputs
3.4 Plan Business Analysis Information 3 Elements
Management
4 Guidelines & Tools
TASK
5 Techniques
6 Stakeholders
WHAT IS BUSINESS ANALYSIS INFORMATION
Comprises of all the information that business analysts elicit, create, compile, and
disseminate in the course of performing business analysis.
E.g. models, scope statements, stakeholder concerns, elicitation results,
requirements, designs, solution options, requirements, designs, user stories, formal
requirement documents, functioning prototypes, etc.
Purpose, Inputs and Outputs
How business analysis Stakeholder engagement
How information be
information will be stored organized, level of approach,
Information management
and accessed detailing, relationships, Business Analysis
approach
accessed & stored approach, Governance
approach
.
Purpose Description Inputs Outputs
3.4
Plan Business
Analysis
Info management
Plan Business Analysis Information Management
BA information is organized for its efficient use and access
Organization of BA based on:
O ▪ Access and usage needs of stakeholders
Elements
Information
▪ Size and complexity of change
Detailing of BA information is decided on stakeholder’s role &
L Level of Abstraction importance of topic
BA plans the traceability approach based on:
Plan Traceability ▪ Complexity of domain
P Approach ▪ Organizational standards, Requirements risks, regulatory
requirements
▪ Costs and benefits for traceability
Plan Business Analysis Information Management
Plan for Requirements Requirements re-use can save time, cost & effort.
P re-use
Elements
Storage of business analysis information, access rights and
S Storage and Access conditions for access.
Requirements attributes allow business analysts to associate
R Requirements Attributes information with individual or related groups of requirements.
Guidelines & Tools
Business analysis
performance assessment Information Management tools
Business Policies Legal/Regulatory Information
Brainstorming. Lessons Learned Survey or Questionnaire
Techniques
Interviews Mind Mapping Workshops
Item Tracking Process Modelling
Sponsor
Stakeholders
Regulator
Domain Subject Matter
Expert
Business Analysis Planning & Monitoring
1 Purpose
2 Inputs/Outputs
3.5 Identify Business Analysis 3 Elements
Performance Improvements
4 Guidelines & Tools
TASK
5 Techniques
6 Stakeholders
Purpose, Inputs and Outputs
Assessment of Business
Define performance
analysis work and measures, conduct Performance Objectives
Business analysis
identification of analysis of data & take (External), Business
performance assessment
actions to improve Analysis approach
improvement areas
.
Purpose Description Inputs Outputs
3.5
Identify BA
performance
improvements
Identify Business Analysis Performance Improvements
Performance analysis is conducted to ensure effective business
P Performance
Analysis analysis work
Elements
Appropriate measures need to be identified to ensure effective
performance analysis. Measures could be – Quantitative and qualitative
A Assessment measures
Actual measurement data is compared against the defined measures.
A Analyze results
Recommend action for Based on gaps – preventive, corrective or improvement action can be
R improvement taken
Guidelines & Tools
Organizational performance Standards
Brainstorming. Observation Root cause analysis
Interviews Process Analysis Survey or Questionnaire
Techniques
Item Tracking Process Modelling Workshops
Lessons Learned Reviews
Risk Analysis &
Metrics and KPIs
Management
Sponsor
Stakeholders
Domain Subject Matter Project Manager
Expert
Case Study
An e-commerce company has hired an IT company to
develop a customer tracking application to manage
visitors who abandon the purchase cycle mid-way.
The project management team wants to monitor the
performance of the project and key professionals
including the business analyst.
Business Analysis performance metrics
Activities Expected value Measurement
Total number of defects
Number of defects 3 / Person Month -------------------------------------------
(Project months spent till then)
(Actual end date – actual start date) * 100
-----------------------------------------------------------
Schedule variance <= 3%
(Scheduled end date – Scheduled start date)
Business Analysis performance improvement
Activities Expected value Actual Value Correction action Preventive action
4 / Person month Conduct regular reviews to
Number of defects 3 / Person Month Get the defects fixed
(Iteration 1completion) prevent defects
Communicate to the
stakeholders for a
possible overall project Weekly (or reduce
5% delay frequency of
Schedule variance <= 3%
(Iteration 1completion) measurement) work
Evaluate for activity tracking
compensating as
variance is low
