This document outlines several tasks involved in business analysis planning and monitoring, including identifying stakeholders, developing estimates, planning communication, and determining metrics. Key tasks covered include planning the business analysis approach, conducting stakeholder analysis, planning business analysis activities and communication, planning requirements management, and managing business analysis performance. Inputs, elements, techniques and outputs are defined for each task.
2. WHAT IS BUSINESS ANALYSIS PLANNING
The Business Analysis Planning and Monitoring defines the tasks associated with
the planning and monitoring of business analysis activities i.e. identifying
stakeholders, defining roles and responsibilities of stakeholders in the business
analysis effort, developing estimates for business analysis tasks, planning how the
business analyst will communicate with stakeholders, planning how requirements will
be approached, traced, and prioritized, determining the deliverables that the
business analyst will produce, defining and determining business analysis processes,
determining the metrics tha.t will be used for monitoring business analysis work.
In addition, this are includes monitoring and reporting on work performed to
ensure that the business analysis effort produces the expected outcomes.
4. PLAN BUSINESS ANALYSIS APPROACH
Purpose
This task describes how to select an approach to performing business analysis, which
stakeholders need to be involved in the decision, who will be consulted regarding and
informed of the approach, and the rationale for using it.
Inputs:
Business Need, Expert Judgment, Organizational Process Assets.
Elements:
Timing of Business Analysis Work, Formality And Level Of Detail Of Business Analysis
Deliverables, Requirements Prioritization, Change Management, Business Analysis Planning
Process, Communication With Stakeholders, Requirements Analysis and Management Tools,
Project Complexity.
6. PLAN BUSINESS ANALYSIS APPROACH
Techniques:
Decision Analysis, Process Modeling, Structured Walkthrough.
Stakeholders:
Customer, Domain SME, End User or Supplier, Implementation SME, Project Manager,
Tester, Regulator, Sponsor.
Output:
Business Analysis Approach.
7. CONDUCT STAKEHOLDER ANALYSIS
Purpose
This task covers the identification of stakeholders who may be affected by a proposed
initiative or who share a common business need, identifying appropriate stakeholders
for the project or project phase, and determining stakeholder influence and/or authority
regarding the approval of project deliverables.
Inputs:
Business Need, Enterprise Architecture, Organizational Process Assets.
Elements:
Identification, Complexity of Stakeholder Group, Attitude and Influence, Authority Levels For
Business Analysis Work,
9. CONDUCT STAKEHOLDER ANALYSIS
Technique:
General Technique: Acceptance and Evaluation Criteria Definition, Brainstorming,
Interviews, Organization Modeling, Process Modeling, Requirements Workshops, Risk
Analysis, Scenarios and Use Cases and User Stories, Scope Modeling,
Survey/Questionnaire,
10. CONDUCT STAKEHOLDER ANALYSIS
TECHNIQUE(CNTD.)
RACI Matrix
The RACI matrix describes the roles of those involved in business analysis activities. It
describes stakeholders as having one or more of the following responsibilities for a
given task or deliverable:
[R]esponsible ▶ does the work,
[A]ccountable ▶ is the decision maker (only one)
[C]onsulted ▶ must be consulted prior to the work and gives input
[I]nformed ▶ means that they must be notified of the outcome
11. EXAMPLE RACI
Change Request Process R A C I
Executive Sponsor
Business Analyst
Project Manager
Developer
X
X
X
X
Tester X
Trainer X
Application Architect
Database Analyst (DBA)
Solution Owner
End User
X
X
X
X
Subject Matter Expert (SME)
Other Stakeholders
X
X X X
12. CONDUCT STAKEHOLDER ANALYSIS
Technique:
Stakeholder Map
Stakeholders:
Domain SME, Implementation SME, Project Manager, Tester, Regulator (process),
Sponsor.
Output:
Stakeholder List, Roles, and Responsibilities e.g. List of required roles, Names and
titles of stakeholders, Category of stakeholder, Location of stakeholders, Special
needs, Number of individuals in this stakeholder role, Description of stakeholder
influence and interest, Documentation of stakeholder authority levels.
13. PLAN BUSINESS ANALYSIS ACTIVITIES
Purpose:
Determine the activities that must be performed and the deliverables that
must be produced, estimate the effort required to perform that work, and identify
the management tools required to measure the progress of those activities and
deliverables.
Input:
Business Analysis Approach, Business Analysis Performance Assessment,
Organizational Process Assets.
Elements:
Geographic Distribution of Stakeholders, Type of Project or Initiative, Business
Analysis Deliverables, Determine Business Analysis Activities.
15. PLAN BUSINESS ANALYSIS ACTIVITIES
Techniques:
Estimation, Functional Decomposition, Risk Analysis
Stakeholders:
Customer, Domain SME, End User, and Supplier, Implementation SME, Operational
Support, Project Manager, Tester, Sponsor.
Output:
Business Analysis Plan(s)
16. PLAN BUSINESS ANALYSIS COMMUNICATION
Purpose:
A business analysis communications plan describes the proposed structure and
schedule for communications regarding business analysis activities. Record and
organize the activities to provide a basis for setting expectations for business analysis
work, meetings, walkthroughs, and other communications.
Input:
Business Analysis Approach, Business Analysis Plan, Organizational Process Assets,
Stakeholder List, Roles, and Responsibilities.
Elements:
Geography, Culture, Project Type, Communication Frequency, Communications
Formality,
18. PLAN BUSINESS ANALYSIS COMMUNICATION
Techniques:
Prepare Requirements Package, Communicate Requirements, Communication
Skills, Structured Walkthrough.
Stakeholders:
Customer and Supplier, Domain SME, End User, Implementation SME, Operational
Support, Project Manager, Tester, Regulator, Sponsor.
Output:
Business Analysis Communication Plan.
19. PLAN REQUIREMENTS MANAGEMENT PROCESS
Purpose:
Define the process that will be used to approve requirements for implementation and
manage changes to the solution or requirements scope.
Input:
Business Analysis Approach, Business Analysis Plan(s), Organizational Process
Assets.
Elements:
Repository, Traceability, Select Requirements Attributes, Requirements Prioritization
Process, Change Management, Tailoring the Requirements Management Process,
21. PLAN REQUIREMENTS MANAGEMENT PROCESS
Techniques:
Decision Analysis, Problem Tracking, Risk Analysis.
Stakeholders:
Domain SME, End User, Implementation SME, Operational Support, Project Manager,
Tester, Sponsor.
Output:
Requirements Management Plan.
22. MANAGE BUSINESS ANALYSIS PERFORMANCE
Purpose:
To manage the performance of business analysis activities to ensure that they
are executed as effectively as possible.
Input:
Business Analysis Performance Metrics, Business Analysis Plan(s), Organizational
Performance Standards, Requirements Management Plan.
Elements:
Performance Measures, Performance Reporting, Preventive And Corrective Action,
24. MANAGE BUSINESS ANALYSIS PERFORMANCE
Techniques:
General Techniques – Interviews, Lessons Learned Process, Metrics and Key
Performance Indicators, Problem Tracking, Process Modeling, Root Cause Analysis,
Survey/Questionnaire
Variance Analysis
Stakeholders:
Domain SME and End User, Implementation SME, Operational Support, and Tester,
Project Manager, Sponsor
Output:
Business Analysis Performance Assessment, Business Analysis Process Assets.
