O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Slicing user stories

478 visualizações

Publicada em

How to slice user stories, using concepts like low/high fidelity solutions, iterative vs incremental delivery, and hunting for small bits of value rather than breaking down work in technical chunks.

Publicada em: Tecnologia
  • Seja o primeiro a comentar

Slicing user stories

  1. 1. David Michel 25 October 2016 Slicing User Stories @DavMichel76
  2. 2. Requirements in Scrum? Product Backlog Item User story
  3. 3. Granularity ?
  4. 4. Backlog Refinement Process
  5. 5. How to break down large user stories
  6. 6. Let’s NOT break things down in “waterfall” phases… Implement Test Deploy + +
  7. 7. http://agileforall.com/resources/how-to-split-a-user-story
  8. 8. Let’s explore some of the tools & techniques
  9. 9. Slicing by workflow As customer I want to review and confirm my order, so I can correct mistakes before I pay As customer I want to pay for my order with paypal, so I don’t have to look for my credit card As customer I want to receive a confirmation e-mail with my order, so I have proof of my purchase
  10. 10. Slicing by operation As shop owner I want to add new products, so customers can purchase them As shop owner I want to update existing products, so I can adjust for changes in pricing or product information As shop owner I want to delete products, so I can remove products that I no longer stock
  11. 11. As site owner I want to be able to request a new password when my login fails, so that I can try to log in again Slicing by unhappy As site owner I want to block users with 3 failed log in attempts in a row, so I can protect the site against hackers As user I want to log in with my account, so that I can access secure pages
  12. 12. Slicing by “0>1>many” As a chef, I want to view a customer’s order with no items so I can proceed with the cooking As a chef, I want to view a customer’s order with one item so I can proceed with the cooking As a chef, I want to view a customer’s order with multiple items so I can proceed with the cooking
  13. 13. There are many, many more techniques… • Splitting User Stories Presentation http://www.slideshare.net/arsenalist/splitting-userstories • Splitting User Stories Cheat sheet https://twitter.com/chrisverwijs/status/335109871802384385 • Breaking Down Larger Stories http://agileinaflash.blogspot.co.uk/2009/02/breaking-down-larger-stories.html • User Story Hamburger technique https://gojko.net/2012/01/23/splitting-user-stories-the-hamburger-method/ • Features to User Stories http://idiacomputing.com/pub/UserStories.pdf • Patterns for spitting user stories http://agileforall.com/patterns-for-splitting-user-stories/ • Twenty Ways to Split Stories http://xp123.com/articles/twenty-ways-to-split-stories/
  14. 14. This was easy, right?
  15. 15. Where the magic happens Your comfort zone
  16. 16. Thin vertical slices
  17. 17. Not horizontally
  18. 18. Database Web server GUI + +
  19. 19. Thin vertical slices
  20. 20. Thin vertical slices Thinning Not splitting
  21. 21. Simple to complex Slicing by fidelity http://availagility.co.uk/2009/12/22/fidelity-the-lost-dimension-of-the-iron-triangle/
  22. 22. Iterative vs Incremental
  23. 23. As a gardener, I want to use a So that I can plant this or or or
  24. 24. As a I want to So that . Expected outcome Action Persona How do we know this is the best action to take? Maybe there’s a better way. Too many assumptions http://alanklement.blogspot.co.uk/2013/09/replacing-user-story-with-job-story.html
  25. 25. • Impossible to define any kind of acceptance criteria • Rarely expressed in a way that would make them appear valuable from the perspective of the stakeholders Slicing by “learn vs. earn” Spikes https://leanpub.com/50quickideas
  26. 26. Instead of slicing technical deliverables and then looking for useful chunks of value… Slicing by value …Try to start from the opposite direction: slice value and look for useful technical chunks https://leanpub.com/50quickideas
  27. 27. Slicing by “0>1>many” As a chef, I want to view a customer’s order with no items so I can proceed with the cooking As a chef, I want to view a customer’s order with one item so I can proceed with the cooking As a chef, I want to view a customer’s order with multiple items so I can proceed with the cooking This break down seems particularly artificial. The technical breakdown makes sense to developers but doesn’t bring value to the user!
  28. 28. Instead of slicing technical deliverables and then looking for useful chunks of value… Slicing by value …Try to start from the opposite direction: slice value and look for useful technical chunks https://leanpub.com/50quickideas
  29. 29. Backlog Refinement Process Danger of breaking down things we already know a lot about… leaving the large, not yet understood items and at the bottom of the backlog
  30. 30. Danger of breaking down things we already know a lot about… leaving the large, not yet understood items and at the bottom of the backlog Spike to learn Earn by 1st delivering low-fidelity solution Then iterate towards more refined
  31. 31. How do you slice your stories?

×