You are on page 1of 6

BABOK 3.

0 TASKS INPUTS & OUTPUTS


KA SL. INPUT 1 INPUT 2 INPUT 3 INPUT 4 TASK OUTPUT 1 OUTPUT 2 OUTPUT 3
NO.

1 NEEDS :- The ELICITATION ANALYZE BUSINESS Current State


problem/opport RESULTS CURRENT STATE REQUIREMENTS Description:
unity to be (CONFIRMED) for (mistake) :- The existing
solved Vision or Mission problem definition capabilities e.g.
Statement or and root cause of the procedure (the
Business Goals problem:- existing
process)
2 BUSINESS DEFINE FUTURE BUSINESS FUTURE STATE POTENTIAL
REQUIREMENT STATE OBJECTIVES :- DESCRIPTION :- VALUE :- Why
SMART (To reduce Business the problem
claim processing Requirement need to be
STRATEGY ANALYSIS

cycle (specific & Document solved


relevant) time from 3
days to 1 days
(measurable and
achievable) in 1 year
from today (time
bounded)
3 INFLUENCE :- ELICITATION DESIGNS :- BUSINESS ASSESS RISK RISK ANALYSIS
INTERNAL RESULTS Prototype OBJECTIVES; RESULTS :- Risks ,
(Change agents i.e. (CONFIRMED) :- (OPTIONAL) POTENTIAL assumptions, issues,
Branch Managers) employees (PRIORITIZED); VALUE dependencies (RAID
& EXTERNAL computer, REQUIREMENTS log) + Risk Response
(Hacking, strong (PRIORITIZED) Strategy
regulation, resistance to :- BRD
customer online banking (Mandatory)
perfences)
4 STAKEHOLDER CURRENT FUTURE STATE RISK ANALYSIS DEFINE CHANGE CHANGE STRATEGY SOLUTION
ENGAGEMENT STATE DESCRIPTION RESULTS STRATEGY – how SCOPE :-
APPROACH :- DESCRIPTION (release plan) and Boundary of the
Change strategy is where implement solution:- The
defined as per the change :- geographies,
stakeholder Cost/profit type of
perfereces analysis + benefit customers etc
realization plan
(numbers)
SL. INPUT 1 INPUT 2 INPUT 3 INPUT 4 TASK OUTPUT 1 OUTPUT 2 OUTPUT 3
NO.

Needs (Effect) :- STAKEHOLDER PREPARE FOR ELICITATION


ELICITATION AND COLLABORATION

5 the problem that ENGAGEMENT ELICITATION ACTIVITY PLAN


you are facing APPROACH

6 ELICITATION CONDUCT ELICITATION


ACTIVITY PLAN ELICITATION RESULTS
(UNCONFIRMED)

7 ELICITATION CONFIRM ELICITATION


RESULTS ELICITATION RESULTS
(UNCONFIRMED) RESULTS (CONFIRMED)

8 BA STAKEHOLDER COMMUNICATE BA BA INFORMATION


INFORMATION ENGAGEMENT INFORMATION (COMMUNICATED)
APPROACH

9 BA MANAGE STAKEHOLDER
PERFORMANCE STAKEHOLDER ENGAGEMENT
ASSESSMENT COLLABORATION
10 Business Need PLAN BA BA APPROACH :-
APPROACH Agile or waterfall or
Hybrid

11 Change Business Need BA APPROACH PLAN STAKEHOLDER


Strategy :- STAKEHOLDER ENGAGEMENT
Impact of ENGAGEMENT APPROACH :- Kind of
BUSINESS ANALYSIS PLANNING & MONITORING

change on stakeholders +
stakeholders communicating with
those stakeholders
12 BA APPROACH STAKEHOLDER PLAN BA GOVERNANCE
ENGAGEMENT GOVERNANCE APPROACH :- Reqmt
APPROACH :- Who Mgmt Plan :- How
will be part of CCB, you will manage
sprint review change in
session requirements as well
as how to receive
sign off for
requirements +
requirement
attributes e.g.
priority
13 BA APPROACH STAKEHOLDER GOVERNANCE PLAN BA INFORMATION
:- kind of ENGAGEMENT APPROACH :- INFORMATION MANAGEMENT
artifacts APPROACH :- the templates of the MANAGEMENT APPROACH :- BA
kind of artifacts is derived Plan:- Type +
stakeholders you on basis of template of
require to requirement deliverables _
complete artifacts attributes which stakeholders you will
are defined in be creating as well as
governance template for
approach doc e.g. traceability matrix +
priority, criticality, how will you
status etc maintain reqms for
re-use
14 Information PERFORMANCE BA APPROACH :- IDENTIFY BA BA PERFORMANCE
Management OBJECTIVE what internal PERFORMANCE ASSESSMENT :-
Approach :- (EXTERNAL) :- metrics you can IMPROVEMENT metrics to track BA
Where to End user leverage is decided performance +
measure the satisfaction score on basis of performance
performance approach e.g. the assessment report is
level of detail in also prepared in this
acceptance criteria task
(agile); peer
review comments
on functional spec
document
(waterfall)
15 ELICITATION SPECIFY & MODEL REQUIREMENT
RESULTS (ANY REQUIREMENTS (SPECIFIED AND
STATE) MODELLED) i.e. text,
matrices, and
diagrams
16 REQUIREMENT VERIFY REQUIREMENTS • Atomic: self-contained and
(SPECIFIED AND REQUIREMENTS (VERIFIED) capable of being understood
MODELLED) independently of other
requirements or designs.
• Complete: no missing details
e.g. validation messages
• Consistent: no conflicting with
REQUIREMENT ANALYSIS AND DESIGN DEFINATION

other requirements.
• Concise: contains no extraneous
and unnecessary content.
• Feasible: considering
assumptions and constraints
• Unambiguous: no confusion e.g.
login to be no late than 2 seconds
• Testable: acceptance criteria to
be defined
• Prioritized
• Understandable: represented
using common terminology of the
audience.
17 REQUIREMENT VALIDATE REQUIREMENTS
(SPECIFIED AND REQUIREMENTS (VALIDATED)
MODELLED)

18 SOLUTION REQUIREMENTS INFORMATION DEFINE REQUIREMENT


SCOPE (ANY STATE) MANAGEMENT REQUIREMENT ARCHITECTURE e.g.
APPROACH :- ARCHITECTURE process flow diagram
provides you with mapping to
template for requirements
requirement
architecture
19 REQUIREMENT CHANGE REQUIREMENT DEFINE DESIGN DESIGN OPTIONS
S (VALIDATED, STRATEGY ARCHITECTURE OPTIONS
PRIORITIZED)

20 POTENTIAL DESIGN OPTIONS ANALYZE SOLUTION


VALUE POTENTIAL ValuE RECOMMENDATION
AND RECOMMEND
SOLUTION
21 REQUIREMENTS DESIGNS PRIORITIZE REQUIREMENTS DESIGNS • Benefit:
REQUIREMENTS (PRIORITIZED) (PRIORITIZED) • Penalty:
(1) • Cost: Low
• Risk:
•Dependencie
s:
• Time
Sensitivity:
• Stability:
•Regulatory
or Policy
22 REQUIREMENTS DESIGNS TRACE REQUIREMENTS DESIGNS :Derive,
REQUIREMENT (TRACED) (TRACED) Depends,
REQUIREMENTS LIFE CYCLE

(2) Satisfy,
Validate

23 BA governance REQUIREMENTS DESIGNS APPROVE REQUIREMENTS DESIGNS


Plan :- (VERIFIED) (VERIFIED) REQUIREMENTS (APPROVED) (APPROVED)
MANAGEMENT

Additional (3)
recommended
input
24 REQUIREMENT DESIGNS PROPOSED ASSESS REQUIREMENTS DESIGNS • Benefit:
S CHANGE REQUIREMENTS CHANGE CHANGE • Cost:
CHANGES (4) : ASSESSMENT ASSESSMENTS • Schedule:
recommendation •Urgency e.g.
for approve, deny regulations
or modify a • Impact on
proposed changes Stakeholders
25 •Information REQUIREMENTS DESIGNS MAINTAIN REQUIREMENTS DESIGNS
Management REQUIREMENTS (MAINTAINED) (MAINTAINED)
Approach :- for reuse and
Guideliness & update (5)
Tools
26 IMPLEMENTED BUSINESS MEASURE SOLUTION
SOLUTION OBJECTIVES SOLUTION PERFORMANCE
PERFORMANCE :- MEASURES :-
ST/SIT OR UAT or functional and non-
LIVE functional defects
PROVING/PILOT that you have
TESTING detected
27 POTENTIAL SOLUTION ANALYZE SOLUTION
SOLUTION EVALUATION

VALUE can be PERFORMANCE PERFORMANCE PERFORMANCE


derived by MEASURES MEASURES ANALYSIS :- severity
Minimal Viable of defects, identify
Product/Solution which defects to be
resolved
28 IMPLEMENTED SOLUTION ASSESS SOLUTION SOLUTION
SOLUTIONS PERFORMANCE LIMITATIONS LIMITATIONS are
ANALYSIS : with respect to
COMBINATION OF unresolved defects in
RESOLVED + the solution and
UNRESOLVED causes for those
DEFECTS unresolved defects
29 IMPLEMENTED CURRENT STATE SOLUTION ASSESS ENTERPRISE
SOLUTION DESCRIPTION :- PERFORMANCE ENTERPRISE LIMITATIONS after
From an ANALYSIS :- List of LIMITATIONS go-live
enterprise unresolved defects
perspective
30 SOLUTION ENTERPRISE RECOMMEND RECOMMEND
LIMITATIONS LIMITATION ACTIONS TO ACTIONS
INCREASE
SOLUTION VALUE

You might also like