ES

R I
TO
S
ER
US
USER STORY
• A user story is one or more sentences in the everyday or business language of the
end user that captures what the user wants to achieve. User stories are used
with Agile software development methodologies for the basis of what features
that can be implemented.
• Each user story is limited, so it fits on a small paper note card to ensure that it
does not grow too large.
USER STORY TEMPLATE
• As a <role>, I want <goal/desire> so that <benefit>.

• Example:
• As a user I want to create organizer records, so that I can store my plans
scheduled somewhere.
USER STORY
• User stories are a quick way of handling customer requirements without having
to elaborate vast formalized requirement documents and without performing
overloaded administrative tasks related to maintaining them.
• Story must describe the What not How.
• The intention of the user story is to be able to respond faster and with less
overhead to rapidly changing real-world requirements.
USER STORY BOARD
•
USER STORY SHOULD BE
• Independent - stories should not be dependent on one another. Dependencies between
stories lead to prioritization and planning problems.
• Negotiable - They are not written contracts or requirements that the software must
implement. Story cards are short descriptions of functionality, the details of which are to be
negotiated in a conversation between the customer and the development team.
• Valuable - each story must bring some business value.
• Estimable – the scope of as story must be observable.
• Small – to estimate, to track progress
• Testable - must be a criteria of “done”
USER STORY AUTHOR
• The user stories should be written by customer product manager for a software
project and are their main instrument to influence the development of the
software.
• Business analyst can be a surrogate of a customer.
• User stories could also be written by developers to express non-functional
requirements.
ACCEPTANCE OF A STORY
• Before a user story is to be implemented, an appropriate acceptance procedure
must be written by the customer to ensure by testing or otherwise determine
whether the goals of the user story have been fulfilled.
• Example:
• Acceptance criteria: a record with all fields specified is created and saved so
some persistent state
ORGANIZER CRUD USER STORIES: C
US 1.
As a user I want to create organizer records, so that I can store my plans
scheduled somewhere.
_____________
Acceptance criteria: a record with all fields specified is created and saved so
some persistent state
Size: medium.
Priority: high
Sprint: 1
ORGANIZER CRUD USER STORIES: R
US 2.
As a user I want to view the records that have a particular date, time specified on
the calendar, so that I can schedule my plans.
_____________

Acceptance criteria: System displays the records that have date specified on the
calendar.
Size: medium.
Priority: high
Sprint: 1
ORGANIZER CRUD USER STORIES: R
US 3.
As a user I want to view the records with no date specified on the tasks section,
so that I can view my tasks that have to schedule.
_____________

Acceptance criteria: System displays the records that have no date specified on
the tasks pane.
Size: medium.
Priority: medium
Sprint: 1
ORGANIZER CRUD USER STORIES: U
US 4.
As a user I want to edit the records stored persistently in the app, so that I can
change my plans.
_________

Acceptance criteria:
1. System allows to edit an existing records.
2. The entered/existing data is saved successfully to the persistent storage when
the user saves the record.
Size: big.
Priority: low
Sprint: 2
ORGANIZER CRUD USER STORIES: D
US 5.
As a user I want to delete records, so that I can clean up the mess.
______

Acceptance criteria: The record is deleted from the persistent storage and is no
longer available.
Size: simple.
Sprint: 2
USE STORIES ENVIRONMENT
• Agile > Scum
• Agile > XP
• Agile > Kanban
SCRUM: USER STORY LIFECYCLE
SCRUM: BACKLOGS
• Product backlog
• Sprint Backlog
• User Story XXX
• Task 1
• Task 2
• Task 3
• Task 4
USER STORIES PRACTICE
• Create a user story for your project
• Identify user role
• Identify value
• Identify acceptance criteria
• Estimate the story
• Prioritize the story
QUESTIONS
• Come’n I know ya gotta tricky question for me….