CBAP Perparation

Barath
Business Analysis Planning &
Monitoring
The Business Analysis Planning and Monitoring Knowledge
Area defines the tasks
associated with the planning and monitoring of business
analysis activities, including:
identifying s ▶▶ takeholders
▶▶ 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 that will be used for monitoring
business analysis work
In addition, this knowledge area describes the work involved
in monitoring and reporting
on work performed to ensure that the business analysis effort
produces the expected
outcomes. If these outcomes do not occur, the business
analyst must take corrective
action to meet stakeholder expectations.
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.

describe the overall process, how and when tasks will be performed,the techniques that will be used, and the deliverables that
should be produced. established ways, Softaware- waterfall,agile Business process improvement- lean and six sigma. organizations
will have formal or informal standards in place,Tailoring may be governed by organizational standards that define which approaches
are permitted.

The business analysis approach is often based on or related to the project approach, but in some cases they may be independently
determined

Inputs
Business Need: when,what is needed .Expert Judgment: for selecting optimal approach.Organizational Process
Assets Organizational Process Assets- tools,procedures, policy ,guideline, templates .

methodologies Plan-driven approaches focus on minimizing up-front uncertainty and ensuring that thesolution is fully defined before
implementation begins in order to maximize control andminimize risk.Plan-driven approaches focus on minimizing up-front
uncertainty and ensuring that thesolution is fully defined before implementation begins in order to maximize control andminimize
risk.

Change-driven approaches focus on rapid delivery of business value in short iterationsin return for acceptance of a higher degree of
uncertainty regarding the overall deliveryof the solution. These approaches tend to be preferred when taking an
exploratoryapproach to finding the best solution or for incremental improvement of an existingsolution. The authority to approve
requirements usually rests with a single individual,who is an active participant in the team’s daily activities—others may advise or
beinformed but may not withhold consent, and the approval process must be completedwithin a strict time limit. Agile methods of
software development, as well as
Timing of Business Analysis Work, when the work/task and
how long will it be performed- Plan-driven : at the beginning
.Change driven : Performed iterative after initial work.
Formality And Level Of Detail Of Business Analysis
Deliverables: Plan-driven- More formal, approval is needed.Can
be multiple document with varying level of detail. Change
driven:- minimal document, done at the end for KT. Mandatory
is prioritized requirement list. Acceptance criteria .
Requirements Prioritization:Determine how requirements will
be prioritized and how those priorities will be used to define the
solution scope
Change Management
Consider the expected likelihood and frequency of change and
ensure that the change management process is effective
forthose levels of change Plan-driven:mini project if genuinely
necessary. change driven: no separate change management
process
Business Analysis Planning Process-part of project plan
Communication with Stakeholder-Plan-driven formality,
change-driven frequency.
Requirements Analysis and Management Tools

Project Complexity.
techniques: Decision analysis,process Modeling,Structured
walktrhu.

Customer , Enduser, Domain SME, Supplier. Implementation

SME
PM,tester,regulator , Sponsor.

business analysis approach may specify team roles,

deliverables, analysis techniques, the timing and frequency of
stakeholder interactions, and other elements of the business
analysis proces
Conduct Stakeholder Analysis

Purpose

identification of Stakeholders 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

Input
Description
Stakeholder analysis is performed as soon as a business
need is identified and will usuallybe an ongoing activity as long
as business analysis continues.identified and grouped.

The roles, responsibilities, and authority over the requirements

for each stakeholder or stakeholder group must be clearly
described. influence on and attitude towards the initiative,
andassessing positive and negative attitudes and behaviors

Input Business Need.Enterprise Architecture,Organizational

Process Assets
Conduct Stakeholder Analysis
Identification: Later identification can modify and nullify work done

Complexity of stakeholder : Number and variety of direct end users ;

