Your SlideShare is downloading. ×
Questions Not Stories (Agile Cambridge 2012)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Questions Not Stories (Agile Cambridge 2012)

1,513
views

Published on

Workshop on user stories vs hypothesis & experiments from the Lean Startup community, presented on September 27 at Agile Cambridge 2012.

Workshop on user stories vs hypothesis & experiments from the Lean Startup community, presented on September 27 at Agile Cambridge 2012.

Published in: Technology

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,513
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
14
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Questions not Stories Agile Cambridge 2012 Adrian Howard (@adrianh) quietstars.com
  • 2. Please askquestions
  • 3. Disclaimer 1: Eh?
  • 4. Disclaimer 2:I could be confused and stupid
  • 5. Who am I?
  • 6. Swear Jar
  • 7. (obligatory cute animal slide)
  • 8. Who are you?
  • 9. Disclaimer 3:Be careful if you’re new to agile
  • 10. Chatham House Rule applies please
  • 11. "When a meeting, or part thereof, isheld under the Chatham House Rule, participants are free to use theinformation received, but neither the identity nor the affiliation of the speaker(s), nor that of any other participant, may be revealed"
  • 12. Exploring user stories
  • 13. Exercise• 5m• Everybody write a user story• Real (if you can) or made up• “As a <user>, I want <goal> so that <reason>” template if you want to, but not compulsory
  • 14. Exercise• 5m• Each person explain their user story to the group• Card. Conversation. Confirmation.
  • 15. Exercise• 5m• Each table write on post-it notes• User story likes/dislikes, good/bad points, purposes, etc.
  • 16. Relax
  • 17. Stories arestatements
  • 18. Stories describe the product
  • 19. Product owner says“doing X will return business value”
  • 20. Breakdown stories by splitting & thinning
  • 21. Stories =known knowns.
  • 22. What aboutknown unknowns?
  • 23. The Lean Startup“A true experimentfollows the scientificmethod. It begins witha clear hypothesis thatmakes predictionsabout what is supposedto happen. It then teststhose predictionsempirically”
  • 24. The Lean Startup• Come up with hypothesis• Design experiment• Run experiment• Validate/Invalidate hypothesis• Repeat
  • 25. The Lean Startup
  • 26. Moving from Stories to Hypotheses
  • 27. As a potential user, I want register usingtwitter so that I don’t have to fill out a registration form.
  • 28. Step 1
  • 29. As a potential user, I want register usingtwitter so that I don’t have to fill a registration form ?
  • 30. As a potential user, I want register usingtwitter so that I don’t have to fill a registration form ?
  • 31. Step 2: Ask why?• Increase # registrations?• More social media penetration for marketing?• Allow notification features?
  • 32. Step 3: What’s our hypothesis?
  • 33. Allowing users toregister with twitterwill drop abandoned registrations by 5%
  • 34. Exercise• 5m• Pair up• Pick a story card and apply: 1. Question mark 2. Why (or “whys”) ? 3. Generate hypothesis
  • 35. BuildingExperiments
  • 36. Experimentsproduce learning not product
  • 37. Experiments canget thrown away
  • 38. Focus on speed of feedback
  • 39. Allowing users toregister with twitterwill drop abandoned registrations by 5%
  • 40. Experiment• Built fake “register with twitter” link which led to nice error message• Released to segment of customers on live site• Measured how many new users tried it• <1% - hypothesis invalid
  • 41. Not just A/B testing
  • 42. Exercise• 5m• Pair up• Pick a hypothesis• Come up with as many ways to validate the hypothesis as possible
  • 43. Exercise• 5m• Each table write on post-it notes• Hypothesis/experiment likes/dislikes, good/bad points, purposes, etc.
  • 44. The Good, the Bad & the Ugly
  • 45. Alignment on value
  • 46. Helps build anexperiment culture
  • 47. It’s hypothesesbefore, during andafter development
  • 48. Metric-FirstDevelopment
  • 49. Encouragesvalue-oriented infrastructure
  • 50. Hypotheses talkabout business value directly
  • 51. Success changes
  • 52. Splitting/thinning changes
  • 53. Where’s the user?
  • 54. Where’s the delight?
  • 55. Horde of zombie experiments
  • 56. Where are therunning, tested features?
  • 57. What happens when I can’tvalidate cheaply?
  • 58. What about non-startup contexts?
  • 59. Some folk find reality hurts
  • 60. Further Reading• Lean Startup by Eric Ries• Running Lean by Ash Maurya• The Four Steps to the Epiphany by Steve Blank• The Entrepreneur’s Guide to Customer Development by Brant Cooper & Patrick Vlaskovits• The Startup Owners Manual by Steve Blank (not read)
  • 61. I <heart> feedback
  • 62. Questions?
  • 63. Adrian Howard adrianh@quietstars.com twitter.com/adrianhlanyrd.com/profile/adrianh quietstars.com

×