By:

Deepali Bhardwaj



Requirements Lifecycle
Identification
of a Need
T
e
c
h
n
o
l
o
g
y

RFP
7/4/2014 2 Planning for Business Analysis
Stakeholder analysis
Planning BA activities
Requirements Management Process
Configuration management
Communication plan
Change management
Conflict resolution
Acceptance Criteria
Approval process and the authorizations
Business analysis performance

7/4/2014 3
Plan And Manage
Planning for Business Analysis
Any individual, group or institution who has a vested
interest in the project and/or who potentially will be
affected by project activities or outcome and have
something to gain or lose if conditions change or
remain the same
Anyone who can positively or negatively influence the
outcome of the project
Stakeholders
7/4/2014 5 Planning for Business Analysis
Identification of stakeholders who may be affected by
a proposed initiative or who share a common business
need
Determining stakeholder influence and/or authority
regarding the approval of project deliverables
Must clearly identify the roles, responsibilities, and
authority for each stakeholder or stakeholder group
over the requirements - RACI Matrix
Understand stakeholders attitude towards the
initiative

Stakeholder Analysis
7/4/2014 6 Planning for Business Analysis
Stakeholders Onion Diagram
7/4/2014 Planning for Business Analysis 7
Affected
External
Stakeholders
Organization /
Enterprise
Affected
Organization
Unit
Solution
Delivery
Project team and others directly
involved in creating the solution
End users, Help desk
and others whose work
changes when the
solution is delivered
Sponsors, Executives,
Domain SMEs and
others who interact with
the Affected Group
Customers, Suppliers,
Regulators and others
Person in-charge of the feature list
Prioritizes the list of features for highest ROI
Most likely from the Business and has most to
lose/gain from the project outcome
Knowledgeable, Empowered, Engaged
Accountable for project success
Only one who can add or remove features from the
feature list





Business Lead /Project Champion
7/4/2014 8 Planning for Business Analysis
7/4/2014 9
Methods Of Identifying Stakeholders
Role Brainstorming
Process Diagrams
Personas and Role Matrix
Shadowing
Surveys
Use Case Diagrams
Interviews
Planning for Business Analysis
For each stakeholder, document needs, attitudes,
influences, authority level for business analysis work
Attitude towards goals, objectives, approach,
collaboration, BA , Sponsor, Team members etc
Influence on project, good of the project, other
stakeholders, and within organization
Authority to approve deliverables, inspect and approve
requirements, request and approve changes, veto
proposed requirements etc





Managing Stakeholders
7/4/2014 10 Planning for Business Analysis
Develop a stakeholder engagement plan
Consider geographic distribution of stakeholders while
planning and SH analysis
Manage competing interests and goals among
stakeholders while avoiding conflict of interest
between stakeholders
Help stakeholders find and support common ground
requirements




Managing Stakeholders
7/4/2014 11 Planning for Business Analysis





Stakeholder Register
7/4/2014 12
NAME POSITION INTERNAL/
EXTERNAL
PROJECT
ROLE
CONTACT
INFORMATION
Stakeholder Register for <Project Name>

Prepared By: Date:
Planning for Business Analysis





Stakeholder Register
7/4/2014 13
NAME POSITION INTERNAL/
EXTERNAL
PROJECT
ROLE
CONTACT
INFORMATION
Ravi
Kumar
VP of HR Internal Project
Champion
ravik@xyz.com
Shayamli
Sharma
Training
Director
Internal Project
Sponsor
shayamlis@xyz.c
om
Stakeholder Register for <Project Name>

Prepared By: Date:
Planning for Business Analysis





Stakeholder Matrix
7/4/2014 14
I
n
f
l
u
e
n
c
e

o
f

S
t
a
k
e
h
o
l
d
e
r

Impact on
Stakeholder
Low High
High
Low
Monitor to ensure SHs
interest or influence
do not change
Keep informed; SH is
likely to be very
concerned and may feel
anxious about lack of
control
Work closely with SH
to ensure that they are
in agreement with
and support the
change
Ensure SH remains
satisfied
Planning for Business Analysis