Attitude and Influence: The business goals, objectives, and solution approach, business analysis, collaboration,sponsor:, team
members
.Influence: strategies for obtaining buy-in.the project.,the organization, needed for the good of the project, with other
stakeholders.
Authority Levels For Business Analysis Work: authority over business analysis activities, in relation to both business analysis work
and product deliverable Approve the deliverables;Inspect an d approve the requirementsRequest and approve changes;Approve
the requirements process that will be used;Review and approve the traceability structure;Veto proposed requirements or solutions
(individually or in a group;

Acceptance and Evaluation Criteria Definition, Brainstorming, Interviews, Organization Modeling, Process Modeling ,
Requirements Workshops, Risk Analysis, Scenarios and Use Cases (9.26), and User Stories, Scope Modeling,
Survey/Questionnaire

RACI Matrix, [R]esponsible, [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

Stakeholder Map A matrix mapping the level of stakeholder influence against the level of stakeholder interest. An onion diagram
indicating how involved the stakeholder is with the solution

Domain SME:, Implementation SME, Project Manager, Tester:,Regulator: Sponsor

Plan Business Analysis Activities

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.

Identify business analysis deliverables Determine the scope of work for the business analysis activities Determine which activities
the business analyst will perform and when Develop estimates for business analysis work.

rolling-wave high-level plan for the long term and detailed plans to address near-term activities.

Input: Business Analysis Approach,Business Analysis Performance Assessment,Organizational Process Assets,Stakeholder List,
Roles, and Responsibilities.

Elements : Geographic Distribution of Stakeholders (Collocated,Dispersed),Type of Project or Initiative

Business Analysis Deliverables- Methods for identifying, 1. Interviews or facilitated sessions w ▶▶ ith key stakeholders,Review
project documentation, Review organizational process assets, such as methodologies and templates, Frequently, additional
techniques may be selected on an ad-hoc basis during execution
Determine Business Analysis Activities: The WBS decomposes the project scope into smallerpieces, creating a hierarchy of
work. iterations, releases, or phases; break deliverables into work packages; or break activities into tasks.
This decomposition of activities and tasks creates activity list.( Unique Number, Activity description, assumptions, dependecies,
Milestone)

Techniques: Estimation and Functional Decomposition, Risk Analysis

Customer, Domain SME, End User, and Supplier: Domain,Implementation SME, Operational Support:,Project
ManagerTester:, Sponsor:
Requirements Management &
Communication
managing and expressing requirements to a broadand diverse
audience.
ensure that all stakeholders have ashared understanding of
the nature of a solution and to ensure that those
stakeholderswith approval authority are in agreement as to
the requirements that the solution shall meet.

Communicating requirements helps to bring the stakeholders

to a common understanding of the requirements. Because the
stakeholders represent people from different backgrounds and
business domains, this communication is both challengingand
critical to the success of any initiative. It involves determining
which sets ofrequirements are relevant to a particular
stakeholder group and presenting thoserequirements in an
appropriate format for that audience
.Management of requirements assists with understanding the
effects of change andlinking business goals and objectives to
the actual solution that is conucted and delivered. Over the
long term, it also ensures that the knowleand understanding
of\the organization gained during business analysis is
avaiable for future use.
Plan Business Analysis Communication
Purpose
A business analysis communications plan describes the
proposed structure and schedule for communications
regarding business analysis activities. determining how
best to communicate with each stakeholder.appropriate
for a particular initiative and its stakeholder
input: Business Analysis Approach,Business Analysis
Plan,Organizational Process Assets,Stakeholder List,
Roles, and Responsibilities.

Elements. Geography,Culture,Relationship to time,task

completion,contracts,formal and informal authority.Project
Type,Communication Frequency,Formality.
Technique: Structured Walkthrough and Requirements
Package (4.4) and Communicate Requirements (4.5)
Stakeholder all.
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.

This task determines the appropriate requirements management process for a particular initiative. It includes determining the
process for requirements change, which stakeholders need to approve change, who will be consulted or informed of changes, and
by extension, who does not need to be involved. The task also includes assessing the need for requirements traceability and
determining which requirements attributes will be captured.

Input Business Analysis Approach,Business Analysis Plan,Organizational Process Assets,

Elements: Repository,
Traceability,
Attributes: Requirements attributes provide information about requirements, such as the source of the requirement, the importance
of the requirement, and other metadata. Attributes aidin the ongoing management of the requirements throughout the project
lifecycle. (Absolute reference, Author of the requirement, Complexity, Ownership, Priority, Risks, Source of the
requirement,Stability,Status,Urgency, additional attributes

Requirements Prioritization ProcessFormality.Establishing The Process And Technique,Plan The Participation

Change Management:process for requesting changes,who will authorize changes,Impact Analysis,Plan the wording of the request
(Cost and time estimates of change,Benefits and risks of the change,Recommended course of action for change,Coordinate
Prioritization Of Chan,
Tailoring the Requirements Management Process, An organization’s requirements management process may need to be tailored to
meetthe needs of a specific initiative or project.
Factors in the tailoring process include:Organizational culture;Stakeholder preferences;Complexity of project, project phase, or
product,Organizational maturity,Availability of resources

Techniques: Decision Analysis; Problem Tracking: Risk Analysis ;Stakeholder: domain SME, Implementation SME, Project manager,
Sponsor, tester

Stakeholders:
Elicitation

Eliciting requirements is a key task in business analysis. Because the requirements serve as the foundation for the solution to the
business needs it is essential that the requirements be complete, clear, correct, and consistent. Leveraging proven means toelicit
requirements will help meet these quality goals. The definition of elicitation is1:to draw forth or bring out (something l 1. atent or
potential)2. to call forth or draw out (as information or a response)These definitions highlight the need to actively engage the
stakeholders in defining requirements

It is expected that at some point while performing elicitation that sufficient material will have been elicited from the business experts
to allow analysis activities to begin. The combined results of all the elicitation techniques used will serve as input to building the
selected analytical models. Missing, incomplete or incorrect requirements will ideally be exposed during the analysis activities, thus
requiring additional elicitation.
Prepare for Elicitation
Purpose
Ensure all needed resources are organized and scheduled for
conducting the elicitation
activities.Build a detailed schedule for a particular elicitation
activity, defining the specific
activities and the planned dates.

Input: Business Need,Solution Scope and Business

Case, Stakeholder List, Roles, and

ResponsibilitiesClarify the specific scope for the selected

elicitation technique and gathers any
necessary supporting materials.
• Schedule all resources (people, facilities, equipment).
• Notify appropriate parties of the plan.
For event-based elicitation (brainstorming, focus group,
interview, observation, prototyping, requirements workshop)
ground rules must be established. Agreement
is reached with the stakeholders as to the form and frequency
of feedback during the elicitation process as well as the
mechanism for verifying and signing off on the elicited
results.

Technique: Brainstorming ,Document Analysis ,Focus Groups

,Interface Analysis ,Interviews ,Observation ,Prototyping
,Requirements Workshops ,Survey/Questionnaire
Conduct Elicitation Activity

Purpose
Meet with stakeholder(s) to elicit information regarding their
needs.Description The elicitation event takes place
(brainstorming, focus groups, interviews,
observation, prototyping, requirements workshops), or
elicitation is performed (document analysis, interface analysis)
or distributed (survey/questionnaire).
Input: Business Need,Organizational Process
Assets,Requirements Management Plan,Scheduled
Resources,Solution Scope and Business Case,Supporting
Materials

Elements: Tracing requirements,Capturing requirement

attributes,Metrics

Techniques: Data Dictionary and Glossary:

Stakeholder Customer, Domain SME, End User, Supplier and
Sponsor.Implementation SME, Operational Support, Project
Manager, Supplier and Tester , Regulator,
Manage Solution Scope &
Requirements
Purpose
Obtain and maintain consensus among key stakeholders
regarding the overall solution
scope and the requirements that will be implemented.

Input: Requirements Management Plan, Solution

Scope, Stakeholder List, Roles, and Responsibilities,
Stakeholder, Solution, or Transition Requirements
[Communicated or Traced]

Elements : Solution Scope Management- align to business

goals. additional needs may be valid or invalid. so amend
business requirements or make agreement with stakeholder

Conflict management and issues management: inconsistent

requirement, conflicting priorities , different perspectives.

Presenting requirement for review; Formal vs informal.

Approval. Is must for finalizing and necessary change history
has to be maintained

Techniques. Problem tracking, Signoff, Baselining .

Stakeholder: domain SME, Implementation SME, Project

manager, Sponsor
Document Elicitation Results

Purpose
Record the information provided by stakeholders for use in
analysis.

Description
For an elicitation event (brainstorming, focus groups,
interviews, observation,
prototyping, requirements workshops) a summary of the
output from the event, including
issues is produced.

Elicitation Results: Includes the information provided by

stakeholders that will be
recorded and structured.

Elements
Documentation can take a number of forms, including:
▶▶ Written documents describing the outcomes, such as
meeting minutes
▶▶ Visual or audio recordings
▶▶ Whiteboards (either actual or virtual)
Confirm Elicitation Results

Purpose
Validate that the stated requirements expressed by the
stakeholder match the stakeholder’s understanding of the
problem and the stakeholder’s needs Description Some
elicitation techniques benefit from reviewing the documented
outputs with the stakeholders to ensure that the analyst’s
understanding conforms to the actual desires or intentions of
the stakeholder.

Input
Requirements [Stated, Unconfirmed]:
Stakeholder Concerns [Unconfirmed]:

Elements
Refer to the description of the relevant technique for unique
aspects of confirming the
results of the Interview and Observation techniques.

Techniques
▶▶ Interviews (9.14)
▶▶ Observation (9.18)
Manage Business Analysis
Performance
Purpose
To manage the performance of business analysis activities to ensure that they are executed as effectively as possible.This task
covers determining which metrics will be used to measure the work performedIt includes how to track, assess, and report on the
quality of. the work and take steps to correct any problems that may arise

Input: Business Analysis Performance Metrics:;Business Analysis Plan(;Organizational Performance Standards; Requirements
Management Plan.

Elements: Performance Measures: to set expectations regarding what constitutes effective business analysis work
Performance Reporting: Reports can be in written format to provide for archival and tracking, formal or informal.
Preventive And Corrective Action: Preventative or corrective action is likely to result in changes to the business analysis plan
Techniques: Interviews;Lessons Learned Process;Metrics and Key Performance Indicators;Problem Tracking;Process
ModelingRoot Cause Analysis:Survey/Questionnaire.
Variance Analysis: discrepancies between planned and actual performance, determine the magnitude of those discrepancies, and
recommend corrective and preventive action as require

Stake holder : Domain SME and End User, Implementation SME, Operational Support, and Tester, Project Manager:, Sponsor
Manage Requirements Traceability

Purpose
Create and maintain relationships between businesis
objectives, requirements, other team deliverables, and
solution components to support business analysis or
other activities.

“Tracing” a requirement refers to the ability to look at a

requirement and the others to which it is related. Tracing links
business requirements to stakeholder and solution
requirements, to other artifacts produced by the team, and to
solution components

Derivation and allocation, All types of project management,

risk and impact assessment. Relationship management
Impact assessment , coverage, and allocation

Input; Requirement and management plan

Elements : Relationship(necessity, cover, subset, effort value),

Impact analysis and config mgmt(tools).

Technique : Coverage matrix

Stakeholder: Implementation SME , Project manager,tester

Maintain Requirements for Re-use

Purpose
To manage knowledge of requirements following their
implementation
candidates for long-term usage, meet on an ongoing basis

facilitate impact analysis of new, proposed changes to the

business, reduce analysis time and effort, assist in
maintenance of previously implemented solutions, and
support other activities, including training, corporate
governance, and standards compliance

input: Organizational Process Assets, Requirements:

Elements:Ongoing Requirements,Satisfied Requirements

Stake holder, new BA, Implementation SME, Domain

SMERequirements [Maintained and Reusable]: The output of

this task are requirements thatare expressed in a form that
makes them suitable for long-term usage by the
organization(even in the absence of the stakeholders who
originally defined the requirements). Theymay become
organizational process assets or be used in future initiatives or
projects. Insome cases a requirement that was not approved
or implemented may be maintained fora possible future
initiative.
Prepare Requirements Package
structure a set of requirements in an appropriate
fashion extent needed
Formal Documentation:Presentation:Models
:Business Analysis Communication Plan:Organizational
Process Assets:Requirements:Requirements Structure
Work Products and Deliverables
Format

Each requirements package may have a Table of Contents

outlining what is included inthe package. Grouping of the
requirements into categories should be clearly identified inthe
Table of Contents for ease of navigation. It may also include a
revision log to documentchanges between versions and help
stakeholders verify that they have the most recentversion.

Techniques Requirements Documentation;

BRD,SRD

Requirements for Vendor Selection

RFI
RFP
RFQ

StakeholdersDomain SMEs and End Users:Implementation

SMEs:Project Managers:Regulators:SponsorsTesters:

Requirements Package
Communicate Requirements

Purpose Communicating requirements is essential for bringing

stakeholders to a common understanding of requirements.

conversations, notes, documents, presentations,

and discussions. Concise, appropriate, effective
communication

Input: BA communication plan, Requirement , requirement

package.

Business Analysis Communication

Plan,Requirements Requirements Package:

General Communication
Presentations- Formal or informal

Techniques:
Requirements Workshops and structured walkthru
Enterprise Analysis
identify a business need, problem, or opportunity, define the
nature of a solution that meets that need, and justify the
investment .
provide context to requirements analysis and to solution
identification

. Enterprise analysis
is often the starting point for initiating a new project and is
continued as changes occur and more information becomes
available.

business requirements are identified and documented.

It Analyze the business situation in order to fully understand

▶▶ business problems and opportunities.
▶▶ Assess the capabilities of the enterprise in order to
understand the change needed to meet business needs and
achieve strategic goals.
▶▶ Determine the most feasible business solution approach.
▶▶ Define the solution scope and develop the business case
for a proposed solution.
▶▶ Define and document business requirements (including the
business need, required
capabilities, solution scope, and business case).
Assess Capability Gaps- What we have

Purpose
To identify new capabilities required by the enterprise to meet
the business need

Assess the current capabilities of the enterprise and identify

the gaps that prevent it
from meeting business needs and achieving desired
outcomes

Input Business need, solution performance,Enterprise arc

Current capabilities are assessed against the desired

objectives to determine whether the organization currently has
the capability to meet the business need
Assessment of New Capability Requirements : If current
capabilities are insufficient to meet the business need, the
business analyst must identify the capabilities that need to be
added. comparison of the current and desired future states
will identify gaps.

assumptions must be identified and clearly understood,so

that appropriate decisions can be made if the assumption later
proves invalid.

Techniques: Document analysis , SWOT analysis.

Customer supplier, implementation SME,Sponsor Domain
SEM
Determine Solution Approach
Purpose
To determine the most viable solution approach to meet the
business need in enough detail to allow for definition of
solution scope and prepare the business case.

Input Business Need,Organizational Process Assets Required

Capabilities:

Elements :
Generating alternatives : Do nothing, buy time, get as many till
you get diminishing returns, acceptable, non repetitive

Assumptions and constraints Assumptions and constraints

should be questioned to ensure that they are

Rank the option

Capture consistent information on feasibility of the options and
rank them
A scoring system can be used for complex criteria

Benchmarking , brainstroming , decision analysis , SWOT

analysis, Estimation.
Prototyping formal and informal
Customer, Domain SME, End User and Supplier,
Implementation SME and SPonsor (source of constraints)
Define Solution Scope

Purpose
To define which new capabilities a project or iteration will
deliver.

The purpose of this task is to conceptualize the recommended

solution in enough detail
to enable stakeholders to understand which new business
capabilities an initiative will
deliver.

Changes based on changes in the business environment

or project scope,The scope of analysis,capabilities,releases
or iterations, enabling capabilities

Assumptions and constraints, business need, Solution

approach , required capabilities.

Solution scope definition (area of change), Implementation

approach, dependency (business and technical)

techniques: Functional decomposition. Interface analysis ,

scope modeling and user stories.

Problem or vision statement.

Stakeholders:
 Define Business Case
Purpose
To determine if an organization can justify the investment
required to deliver a proposed
solution

the justification,qualitative and quantitative benefits, estimates

of cost and time to break even, profit expectations,and follow
on opportunities.constraints associated with theproposed
project, along with the estimated budget,and alignment with
strategies established by organization.

Input Assumptions and Constraints,Business Need:,Solution

Scope:,stakeholder concerns.(risk and issues)

Benefit, Qualitative and quantitative

Cost, all type of cost
risk assessment- is the solution is risky, Feasibility ,technical ,
organizational business. and financial risk

Techniques Decision analysis , Estimation , metrics and KPI.

Risk analysis and SWOT analysis, vendor Assessment.

Stakeholders

Sponsor , domain sme , implementation SME and PM.

.
Define Business Need - What we
need?
Purpose
Identify and define why a change to organizational systems or
Self identified audit issues,customer esclations,SOX and other
audit issues
, Input from legal team, Dodd Frank , Durbin ect.
capabilities is required.
JAD, BRD , Project charter.
Output Project objective
The business need defines the problem that the business analyst is
trying
to find a solution for.
way the business need is defined determines which alternative will
be considered

It is common for organizations to act to resolve the issue without

investigating the
underlying business need.question the assumptions
Goals and Objective
describe the ends that the organization is seeking to achieve.
Goals are high level, focus area are specific goal component ,
objectives are granular goal blocks.
SMART.

In every issue there may be opportunity , Root cause, impact,

benefit of a fix, and time for resolution.

Desired outcome is the target state that business will attain.

Benchmarking, brainstorming, Business rule analysis, Functional

decomposition and root cause anal
Customer or Supplier,Domain SME and End
User: Implementation SME,Regulator , Sponsor.
 Prioritize Requirements
Need: focus High impact, high visible , legal compliance request are given
on the most critical requirements precedence

decision process used to determine the relative

importance of requirements, value, risk,etc

Input, business care or need, requirements, management plan

and stakeholder

Basis
Business Value(incremental solution),Risk , Difficulty( gain
familiarity) ,success(to gain confidence) ,
compliance, Dependencies , stakeholder agreement and
urgency.

challenges

To avoid taking tough decision stakeholder may provide

1. Nonnegotiable demand
2. Unrealistic trade-off ( over estimation to influence a option
Stakeholder
Domain sME , Implementation SME , PM , Sponsor

techniques
Decision analysis, risk analysis, MoSCoW.
Time boxing( all in, all out, selctive after determining solution
apprach), voting
 Prioritize Requirements
Need: focus High impact, high visible , legal compliance request are given
on the most critical requirements precedence

decision process used to determine the relative

importance of requirements, value, risk,etc

Input, business care or need, requirements, management plan

and stakeholder

Basis
Business Value(incremental solution),Risk , Difficulty( gain
familiarity) ,success(to gain confidence) ,
compliance, Dependencies , stakeholder agreement and
urgency.

challenges

To avoid taking tough decision stakeholder may provide

1. Nonnegotiable demand
2. Unrealistic trade-off ( over estimation to influence a option
Stakeholder
Domain sME , Implementation SME , PM , Sponsor

techniques
Decision analysis, risk analysis, MoSCoW.
Time boxing( all in, all out, selctive after determining solution
apprach), voting
Organize Requirements
need:to create a set of views of the requirements. comprehensive,
complete, consistent, and understood
from all stakeholder perspectives.

appropriate model,model interrelationships and dependencies

Organizational Process Assets, Requirements, Solution scope .

1.Follow org standard.2. Simple natural and consistent

language,3.Document dependency , 4. Consistent set of documents.

Level of abstraction. ( what and not how).

Model selection. High to low and methodologies

abstract and simplify reality develop multiple models using different

modeling techniques. No hierarchy .Popole ( User class, role , profile)
usecase,process,orgobject(concepts and relationship) Data
modelsEvent - Scope Model, process, use case, state Process -
process, use case, state , orgRules - process, use case, state

Domain SME, End User, Implementation SME, and Sponsor Project

Manager
Specify and Model Requirements

Purpose analyze expressed stakeholder desires and/or the

current state of the organization.

opportunities for improvement.

- assist in
development and implementation of solutions
facilitating
communication
training
knowledge
management
compliance

Input requirement stated and requirement structure

Elements : text, select models, matrix . - Improvment

opportunities, attributes

Automate Or Simplify The Work People Perform, Improve

Access To Information:Reduce Complexity Of
Interfaces:Increase Consistency Of Behavior:Eliminate
Redundancy:
Define Assumptions and Constraints

Purpose
Identify factors other than requirements that may affect which
solutions are viable.

Definition. Assumption are assumed to be true. has risk.

Constraints , restrictions or limitations

Stakeholder concerns

Assumptions
believed to be true- not verified, source of potential project risk
.

Constraints business and technical

Problem tracking and risk analysis

Verify Requirements

Purpose: specifications and models meet

the necessary standard of quality

Description: Requirement has to be defined correctly with

sufficient quality .Ready for formal review validation and
further work.

Input Any requirement except stated.

1. Characteristics of quality
Cohesive, Complete, consistent, Correct, Feasible, Modifiable
, unambiguous , testable

Need to Check
1.Completeness , consistency, variance and variance triggers
and outcomes, terminology , examples

acceptance and evaluation criteria

Problem tracking
structured walkthru
checklist

all stakeholders
Validate requirements

Purpose: Requirement align to business goal/objective,

stakeholder needs

Requirements must be complete to achieve desired state.

Sometime stakeholders will have conflicting requirements and
they have to reconciled

Business case( and its inputs), Requirements

Identify assumptions .-- wont have proof for everything
Define measurable evaluation criteria
Determine business value (qualitative quantitative,
elimination)
Determine dependency for benfit realization
Evaluate alignment with business case and opportunity cost
should be minimized

Acceptance and evaluation criteria

metrics and key performance indicators
prototyping
risk analysis
structured walk thru

All
Assess Proposed Solution

determine how closely they meet stakeholder All the possible options are considered, eg. conversion from a
and solution requirements. to b , b to a , a and b to c ect.
various criteria are ranked and best solution is taken.
Assumptions and Constraints:
Requirements [Prioritized and Approved]: Identification of additional capabilities like , making
Solution Option(s): generic engine , generic database etc are done.

Ranking of Solution Options

Lesser the criteria easier it to decide ,For complex criteria a
scoring system can be deployed.
Identification of Additional Capabilities, unused, easy to
implement, future benefit that are not in business case.
Scoring will be done such that acceptance of solution is
visible
Decision analysis like , Discounted cash flow, present value
return, payback perid and return of investment are used to
rank solutions

If outsourced then vendor details, sla are analyzed

Acceptance and Evaluation Criteria Definition (9.

Decision Analysis

Vendor Assessment The output of this task is used in solution selection and
design
Domain SME. Implementation SME ( interoperability)
Operational support ( limitation feedback). Project manager,
supplier and sponsor.
Allocate Requirements

Purpose:allocate requirements among solution components
and releases, maximize business value and minimize cost, By
how and when they are implemented
High level requirements are split at Org Level ( like Customer
system, core system, ops system), people role - analytic and
operations
or between software , like core and support , between
releases , like phase 1, phase 2 etc

Type of solution components encountered

1 Org change, 2, Software system change, 3. Process
It is an ongoing process change, 4. Rules change. 5, People change

Requirement - approved , Solution design will again warrant revisiting allocation

Solution Scope- business requirement will be mapped
Solution [Designed]- granularity in cost and effort
Solution Components
What the L2 and L3 can take ,and what needs to be done
manually by law and what data is needed.
And dependency

Available resources: Release calendar, freeze period ect.

Constraints on the solution
Dependencies between requirements

Release Planning
Release Planning, Release calendar , Freeze , RCP,
Legal requirements.
Asses Organization Readiness

Purpose: Is every one ready to use. Purpose: check if every one ready for new solution.

describes the effect, is prepared for the organizational
change.
Effective communication assist in identifying training
requirements
end to end impact vision
Input. Stakeholder concerns, Solution designed, Solution
scope, Enterprise architecture
Elements
Culture: attitude, willingness, belief, understanding, feelings.
Operations or technical assessment; hardware
software,training, manuals and rules
Stakeholder impact.
Concerns, jobs, skills , efficiency, satisfaction, work load
Task, Changes, complexity , flexibility, skill levels
Location; ways of communication
Functions ; where do the people fit in.
impact on ops, L2 , L3 org structure ops , training for
associates. Roles , responsiblity location ect.
Elements
attitude, willingness, belief, understanding, feelings.
Operations or technical assessment; hardware
software,training, manuals and rules
Stakeholder impact.
Concerns, jobs, skills , efficiency, satisfaction, work load
Task, Changes, complexity , flexibility, skill levels
Location; ways of communication
Functions ; where do the people fit in.
techniques
org modeling, process modeling, problem tracking

techniques
Force field analysis
Define Transition requirement

Purpose: Define requirements for transition from current state Purpose: transition requirement, implementation plan ,
to desired state communication

Definition: while implementing there can be parallel run, Data migration ad hoc scripts, etl, ongoing work completion ,
conduct training for users and so forth, Implementation team resource absorption and release
has to develop the capabilities to support transition
technique .
Can be done only after solution is designed , life time is limited Business rule analysis , data flow diagram, process model,
, techniques are same , input nature, and lifespan are org model, data modeling
different.
All stake holders
If it is a new solution it is not needed.

Input: organization readiness

assessment,requirements,solution deployed and designed

elements
Data migration, Ongoing work , org change

technique; Business Rules Analysis,Data Flow

Diagrams,,Process Modeling,Organization Modeling and data
modeling

All stake holders

Validate Solution
Purpose: Validate that the solution meets business needs
and appropriate actions for identified defects.
Input: Requirements, Solution (constructed-may or man not
have implemented).
Investigate defective solution output.
Establish what is defect, like reworked , rejected requirement
etc.
RCA has to be done , For software it will be done by
implementation SME
Asses Defects and issues
Purpose: Test result review meeting, Ongoing prodution
support work queue meeting, Post install PPV, PPR ,
exceptions and ongoing validation
Input : Quality Center, Maximo and production.
Defect Identification, Reporting and prioritizing , PPR and
Mitigation
Technique
1. Problem tracking, 2, Threshold values, 3. Root cause
analysis
Stake holder
TCOE, L3, Product owner, PM, Legal team, end users

- Identification, Impacst assement, priority , frequency,

resilience ,

If Root cause can not be found and stake holder can not
accept the defect then BA has to find mitigation plan

Technique
Acceptance and evaluation criteria,problem tracking
root cause analysis

Stake Holder: Tester(plan and test), User (acceptance

testing), Domain SME(EC), Implementation SME(Defect
Resolution and recovery),PM,Regulator (verify
acceptance testing) and Sponsor (accept the solution)
Solution performance assesment
Purpose : PPV-A and additional value add. Correlation

Solutions:- Altered, Added, Adopted - what to be understood Purpose:

.3w Verification checklist after major install. user feed back,
Scenario sampling,Reports verfication and validation.
Business Need, Defects,metrics, solution
Elements:
Elements : Workaround documentation
value - under/over performance.- new business need. FCI,Reduce FCI,Fix and defect.
Over performance . - future estimation input, resource
redistirbution. Refine metrics : FCI process improvement

Refine metrics: Solution produce 100% desired output but

business goal is not met. Metrics can be automated Application rationalizing and decommissioning

Solution replacement: Vendor support expiry, Hardware support, Business need,

ongoing cost vs initial investment. Sunk cost - reusing existing infrastructure.
Opportunity cost. - ROI
Necessity :obsolescence Decision analysis, question and survey, Focus group
Sunk cost: avoid reluctance if we have high ROI (JAD), Observation ( via a screen print flow)

Technique . Stake holder: Sponsor, L3,Domain SME,Legal team, Users

Decision Analysis , Focus group, Observation, Survey.

Stake holder: (customer,Domain SME, Supplier ), End

user, Sponsor , Operations, regulator.