The document explains the concept of user stories in software development, outlining their structure as a representation of features from the end user's perspective. It compares user stories with use cases and provides an example related to searching for flight tickets, detailing required fields, successful scenarios, and error handling. Additionally, it highlights that user stories can be utilized in any methodology, not limited to agile practices.

1. 1
#FromGroundZero
Business Analyst Tutorials
USER STORIES BASICS

2. HELLO!
I am Abhishek Srivastava
Author, Blogger and Experienced IT
professional
2

3. 3

4. What is a User Story
User Story
Is a format/structure to represent a feature of a software system from the end user
perspective

5. Format of user story
As a <User role>
I want <to do something>
So that I can <achieve some goal>
As a <User>
I want <to search for flight tickets as per my schedule>
So that I can <so that I can attend a business conference>

6. User story Vs Use Cases
As a <User>
I want <to search for flight tickets as
per my schedule>
So that I can <so that I can attend a
business conference>

7. User Story 3C by Ron Jeffries
Card
A sticky note (Post-It) showing the basic user story as we have seen previously
Conversation
Summary of discussions pertaining amongst stakeholders about the feature/functionality
to enhance it more details. This will include details of steps, rules, prototypes & more…
Confirmation
How will this user story (piece of functionality be accepted) – the acceptance test cases

8. User Story Example
As a <User>
I want <to search for flight tickets as per my schedule>
So that I can <so that I can attend a business conference>

9. From
Date
Of Travel
Num of
passengers
Search Cancel
The FROM field will have autofill/Selection
capability.
The option cities must be valid airports
Only one of these options can be selected
You cannot put a past date.
You cannot book tickets for a date more than
one year away.
As a visitor, I would search for flights so that I can plan my trip
To
Trip Type One Way Round Trip
The TO field will have autofill/Selection capability.
Date of travel cannot be entered, it has to be
selected from a calendar
Number of passengers will be a drop down list
with only valid options
All the fields are mandatory
Return date
Submit button will call an API from Galileo

10. Successful Scenarios:
1. When the visitor clicks on the search button, the search results are displayed on the next page
2. When the visitor clicks on the cancel button, the visitor stays on the same page and all the fields will become blank
Alternate Scenarios:
1. If any of the mandatory/required data is missing, the click on search button should throw a relevant error message (If
date of travel is missing – the message should be “The date of travel must be specified”)
2. In case of GDS systems being down, the system should display a message “We have encountered some problems,
please try after some time”
As a visitor, I would search for flights so that I can plan my trip
Confirmation

11. Points to note
 User stories can be used in any methodology including Agile
(It’s not meant for Agile only)
 Any modelling technique must be used with the objective of
helping the stakeholders achieve the business objective

12. 12
THANKS!
Any questions?
You can find me at
 @techcanvass
 info@techcanvass.com