Easy ways to break up by Dipesh Pala

1,145 views

Published on

Insightful Agile - Easy Ways to Break Up!

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

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

No notes for slide

Easy ways to break up by Dipesh Pala

  1. 1. Easy ways to Break Up! By Dipesh Pala
  2. 2. Why are real life break ups so difficult?
  3. 3. Why are real life break ups so difficult? • Risky
  4. 4. Why are real life break ups so difficult? • Risky • Dependency
  5. 5. Why are real life break ups so difficult? • Risky • Dependency • Complex
  6. 6. Why are real life break ups so difficult? • Risky • Dependency • Complex • Expensive
  7. 7. Why are real life break ups so difficult? • Risky • Dependency • Complex • Expensive • Lack of Confidence
  8. 8. Why are real life break ups so difficult? • Risky • Dependency • Complex • Expensive • Lack of Confidence • Not knowing When or How to Break Up!
  9. 9. Break Up Real UserDifficulty Life StoriesRiskyDependencyComplexExpensiveLack of ConfidenceNot knowing When orHow to Break Up
  10. 10. Three C’s by Ron Jeffries CARD CONVERSATION CONFIRMATION
  11. 11. User Story Card This is an invitation to have a Conversation that will result in Confirmation of the requirements
  12. 12. Three C’s by Ron Jeffries CARD CONVERSATION CONFIRMATION+1 more C
  13. 13. Three C’s by Ron Jeffries CARD CONVERSATION CONFIRMATION+1 more C COMMITMENT
  14. 14. Bill Wake’s INVEST model I N V E S T
  15. 15. Bill Wake’s INVEST model I NDEPENDENT N V E S T
  16. 16. Bill Wake’s INVEST model I NDEPENDENT NEGOTIABLE V E S T
  17. 17. Bill Wake’s INVEST model I NDEPENDENT NEGOTIABLE VALUABLE E S T
  18. 18. Bill Wake’s INVEST model I NDEPENDENT NEGOTIABLE VALUABLE ESTIMABLE S T
  19. 19. Bill Wake’s INVEST model I NDEPENDENT NEGOTIABLE VALUABLE ESTIMABLE SMALL T
  20. 20. Bill Wake’s INVEST model I NDEPENDENT NEGOTIABLE VALUABLE ESTIMABLE SMALL TESTABLE
  21. 21. DIFFICULTIES
  22. 22. DIFFICULTIES EXCUSES
  23. 23. DIFFICULTIES EXCUSES
  24. 24. DIFFICULTIES EXCUSES
  25. 25. DIFFICULTIES EXCUSES
  26. 26. Break Up Tip #1This story is ... Difficulty too Complex Does the story describe a Consideration workflow? Take a thin slice through the Opportunity workflow and enhance it later
  27. 27. Original User StorySuggested split by slicing the workflow: Calculate the Total Payment Amount...
  28. 28. Break Up Tip #2This story is ... Difficulty too Complex Does the story include Consideration multiple operations? Separate the operations into Opportunity separate stories
  29. 29. Original User Story
  30. 30. Original User StorySuggested split by separate operations
  31. 31. Break Up Tip #3This story is ... Difficulty too Complex Does this story have a simple core that provides most of Consideration the value? Split the story to do the Opportunity simplest option first and enhance it later
  32. 32. Original User Story
  33. 33. Original User StorySuggested split by simple / complex variations
  34. 34. Break Up Tip #4This story is ... Difficulty too Complex Does this story have a Consideration Complex User Interface? Split the story to do a simple Opportunity UI first and enhance later
  35. 35. SimpleComplex
  36. 36. Original User Story
  37. 37. Original User StorySuggested split by UI variations
  38. 38. Key Takeaways...
  39. 39. Key Takeaways...Break Up Tip #1Take a thin slice through the workflow andenhance it later
  40. 40. Key Takeaways...Break Up Tip #1 Break Up TipTake a thin slice #2 through the workflow and Separate theenhance it later operations into separate stories
  41. 41. Key Takeaways... Break Up Tip #3 Do the simple version first and enhance it laterBreak Up Tip #1 Break Up TipTake a thin slice #2 through the workflow and Separate theenhance it later operations into separate stories
  42. 42. Key Takeaways... Break Up Tip #3 Do the simple version first and enhance it laterBreak Up Tip #1 Break Up TipTake a thin slice #2 through the workflow and Separate the Break Up Tipenhance it later operations into #4 separate stories Do a simple UI first and enhance later
  43. 43. Break Up Tip #5This story is ... Difficulty too Expensive Does this story refer to multiple users doing similar Consideration things at the same time? Split the story to handle Opportunity single user first and enhance it later
  44. 44. Suggested split by Single / Multiple users
  45. 45. Suggested split by Single / Multiple users
  46. 46. Break Up Tip #6This story is ... Difficulty too Expensive Does this story become expensive due to non- Consideration functional requirements? Split the story to just make it Opportunity work first and enhance it later
  47. 47. If you can’t fly, Run.If you can’t run, Walk.If you can’t walk, Crawl.But, by all means keep moving. - Dr. Martin Luther King, Jr.
  48. 48. Suggested split by deferring Performance or Quality
  49. 49. Break Up Tip #7This story is ... Difficulty too Expensive Does this story have a major effort regardless of how it is Consideration split? Split the story so that most of Opportunity the value comes from the first split
  50. 50. All Credit Card types
  51. 51. Original User StorySuggested split by Major Effort
  52. 52. Key Takeaways...
  53. 53. Key Takeaways... Break Up Tip #5Handle single userfirst and enhance it later
  54. 54. Key Takeaways... Break Up Tip #5 Break Up TipHandle single user #6first and enhance it later Just make it work first and enhance it later
  55. 55. Key Takeaways... Break Up Tip #5 Break Up Tip Break Up Tip #7Handle single user #6first and enhance Split the story so it later Just make that most of the it work first and value comes from enhance it later the first split
  56. 56. Break Up Tip #8This story has ... Difficulty too many dependencies Does this story have a variety Consideration of business logic? Split the story to do a subset Opportunity of rules first, and enhance it later
  57. 57. Original User Story
  58. 58. Original User StorySuggested split by business logic
  59. 59. Break Up Tip #9This story has ... Difficulty too many dependencies Does this story refer to data Consideration from multiple sources? Split the story to handle data Opportunity from one source first and enhance later
  60. 60. Original User Story
  61. 61. Original User StorySuggested split by data variation
  62. 62. Break Up Tip #10This story has ... Difficulty too many dependencies Does this story need any investigation prior to being Consideration started? Split the story so that the Opportunity research is done first, with action later
  63. 63. The longest journey starts with a small step...
  64. 64. Key Takeaways...
  65. 65. Key Takeaways...Break Up Tip #8Do a subset ofrules first, andenhance it later
  66. 66. Key Takeaways...Break Up Tip #8 Break Up TipDo a subset of #9rules first, andenhance it later Handle data from one interface first and enhance later
  67. 67. Key Takeaways...Break Up Tip #8 Break Up Tip Break Up Tip #10Do a subset of #9rules first, and Do the researchenhance it later Handle data from first, with action one interface first later and enhance later
  68. 68. References• http://www.richardlawrence.info/2009/10/28/patterns-for-splitting-user- stories• http://www.mountaingoatsoftware.com/topics/user-stories• http://www.agileforall.com/2010/05/03/new-to-agile-remember-a-user- story-is-more-than-a-card• http://xprogramming.com/articles/expcardconversationconfirmation• http://xp123.com/articles/invest-in-good-stories-and-smart-tasks• Cohn, Mike. 2004. User Stories Applied: For Agile Software Development. Boston, MA: Addison-Wesley.• Jeffries, Ron. 2001, August. “Essential XP: Card, Conversation, and Confirmation.” XP Magazine.• All images collected through Google
  69. 69. Q & A
  70. 70. Dipesh PalaAgile Capability LeadSolnet Solutionse: dipesh.pala@solnetsolutions.com.aum: +61 404 152 850p: 1800 442 472w: solnetsolutions.com.auin: au.linkedin.com/in/dipeshpalat: @dipeshpala

×