Business Analytics

WEEKLY REPORT

Task 4.5 Manage Stakeholder Collaboration

Purpose: To achieve a desirable solution together with stakeholders.

Goal: To promote positive reactions and reduce the chances and impact of negative reactions.

 Begins as soon as stakeholders have been identified and analyzed.

 The stronger the initiative’s impact, the more collaboration management is needed.
 BAs must continuously monitor each stakeholder’s role and responsibilities.
 Positive and trust based relationships with stakeholders help overcome pitfalls.

INPUT PROCESS OUTPUT

INPUT PROCESS OUTPU

STAKEHOLDER
MANAGE T
STAKEHOLDER
STAKEHOLDER COLLABORATION
ENGAGEMENT
APPROACH COLLABORATION
BUSINESS
ANALYSIS
PERFORMANCE
ASSESSMENT

Stakeholders for this task are all the stakeholders.

Elements
  Gain agreement on commitments
 Monitor Stakeholder engagement
 Collaboration

Techniques

 Collaborative Games: Enhances teamwork within the group by having fun in a safe
environment wherein stakeholders can share experiences and thoughts.
 Lessons learned: Helps understand the stakeholder’s satisfaction levels and thereby
helps in improving relationships.
 Risk Analysis and Management: Can use risk analysis tools to mitigate poor
stakeholder participation
 Stakeholder List, Map or Personas: Start managing stakeholder collaboration,
including the relationships between stakeholders and understanding “who” should be
consulted “what”.

REQUIREMENTS ANALYSIS & DESIGN DEFINITION (PLEASE)

Also termed as RADD, the goal of this knowledge area is to analyze the need, create designs
that support the need, explore and analyze solution options and recommend the most effective
option.

It mainly involves exploring different solutions, for meeting the business requirements. Here,
activities are done iteratively and incremental from exploration of the initial needs to the
realization of those needs in a recommended solution. It also means taking elicited
requirements and organising, specifying, modelling, designing, verifying and validating them.
It also involves exploring different solutions and recommending the best among them.

Our team is brainstorming on different solutions to the stakeholder’s requirement of

increasing sales in their sports outlet.

Requirements represent the need and used to design the solution. Therefore a clear
understanding of the stakeholder’s requirements are necessary to design solutions. RADD
includes both feasibility and cost benefit analysis.
RADD TASKS

Task 1: Specify & model requirements

Task 2: Verify Requirements

Task 3: Validate Requirements

Task 4: Define Requirement Architecture

Task 5: Define Design Options

Task 6: Analyse potential value and Recommend Solution

The tasks has a Mnemonic: SEA ROAR

Task 1: Specify & model requirements

The purpose of this task is to transform elicitation results into actual requirements and
designs by refining them through analysis.

Elicitation
PROCESS
Specify & Model Requirements
Results Requirements

INPUT OUTPUT

Stakeholders: Any stakeholder

Guidelines/tools:
  Modelling tools
 Requirements architecture
 Modelling standards
 Requirements life cycle management tools
 Solution scope

Elements

 Model Requirements: Models are the representative tools which helps in pointing out
the gaps in elicitation results.
 Analyse Requirements: Requirements will be broken down into components until
appropriate details are collected.
 Represent Requirements and Attributes: Requirements and design are both needed to
be represented at an appropriate level of detail. Also should capture the requirements
attributes.
 Implement the appropriate level of abstraction: Abstraction refers to the level of
details provided to the stakeholders. Different stakeholders require different
perspectives on the representations. BAs should thus make sure all the stakeholder
views are provided.

Techniques

 Acceptance & Evaluation criteria: Answer the question- Will the stakeholders accept
the designs?
 Business capability analysis: Represent features and functions in an enterprise
 Business canvas model or BCM : Describe the rationale behind requirements
 Glossary: Define terms related to requirements
 Nonfunctional requirement analysis: Determines the attributes which are not directly
related to how it functions nor its features. These are quality requirements without
which solution is not acceptable.
 Roles and permission matrix: Helps in identifying the roles and responsibilities while
modelling activities.
 Root cause analysis: Helps diagnose the problems regarding needs through models
and diagrams.
Task 2: Verify Requirements

The purpose of this task is to confirm that requirements and designs meet quality criteria.

Elements

 Characteristics of Requirements and Design Quality: Should identify the

characteristics of a good requirement. For example, requirements should be within the
schedule and budget.
 Verification Activities: Verification is done throughout the effort and iteratively. It
includes checking for compliance with organizational performance standards such as
right tools, right methods etc.
 Checklists: Used for quality control when verifying requirements and designs. It may
include standard set of qualifying elements

Techniques

 Acceptance and Evaluation Criteria: Represent the criteria attributes for acceptance.
 Item Tracking
 Metrics and KPIs
 Reviews

Requirements Verify
PROCESS Requiremnts
(specified and Requirements (Verified)
modeled )

INPUT OUTPUT
All stakeholders are key at this step.

Task 3: Validate Requirements

Purpose is to ensure that requirements and designs align to business requirements and ensure
that requirements and designs satisfy the requirements.

Goal: Overall goal is to achieve stakeholder’s desired future state.

Requirements Validate
PROCESS Requirements
(specified and Requirements (Validated)
modeled )

INPUT OUTPUT

All stakeholders are required

Elements

 Identify assumptions: New requirements may not have precedents. Therefore there is
a need to list and validated assumptions made based on Stakeholder responses and
Customer responses.
 Define measurable evaluation criteria: Define metrics for expected benefits. And
define the evaluation criteria to identify appropriate metrics.
 Evaluate alignment with solution scope: Requirement may provide benefit to a
stakeholder but not provide overall alignment to desired future state. Therefore there
is a need to view benefit vis-à-vis alignment to desired state.

Techniques
 Acceptance and Evaluation Criteria
 Document Analysis
 Decision Analysis
 Reviews