`
Identify Key Stakeholders To Focus
7/4/2014 15
I
n
f
l
u
e
n
c
e

Advocacy
Low High
High
Low
Minority Friend
Promoter Opponent
Can be time wasters
Need to focus here
Planning for Business Analysis





Stakeholder Management Strategy
7/4/2014 16
Name Level of
Advocacy
Level of
Influence
RACI Profile Potential
Management
Strategies
Stakeholder Management Strategy for <Project Name>

Prepared By: Date:
Use RACI matrix to describe the roles of those involved in business
analysis activities
Planning for Business Analysis





Stakeholder Management Strategy
7/4/2014 17
Name Level
of
Advoca
cy
Level
of
Influe
nce
RACI Profile Potential
Management
Strategies
Action Items
Ravi
Kumar
High High A,I Is a visionary. MBA
and concerned about
financials.
Keep him informed
and seek advise
when needed
Fortnight
Updates with a
focus on
Financials
Shayam
li
Sharma
High High R PhD in education
and looks after
training. Very
professional
Ensure she reviews
documents before
showing it to other
managers
Weekly update on
the progress of
the BA activities.
Plan for all
deliverables to be
reviewed by her
before release.
Send her the
review plan.
Stakeholder Management Strategy for <Project Name>

Prepared By: Date:
Planning for Business Analysis
Overall process that will be followed for Business
Analysis activities
BA approach waterfall, iterative, agile
Work Break down: Which BA activities performed when
and where
Deliverables and Milestones
Management tools used to monitor the progress and
performance
Factors influencing the plan can be distribution of
stakeholders, complexity of the initiative etc
Output: BA Plan document



Plan BA Activities
7/4/2014 18 Planning for Business Analysis
Identify the attributes that will be captured for every
requirement
Ref num, Author, Complexity, Ownership, Priority, Risk,
Source of requirement, Stability, Status
Requirements prioritization process
Communication plan
Configuration Repository:
Storing requirements and other artifacts
Version control

Plan Requirements Management Process
7/4/2014 19 Planning for Business Analysis
Change Management: Determining the process for
requirements change
Who can initiate a change
Who will approve changes
Who will be consulted and informed
Traceability : Plan for requirements traceability
Conflict resolution process
Output : Requirements Management Plan
Plan Requirements Management Process
7/4/2014 20 Planning for Business Analysis
How best to receive, distribute, access, update and
escalate information from project SHs and
communicate to all SHs
Considerations for Communication
What needs to be communicated
What should be the delivery mechanism
Status reports, MOMs, structured walkthroughs etc
Who is the appropriate audience
Frequency: When should communication happen


Communication Plan
7/4/2014 21 Planning for Business Analysis
Stakeholder needs and constraints relevant to
communication include:
Physical location/time zone of the stakeholders
Communication approach for the stakeholder
What types of communications will be required (e.g.
status, anomalies, issues and their resolution, risks,
meeting results, action items, etc.)
How best to communicate requirements
conclusions/packages, including authority level (signoff
authority, veto authority, or review only)
Output: Communication plan


Communication Plan
7/4/2014 22 Planning for Business Analysis
Manage performance of business analysis activities
Elements of Performance Management
Identify metrics and capture data
Analyze
Performance reporting
Implement preventive and corrective measures
Examples of Metrics can be
Timely delivery
No of changes in the requirements
Feedback from stakeholders
Number of review cycles required
Output : BA Performance Plan
Plan To Manage Business Analysis Performance
7/4/2014
23 Planning for Business Analysis
Lay the ground work
Bring all stakeholders on the same page
Purpose of project: Goal
Scope of work
Stakeholders
Constraints
Naming conventions
Relevant facts and assumptions
Estimated cost
Risks
First cut Prototype
Seek commitment and support
Kick-Off For Requirements Gathering
7/4/2014 24 Planning for Business Analysis
Lay the ground work
Key Deliverables
Purpose of project: Goal
Scope of work :
Stakeholders
Constraints
Naming conventions
Relevant facts and assumptions
Estimated cost
Risks
First cut Prototype
Kick-Off For Requirements Gathering
Context model that shows
connections between work and
adjacent systems
7/4/2014 25 Planning for Business Analysis