Professional Documents
Culture Documents
9 BA MANAGE STAKEHOLDER
PERFORMANCE STAKEHOLDER ENGAGEMENT
ASSESSMENT COLLABORATION
10 Business Need PLAN BA BA APPROACH :-
APPROACH Agile or waterfall or
Hybrid
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)
(2) Satisfy,
Validate
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