user story driven product development process
TRANSCRIPT
User StoryDrivenProduct
Ran lironHead of UX at Varonis systemsUX mentor at Google [email protected]
“Ran Liron” on SlideShare and LinkedIn
Disclaimers!
I didn’t invent anything I’m about to tell you.
I did experience most of it.
Everywhere is different.
As a user experience designerI want to provide value to our users
As a user experience designer,I want to facilitate conversation andensure that we follow a user centereddesign process,So that we will provide value to our users
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
Whatis a “user story”?
What is a “user story”?An Agile method to describe the needsof a specific user, from the user perspective,in order to achieve clearly defined values.
[Persona][Method]
[Value]
As aI want
So that
busy, yet concerned mother of young kidsa clear and easy way to review common cold treatments for children
As aI want
I'll know how to protect my kids from the common coldSo that
Professional athlete to get in-depth review of vitamin C as a common cold prevention
As aI want
I'll know if I should use vitamin C while preparing for a marathon So that
Whydo we need user stories?
?
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
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
Why do we need “user stories”?
Did I mentionconversation?
Whois responsible for generating user
stories?
Who is responsible for the user stories? user stories should be providedby the product owner.
PM UX
Howto generate effective user
stories?
How to generate effective user stories?1. INVEST2. DoD 3. Story development order
The INVEST method
Independent Stand alone by itself
* INVEST concept - by Bill Wake
The INVEST method
Negotiable It is not an explicit contract for features
* INVEST concept - by Bill Wake
The INVEST method
Valuable Provide value to the end user
* INVEST concept - by Bill Wake
The INVEST method
Estimable The required effort can be evaluated
* INVEST concept - by Bill Wake
The INVEST method
SmallCan be developed in a short period
* INVEST concept - by Bill Wake
The INVEST method
TestableCan be tested and verified
* INVEST concept - by Bill Wake
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
DoDDefinition of “Done” (a.k.a. “Success criteria”)
What is required from R&D, in order for the story to be defined as “Done”?
User story example: compose new mailAs 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
Story development order
“As a ___ , I want ___ , so that ___”
Story development order
“As a ___ , I want ___ , so that ___”
Persona1As a__
Story development order
“As a ___ , I want ___ , so that ___”
The value2so that___
Story development order
“As a ___ , I want ___ , so that ___”
The method3
I want___
Story development order
“As a ___ , I want ___ , so that ”___
1 23
How to generate effective user stories?1. The INVEST method2. Definition of Done (DoD)3. Story development order
User Storyvs.
Other Tools
User story vs. use caseWhat 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
User story vs. use caseWhat 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
User story vs. use caseWhat is it all about?Use cases - Focus on the flow of the solutionUser stories - Focus on the generated value
Can user stories replace wireframes?
Nope
Can user stories replace style guides?
Hell no
Can user stories replace use cases?
YesIn many cases
Conclusion
Takeaways
We doFacilitate conversationAddress the needs ofa specific personaFocus on delivering value by addressing end-to-end solution
We don’tSubmit “requirements” Target “a user”
Focus on “Features”
User stories can help ensure that -
To learn more:
User Story MappingA book by Jeff Patton
UX @Agile – a presentation by me Available on SlideShare
Now go aheadand craftyour stories!
