Uer stories - how to utilize it effectivly in order to follow a user center design path to delivering a successful product.

1. User Story
Driven
Product

2. Ran liron
Head of UX at Varonis systems
UX mentor at Google Launchpad
LironRan@gmail.com
“Ran Liron” on SlideShare and LinkedIn

3. Disclaimers!
I didn’t invent anything I’m about to tell you.
I did experience most of it.
Everywhere is different.

4. As a user experience designer
I want to provide value to our users

5. As a user experience designer,
I want to facilitate conversation and
ensure that we follow a user centered
design process,
So that we will provide value to our users

6. As a user experience designer,
I want to facilitate conversation and
ensure that we follow a user centered
design process,
So that we will provide value to our users

7. What
is a “user story”?

8. What is a “user story”?
An Agile method to describe the needs
of a specific user, from the user perspective,
in order to achieve clearly defined values.

9. [Persona]
[Method]
[Value]
As a
I want
So that

10. busy, yet concerned mother of young kids
a clear and easy way to review common cold treatments for children
As a
I want
I'll know how to protect my kids from the common coldSo that

11. Professional athlete
to get in-depth review of vitamin C as a common cold prevention
As a
I want
I'll know if I should use vitamin C while preparing for a marathonSo that

12. Why
do we need user stories?

13. Why do we need “user stories”?
A product shouldn't be about providing
“capabilities” or “features”.
It should be about providing value to the user

14. Why do we need “user stories”?
• Map the users’ needs
• Facilitate conversation
• Work toward shared understanding
• Focus on providing value to specific users
• Help estimate efforts and prioritize tasks
• Record the fine details of the design

15. Why do we need “user stories”?
Did I mention
conversation?

16. Who
is responsible for generating user stories?

17. Who is responsible for the user stories?
user stories should be provided
by the product owner.
PM UX

18. How
to generate effective user stories?

19. How to generate effective user stories?
1. INVEST
2. DoD
3. Story development order

20. The INVEST method
Independent
Stand alone by itself
* INVEST concept - by Bill Wake

21. The INVEST method
Negotiable
It is not an explicit contract for
features
* INVEST concept - by Bill Wake

22. The INVEST method
Valuable
Provide value to the end user
* INVEST concept - by Bill Wake

23. The INVEST method
Estimable
The required effort can be
evaluated
* INVEST concept - by Bill Wake

24. The INVEST method
Small
Can be developed in a short
period
* INVEST concept - by Bill Wake

25. The INVEST method
Testable
Can be tested and verified
* INVEST concept - by Bill Wake

26. The INVEST method
• Independent - Stand alone by itself
• Negotiable - It is not an explicit contract for features
• Valuable - Provide value to the end user
• Estimable - The required effort can be evaluated
• Small – Can be developed in a short period
• Testable — Can be tested and verified
* INVEST concept - by Bill Wake

27. DoD
Definition of “Done” (a.k.a. “Success criteria”)
What is required from R&D, in order for the story
to be defined as “Done”?

28. User story example: compose new mail
As an experienced email user,
I would like to launch a new email editor,
so that I can write and send a new email
Success criteria (DoD):
• Visible link to “create new email”
• Mandatory fields validation and error handling
• Execution according to the visual design guidelines

29. Story development order
“As a ___ , I want ___ , so that ___”

30. Story development order
“As a ___ , I want ___ , so that ___”
Persona1
As a __

31. Story development order
“As a ___ , I want ___ , so that ___”
The value2
so that ___

32. Story development order
“As a ___ , I want ___ , so that ___”
The method3
I want ___

33. Story development order
“As a ___ , I want ___ , so that ___”
1 23

34. How to generate effective user stories?
1. The INVEST method
2. Definition of Done (DoD)
3. Story development order

35. User Story
vs.
Other Tools

36. User story vs. use case
What is it all about?
Use case - Focus on the flow of the solution
• User: all
• Precondition: user has an email (e.g. Gmail) account
• Success/basic flow:
• User logins to her mail account
• User selects to write a new email
• A writing area opens
• User types the mail address of the receiver (one or more, at least one is mandatory)
• User types a subject
• User writes a message
• User selects to send the message
• Message is sent to receiver * Use case example by Nurit Peres

37. User story vs. use case
What is it all about?
User story - Focus on the generated value
As an experienced email user,
I would like to launch a new email editor,
so that I can write and send a new email
Success criteria:
• Visible link to “create new email”
• Mandatory fields validation and error handling
• Execution according to the visual design guidelines

38. User story vs. use case
What is it all about?
Use cases - Focus on the flow of the solution
User stories - Focus on the generated value

39. Can user stories replace wireframes?
Nope

40. Can user stories replace style guides?
Hell no

41. Can user stories replace use cases?
Yes
In many cases

42. Conclusion

43. Takeaways
We do
Facilitate conversation
Address the needs of
a specific persona
Focus on delivering value by
addressing end-to-end solution
We don’t
Submit “requirements”
Target “a user”
Focus on “Features”
User stories can help ensure that -

44. To learn more:
User Story Mapping
A book by Jeff Patton
UX @Agile – a presentation by me
Available on SlideShare

45. Now go ahead
and craft
your stories!

46. I love feedback!
LironRan@gmail.com,
“Ran Liron” on LinkedIn and SlideShare