Agile Adria User Stories workshop

1,341 views

Published on

Most agile software development team grapple with user stories as a technique for understanding what needs to be developed iteratively.
Come to this workshop to hear some techniques for uncovering useful user stories and how to slice them in a way to deliver value in small increments.
We’ll give you a cheatsheet for story splitting to take away with you

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,341
On SlideShare
0
From Embeds
0
Number of Embeds
15
Actions
Shares
0
Downloads
26
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Agile Adria User Stories workshop

  1. 1. THE ART OF SLICING & DICING USER STORIES @RachelCDavies
  2. 2. A WORKSHOP IS LEARNING THROUGH YOU DOING SOME WORK ..
  3. 3. RACHEL DAVIES Agile Coach @Unruly Media, London Started as software developer in 1988… …Consulting, designing, engineering, leading, coaching, training…. Co-author of first book on “Agile Coaching” in 2009.
  4. 4. ABOUT UNRULY MEDIA Unrulymedia.com
  5. 5. ABOUT YOU
  6. 6. WORKSHOP AIMS !  What is a “user story” !  What is a “persona” !  Why is a persona valuable !  Try story splitting !  Not covering estimation or prioritization or implementing stories
  7. 7. What is a User Story? A user story is a short description of a system feature that is: “…understandable to customers and developers, testable, valuable to the customer and small enough so that the programmers can build half a dozen in an iteration.” Kent Beck, 2001
  8. 8. 3C’S "  Conversation between customer & developers "  Card notes of story & tests on index cards "  Confirmation tests that show story is complete •  Ron Jeffries, Xprogramming.com
  9. 9. Find out more .. Talk to users & stakeholders! In person or hangout/chat START WITH A CONVERSATION
  10. 10. QUESTIONS HELP FIND CONTEXT Ask questions to uncover the user stories.. •  Who will use it? •  What problem are they trying to solve? •  What’s their goal? •  Why is this valuable to them? Understand this before diving into solution details
  11. 11. USER STORY FORMAT
  12. 12. EXAMPLE USER STORY
  13. 13. EPICS?
  14. 14. Old saying “A bird in the hand, worth two in the bush” Look for ways to deliver small amount of value as early as possible!
  15. 15. BENEFITS OF SPLITTING Small stories are: •  Better understood •  Get delivered more quickly •  .. ?
  16. 16. Iteration, RELEASE WHEN READY
  17. 17. Consumable Vertical Slices
  18. 18. DTSTTCPW Do the simplest thing that can possibly work!
  19. 19. Epic User Stories T Acceptance Tests T T T T Sometimes creating acceptance tests uncovers new stories SMALLEST STORY IS A TEST
  20. 20. HOW TO SPLIT •  What does a user see? •  What information is essential? •  What can a user do? •  What behaviours does the system have? •  What safety needs to be considered? •  Failure cases •  What platforms is this supported on?
  21. 21. Business TECHNICAL
  22. 22. Needs Options Business Development Value SHARED RESPONSIBILITY
  23. 23. NURTURING EMPATHY Through workshops, interviews and gathering research Mining personas
  24. 24. Comments/Notes
  25. 25. PUT YOURSELF IN THEIR SHOES
  26. 26. CREATE AN EMPATHY MAP FOR ONE PERSONA
  27. 27. Nurture empathy with Visible personas
  28. 28. DIALS There are dials that we can move up and down to iteratively improve the story through iterative delivery.
  29. 29. SAFETY How much do we need to protect the user?
  30. 30. How helpful does system need to be?
  31. 31. SLICK? How pretty does the system need to be?
  32. 32. REALITY How much of the system needs to be there?
  33. 33. PRACTICAL WORK
  34. 34. GROUPWORK !  Get into groups of 2-4 people !  Grab some index cards !  Select one personas !  Use an empathy map to get into their shoes !  Write user stories relevant to this persona !  What dials can you apply to the stories you write? "  Safety? Helpfulness? Slickness? ..? Goal: as many stories as possible!
  35. 35. HEADLINE “EPIC” STORIES !  Happy couple: Invite guests to contribute photos !  Guests: Upload photos !  Happy couple: Select photo set to share !  Guests: Add information about photos !  Guests: View photos
  36. 36. CREATE AN EMPATHY MAP FOR ONE PERSONA
  37. 37. THANK YOU! www.slideshare.net/RachelDavies
  38. 38. LINKS •  Story Maps Jeff Patton  http://www.agileproductdesign.com/blog/the_new_backlog.html •  Bill Wake http://xp123.com/articles/twenty-ways-to-split-stories/  •  Rachel Davies  http://agilecoach.typepad.com/agile-coaching/2010/09/ideas-for-slicing-user- stories.html •  Richard Lawrence  http://www.richardlawrence.info/2009/10/28/patterns-for-splitting-user-stories/ •  Lasse Koskela http://radio.javaranch.com/lasse/2008/06/13/1213375107328.html •  James Grenning http://www.renaissancesoftware.net/blog/archives/48 •  George Dinwiddie http://idiacomputing.com/pub/UserStories.pdf •  Joe Rainsberger  http://www.jbrains.ca/permalink/how-youll-probably-learn-to-split-features •  Thomas http://agile-management.com/wordpress/splitting-user-stories/ •  Mark Levison  http://agilepainrelief.com/notesfromatooluser/2010/09/story-slicing-how-small- is-enough.html and  http://agilepainrelief.com/notesfromatooluser/2010/12/more-notes-on-story- splitting.html

×