1. AGILE TOUR YEREVAN
04, October, 2014
User Story, Sprint Planning
Aram Kalantaryan
Product Owner, VMware
Confidential 10/6/2014 1
2. Agenda
8 tips for writing great User Stories
Sprint Planning
Q&A
2
3. User Story
User stories are short, simple description of a feature told
from the perspective of the person who desires the new
capability, usually a user or customer of the system
3
4. 1. Start with the Users
As a <type of user>, I want <some goal> so that <some
reason>.
4
5. 2. Use Personas to Discover the Right Stories
What functionality does the product have to provide to
meet the goal of the personas?
5
6. 3. Write Stories Collaboratively
A user story is not a specification, but a communication
and collaboration tool.
The product owner and the team should discuss the
stories, or even better, write them together
6
7. 4. Keep your Stories Simple and Concise
Write your stories so that they are easy to understand,
avoid confusing and ambiguous terms
Experiment with different ways to write your stories to
understand what works best for you and your team
7
8. 5. Start with Epics
Starting with epics allows you to sketch the product
functionality without committing to the details
This is particularly helpful for new products and new
features
8
9. 6. Decompose your Stories until they are Ready
Break your epics into smaller, detailed stories until they
are ready: clear, feasible, and testable
the story should not too big, and there has to be an
effective way to determine if the story is done
9
10. 7. Add Acceptance Criteria
The criteria enrich the story and make it more precise
and testable
As a rule of thumb, use three to five criteria for detailed
stories
10
11. 8. Keep your Stories Visible and Accessible
Make Stories visible by putting them up on the wall or by
using collaboration tools
11
12. Agile Planning
There are two defined artifacts that result from a sprint
planning meeting:
o A sprint backlog
o A sprint goal
12