The document provides an overview of user stories, which are brief descriptions of a feature from the user's perspective. It discusses the purpose of writing user stories, who can write them, and offers a framework (I.N.V.E.S.T.) for crafting effective stories. It also includes examples and practices for writing user stories and acceptance criteria.

1. User Stories
Fundamentals
Moises Armani Ramirez

2. What is a User Story?
Short, simple descriptions of a
feature told from the perspective
of the person who desires the new
capability, usually a user or
customerof the system (Mike Cohn)
Functional increment (Agile Alliance)

3. Why writing User
Stories?
• To improve the product
incrementally
• To speed up feedback
To invite the team for a conversation

4. Who can write User
Stories?
Anyone.

5. How to write User
Stories?
As a ______ (who is it for?)
I want to ______ (What does the
user want to do?)
so that ______
(Motivation/problem being
solved)

6. I.N.V.E.S.T.
I
Independent
N
Negotiable
V
Valuable
E
Estimable
S
Small
T
Testable

7. Practice 1: Writing User Stories
• The problem: The client has a website that
offers Agile courses and would like to keep users
informed about the latest news on Agile.
• Task: Write one or more user stories explaining
the problem of the client.
As a ______ (who is it for?)
I want to ______ (What does the user want to do?)
so that ______ (Motivation/problem being solved)

8. Practice 1: Writing User Stories-
Examples
As a site visitor, I can read current news on the home page so that I
stay current on agile news.
As a site visitor, I can access old news that is no longer on the home
page, so that I can access things I remember from the past or that
others mention to me.
As a site member, I can subscribe to an RSS feed of news (and
events?) so that I remain sufficiently and easily informed.
As a site editor, I can assign priority numbers to news items, so
that I can indicate which articles I want featured most prominently
on the site. Note: Items are displayed on the front page based on
priority.
https://www.mountaingoatsoftware.com/uploads/documents/example-user-stories.pdf

9. Acceptance criteria
Given ______ (some context)
When ______ (some action is
carried out)
Then ______ (a set of observable
consequencesshould obtain)

10. Practice 2: Writing Acceptance
Criteria
• The problem: The team now needs to define
acceptance criteria(s) for the user story (as part of
the Definition Of Ready).
• Task: Write one or more acceptance criteria.
Given ______ (some context)
When ______ (some action is carried out)
Then ______ (a set of observable
consequences should obtain)

11. Where to start?
The Three C's
by Ron Jeffries
Card
Conversation
Confirmation

12. Where to start?
Story Mapping
by Jeff Patton
Goals
Activities
Tasks
Stories

13. Horizontal and Vertical
User Stories

14. Story Splitting
Tasks
User Stories
Epic
Support to
multiple user
profiles
As a Portfolio
Manager...
Create new... Update the...
As a Trader...
Remove the...

15. https://dilbert.com/strip/2003-01-10

16. https://agilemanifesto.org/
Working software
over
comprehensive documentation

17. References
• https://www.mountaingoatsoftware.com/a
gile/user-stories
• https://www.agilealliance.org/agile101/agil
e-glossary/
• https://www.deltamatrix.com/horizontal-
and-vertical-user-stories-slicing-the-cake/
• https://www.thoughtworks.com/insights/bl
og/story-mapping-visual-way-building-
product-backlog

18. Thank you!
@armaniramirez
armaniramirez@gmail.com