This is an introduction to User Stories and Product backlog. The User Story is the most appropriate method of elaborating requirements. More than 80% of organizations which have adopted Scrum, use the Product backlog consisting of prioritized list of user stories to manage software delivery.

1. INTRODUCTION :
USER STORIES & PRODUCT BACKLOG
VENKATESH PRASAD
EMAIL: REACHME.VENKY@GMAIL.COM

2. WHAT IS A USER STORY ?
 User Story is a short, simple description of a capability within a feature
 It is told from the perspective of the person who desires this capability
 Usually a customer or a user of the system
 User Story TEMPLATE:
 Why follow this template?
 Think from user perspective
 Provides a structure
 Conversations are focused
As a <type of user>
I want to < accomplish some goal>
So that <particular reason>

3. USER STORY EXAMPLES
 As a computer user, I want to backup my hard
drive, so that I have a copy of the contents to
use in case of hard drive failure
 As an email-site user, I want to store my login
credentials on the site, so that I do not have
enter them each time I visit the website
 As a operations admin, I want to see a
dashboard depicting health of the servers, so
that I know the which servers are operational
and which are not
 As a mobile phone user, I want to edit the
contact list on my phone, so that I can add,
modify or delete contacts

4. THE FAMOUS “INVEST” How big or how small a user story should be ?

5. WHAT IS ACCEPTANCE CRITERIA IN A USER STORY ?
 Acceptance Criteria are “Conditions that a software product must satisfy to be accepted by a user,
customer or other stakeholder.”
 Acceptance Criteria are a set of statements, each with a clear pass/fail result, that specify both functional
and non-functional requirements applicable at the current stage of execution.
 These criteria define the boundaries and parameters of a User Story and determine when a story is
complete
 These must be expressed clearly, in simple language the customer would use
 They must be testable: easily translated into one or more manual/automated test cases and working as
expected.
 Types:
 Functional Criteria: Meet functionality condition
 Non Functional Criteria: User experience design templates
 Performance Criteria: Scale, response time, network latency

6. PRODUCT BACKLOG
 Prioritized list of user stories  Feature elaboration into User Stories and Epics
User Story-1 (Feature1)
User Story-2 (Feature1)
User Story-1 (Feature2)
User Story-2 (Feature2)
User Story-1 (Feature3)
User Story-2 (Feature3)
User Story-3 (Feature3)
User Story-3 (Feature1)
User Story-3 (Feature2)
Feature2
Story-
1
Story-
2
Story-
3
Story-
4
Story-
5
EPIC -6 EPIC -7
Feature 1
Story-
1
Story-
2
Story-
3
Story-
4
Story-
5
EPIC -6 EPIC -7
Feature3
Story-
1
Story-
2
Story-
3
Story-
4
Story-
5
EPIC -6 EPIC -7

7. REFERENCES
 https://www.mountaingoatsoftware.com/agile/user-stories
 http://www.mountaingoatsoftware.com/blog/advantages-of-the-as-a-user-i-want-user-story-template
 https://www.scrumalliance.org/community/articles/2014/june/why-acceptance-criteria%E2%80%9D-is-
needed-before-user-sto
 http://www.seguetech.com/blog/2013/03/25/characteristics-good-agile-acceptance-criteria
 https://help.rallydev.com/writing-great-user-story