Successfully reported this slideshow.

Divide et Impera - a four bullet strategy to vertically split user stories

0

Share

Loading in …3
×
1 of 34
1 of 34

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Related Audiobooks

Free with a 14 day trial from Scribd

See all

Divide et Impera - a four bullet strategy to vertically split user stories

  1. 1. Divideetimpera • Giuseppe Lucio Sorrentino
  2. 2. Agenda 2 Divideetimpera Section–arationaleforverticaluserstories 10m Activity–chooseyourreferencestory 10m Section–afourbulletsstrategytoverticallysplitstories 20m Activity–let’ssplitaepic 1h
  3. 3. arationaleforverticaluserstories 3
  4. 4. 4 As a (USER) I want to (DO THIS) So that I can (ACHIEVE THAT)
  5. 5. incremental-value delivery approach 5 UserStory1 UserStory2 UserStory3 UserStory4 UserStory5 Release1 Release2 Release3 Release4 Release5 Single UserStory FinalRelease limitedornullfeedbackloop
  6. 6. the iceberg effect 6
  7. 7. granularity 2 7 clarityvagueness abstraction concreteness small scope large scope 1 story
  8. 8. 8 Horizontal vs. Vertical - Value comes to the end - Long feedback loop - Difficult to prioritize - Dev silos - Easiest to imagine • Horizontal - Difficult to imagine - Who is our user? - Release must be easy • Vertical
  9. 9. Activity Chooseyourreferencestory 9
  10. 10. Afourbulletsstrategytoverticallysplit stories 10
  11. 11. 11 1. Split thoughtfully…
  12. 12. 12 workflow steps1 1 2 3 4 5 6 7 8 9 0
  13. 13. 13 business rules variations1 1 2 3 4 5 6 7 8 9 0
  14. 14. 14 major effort1 1 2 3 4 5 6 7 8 9 0
  15. 15. 15 simple/complex1 1 2 3 4 5 6 7 8 9 0
  16. 16. 16 variations in data1 1 2 3 4 5 6 7 8 9 0
  17. 17. 17 data entries methods1 1 2 3 4 5 6 7 8 9 0
  18. 18. 18 defer system qualities 1 2 3 4 5 6 7 8 9 0
  19. 19. 19 operations1 1 2 3 4 5 6 7 8 9 0
  20. 20. 20 use case scenarios1 1 2 3 4 5 6 7 8 9 0
  21. 21. 21 break out a spike1 1 2 3 4 5 6 7 8 9 0
  22. 22. 22 1. Split toughtfully… 2. Check the INVEST guidelines always…
  23. 23. 23 I N V E S T 1 Indipendent
  24. 24. 24 I N V E S T 1 Negotiable
  25. 25. 25 I N V E S T 1 Valuable
  26. 26. 26 I N V E S T 1 Estimable
  27. 27. 27 I N V E S T 1 Small
  28. 28. 28 I N V E S T 1 Testable
  29. 29. 29 1. Check the INVEST guidelines always… 2. Split thoughtfully… 3. Eventually find a vertical-horizontal compromise...
  30. 30. 30 1. Check the INVEST guidelines always… 2. Split thoughtfully… 3. Eventually find a vertical-horizontal compromise... 4. Take the time you need to reach a good level of granularity!
  31. 31. Activity Let’ssplitaepic 31
  32. 32. 32 1. Split thoughtfully… 2. Check the INVEST guidelines always… 3. Eventually find a vertical-horizontal compromise... 4. Take the time you need to reach a good level of granularity!
  33. 33. References 1. D. Leffingwell and P. Behrens, “A user story primer,” Agile Requirements: Lean Requirements Practices for Teams, Programs and the Enterprise, Agile Software Development Series, A. Cockburn and J. Highsmith, Series Editors, 2009. 2. O. Liskin, R. Pham, S. Kiesling, and K. Schneider, “Why we need a granularity concept for user stories,” in International Conference on Agile Software Development, 2014, pp. 110–125. 3. “New to agile? INVEST in good user stories,” Agile For All, 14-May- 2009. . 33
  34. 34. Q&A Thankyou! 34

Editor's Notes

  • Obiettivo
  • User stories are a well-established way to record requirements in agile projects.
    A User Story is a brief statement of intent that describes something the system needs to do for the user.
    User stories are a tool for defining a system’s behavior in a way that is understandable to both the developers and users.
  • Reduce the risks of failing commitment
    Fastest learners win
    Large Items are harder to plan/estimate
    Progress = Happiness
    Release = Value
  • User stories are a well-established way to record requirements in agile projects.
    A User Story is a brief statement of intent that describes something the system needs to do for the user.
    User stories are a tool for defining a system’s behavior in a way that is understandable to both the developers and users.
  • User stories are a well-established way to record requirements in agile projects.
    A User Story is a brief statement of intent that describes something the system needs to do for the user.
    User stories are a tool for defining a system’s behavior in a way that is understandable to both the developers and users.
  • User stories are a well-established way to record requirements in agile projects.
    A User Story is a brief statement of intent that describes something the system needs to do for the user.
    User stories are a tool for defining a system’s behavior in a way that is understandable to both the developers and users.
  • a user story is not a contract for specific functionality, but rather a placeholder for requirements to be discussed, developed, tested, and accepted
    This process of negotiation between the business and the team recognizes the legitimacy and primacy of the business inputs, but allows for discovery through collaboration and feedback.
  • a story can be developed, tested, and potentially even delivered, on its own
  • Value is the most important attribute in the INVEST model and every user story must provide some value to the user, customer, or stakeholder of the product
    While normally the value is focused on the user interacting with the system, sometimes the value is more appropriately focused on a customer representative or key stakeholder
  • The minimal investment in estimation is to determine if it can be completed within a single iteration. Additional estimation accuracy will increase the team’s predictability.
    One of the primary benefits of estimating user stories is not simply to derive a precise size, but rather to draw out any hidden assumptions, missing acceptance criteria, and to clarify the team’s shared understanding of the story. Thus, the conversation surrounding the estimation process is as (or more) important, than the actual estimate
  • Increased Throughput
    From queuing theory, we know that smaller batch sizes go through a system faster
    Decreased Complexity
    Smaller stories not only go through faster because of their raw, proportional size, but they go through faster yet because of their decreased complexity, and complexity has a non-linear relationship to size
  • Increased Throughput
    From queuing theory, we know that smaller batch sizes go through a system faster
    Decreased Complexity
    Smaller stories not only go through faster because of their raw, proportional size, but they go through faster yet because of their decreased complexity, and complexity has a non-linear relationship to size
  • User stories are a well-established way to record requirements in agile projects.
    A User Story is a brief statement of intent that describes something the system needs to do for the user.
    User stories are a tool for defining a system’s behavior in a way that is understandable to both the developers and users.
  • ×