DOCUMENTATION

AND CRITERIA
USED FOR
BUSINESS
ANALYSIS

THE BUSINESS ANALYSIS CERTIFICATION PROGRAM

 USER STORIES
DOCUMENTATION
AND CRITERIA
USED FOR
-recognise considerations in employing
user stories BUSINESS
ANALYSIS
 USER STORIES
DOCUMENTATION
AND CRITERIA
-the purpose of a user story is to USED FOR
document
-the needs of a type of stakeholder BUSINESS
-defines the features that the stakeholder
-finds of value for the solution ANALYSIS
 USER STORIES
DOCUMENTATION
AND CRITERIA
-enables prioritisation, estimation, and
planning of solutions USED FOR
-user stories are put into a backlog, and
prioritised BUSINESS
-used to plan the creation and
development and implementation of a
solution
ANALYSIS
 USER STORIES
DOCUMENTATION
-user stories are short and concise
-are a great tool to generate user
AND CRITERIA
acceptance tests
-help to measure the value that's USED FOR
delivered
-used to trace requirements back to the BUSINESS
business objective
-support project management and
reporting
ANALYSIS
-promote additional conversation with
stakeholders
 USER STORIES
DOCUMENTATION
AND CRITERIA
-Describing User Stories. USED FOR
-User stories capture stakeholder needs;
define value features; enable
prioritisation, estimation, and planning of BUSINESS
solutions; and are expressed as concise
statements. ANALYSIS
 USER STORIES
DOCUMENTATION
AND CRITERIA
USED FOR
-Other Uses.
-Other uses of user stories include that
they generate user acceptance tests;
measure value delivered; trace BUSINESS
requirements; carry out additional
analysis; and support project
management and reporting.
ANALYSIS
 USER STORIES
DOCUMENTATION
AND CRITERIA
-A user story is made up of the title, which
are written as goal-based with an active USED FOR
verb phrase.
-They have a statement of value, a BUSINESS
statement of value – that's for the
stakeholder themselves.
-They describe who, what, why.
ANALYSIS
 USER STORIES
DOCUMENTATION
AND CRITERIA
-user stories promote conversations
-include acceptance criteria
-are easy to understand and they are
USED FOR
value focused
-requires the business analyst to
BUSINESS
collaborate with the stakeholders
-enables rapid delivery and feedback on ANALYSIS
the implementation
 USER STORIES
DOCUMENTATION
AND CRITERIA
-intended for short-term use and involve a
conversational approach
USED FOR
-they do require context and visibility
-they involve a lack of documentation BUSINESS
-can be used to support regulatory
requirements ANALYSIS
 USER STORIES
DOCUMENTATION
AND CRITERIA
-Elements of User Stories. USED FOR
-Elements of user stories include the title;
statement of value such as who, what, BUSINESS
and why; a conversation; and
acceptance criteria.
ANALYSIS
 USER STORIES
DOCUMENTATION
-User Stories Considerations.
-User stories considerations include AND CRITERIA
strengths and limitations.
-Strengths include that they are easy to USED FOR
understand; value focused; require
collaboration; and enable rapid delivery
and feedback. BUSINESS
-Limitations include that they are intended
for short-term; involve conversational ANALYSIS
approach that can be a challenge;
require context and visibility; and involve
lack of documentation.
DOCUMENTATION
AND CRITERIA
USED FOR
BUSINESS
ANALYSIS

THE BUSINESS ANALYSIS CERTIFICATION PROGRAM