10 Easy Ways To Break Up by Dipesh Pala
3 likes1,238 views
The document discusses 10 tips for breaking up user stories that are too complex or difficult into simpler stories. It provides examples of how to split stories by slicing the workflow, focusing on the core functionality first, separating complex and simple elements, handling single users before multiple users, prioritizing research before development, and splitting dependencies and logic across multiple stories. Breaking large stories into simpler stories allows for faster delivery of value and incremental improvements.
10 Easy Ways To Break Up by Dipesh Pala
- 1. By Dipesh Pala Agile NZ 2015 2 September 2015 @DipeshPala 10 EASY WAYS TO BREAK UP
- 2. @DipeshPala
- 3. Why are real life break ups so difficult? @DipeshPala
- 4. @DipeshPala Why are real life break ups so difficult? Risky
- 5. @DipeshPala Why are real life break ups so difficult? Risky Dependency
- 6. Once upon a 岳庄馨艶@禽庄沿艶壊鞄永温鉛温 Why are real life break ups so difficult? Risky Dependency Complex
- 7. Once upon a 岳庄馨艶@禽庄沿艶壊鞄永温鉛温 Why are real life break ups so difficult? Risky Dependency Complex Expensive
- 8. Once upon a 岳庄馨艶@禽庄沿艶壊鞄永温鉛温 Why are real life break ups so difficult? Risky Dependency Complex Expensive Lack of Confidence
- 9. @DipeshPala Why are real life break ups so difficult? Risky Dependency Complex Expensive Lack of Confidence Not knowing When or How to Break Up!
- 10. @DipeshPala Break Up Difficulty Real Life User Stories Risky Dependency Complex Expensive Lack of Confidence Not knowing When or How to Break Up
- 11. @DipeshPala
- 12. @DipeshPala Three Cs by Ron Jeffries CARD CONVERSATION CONFIRMATION @DipeshPala
- 13. User Story Card This is an invitation to have a Conversation that will result in Confirmation of the requirements
- 15. @DipeshPala I N V E S T N D E P E N D E NT
- 16. @DipeshPala I N V E S T N D E P E N D E NT E G OT I A B L E
- 17. @DipeshPala I N V E S T N D E P E N D E NT E G OT I A B L E A L U A B L E
- 18. @DipeshPala I N V E S T N D E P E N D E NT E G OT I A B L E A L U A B L E S T I M A B L E
- 19. @DipeshPala I N V E S T N D E P E N D E NT E G OT I A B L E A L U A B L E S T I M A B L E M A L L
- 20. @DipeshPala I N V E S T N D E P E N D E NT E G OT I A B L E A L U A B L E S T I M A B L E M A L L E S T A B L E
- 21. @DipeshPala
- 23. Opportunity Consideration Excuse @DipeshPala This story is too Complex Does the story describe a workflow? Take a thin slice through the workflow and enhance it later Break UpTip #1
- 24. @DipeshPala
- 25. @DipeshPala
- 26. Calculate the Total Payment Amount... Original User Story Suggested split by slicing the workflow: @DipeshPala
- 27. Opportunity Consideration Excuse @DipeshPala This story is too Complex Does this story have a simple core that provides most of the value? Split the story to do the simplest option first and enhance it later Break UpTip #2
- 28. @DipeshPala
- 29. @DipeshPala Suggested split by simple / complex variations Original User Story
- 30. Opportunity Consideration Excuse @DipeshPala This story is too Complex Does this story have a Complex User Interface? Split the story to do a simple UI first and enhance later Break UpTip #3
- 31. @DipeshPala
- 32. Opportunity Consideration Excuse @DipeshPala This story is too Complex Does the story include multiple operations? Separate the operations into separate stories Break UpTip #4
- 33. Suggested split by separate operations Original User Story @DipeshPala
- 34. Opportunity Consideration Excuse @DipeshPala This story is too Expensive Does this story become expensive due to non-functional requirements? Split the story to just make it work first and enhance it later Break UpTip #5
- 35. @DipeshPala If you cant fly, Run. If you cant run, Walk. If you cant walk, Crawl. But, by all means keep moving. - Dr. Martin Luther King, Jr.
- 36. Small wins are something people can experience pretty regularly if the work is chunked down to manageable pieces. @DipeshPala
- 37. @DipeshPala Suggested split by deferring Performance or Quality
- 38. Opportunity Consideration Excuse @DipeshPala This story is too Expensive Does this story refer to multiple users doing similar things at the same time? Split the story to handle single user first and enhance it later Break UpTip #6
- 39. Suggested split by Single / Multiple users @DipeshPala
- 40. Opportunity Consideration Excuse @DipeshPala This story is too Expensive Does this story have a major effort regardless of how it is split? Split the story so that most of the value comes from the first split Break UpTip #7
- 42. Opportunity Consideration Excuse @DipeshPala This story has too many dependencies Does this story have a variety of business logic? Split the story to do a subset of rules first, and enhance it later Break UpTip #8
- 43. Once upon a 岳庄馨艶@禽庄沿艶壊鞄永温鉛温
- 44. @DipeshPala Original User Story Suggested split by business logic
- 45. Opportunity Consideration Excuse @DipeshPala This story has too many dependencies Does this story refer to data from multiple sources? Split the story to handle data from one source first and enhance later Break UpTip #9
- 46. @DipeshPala
- 47. Opportunity Consideration Excuse @DipeshPala This story has too many dependencies Does this story need any investigation prior to being started? Split the story so that the research is done first, with action later Break UpTip #10
- 48. Once upon a 岳庄馨艶@禽庄沿艶壊鞄永温鉛温 The lon ge st journ ey starts wi th a small ste p...
- 49. @DipeshPala
- 50. @DipeshPala
- 51. @DipeshPala
- 52. @DipeshPala
- 53. @DipeshPala
- 54. @DipeshPala
- 55. Q & O
- 56. 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 StoriesApplied: 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 @DipeshPala
- 57. ThankYou Contact details Dipesh Pala Agile Capability Leader IBM Asia Pacific dipeshpala@au1.ibm.com @DipeshPala au.linkedin.com/in/dipeshpala slideshare.net/DipeshPala
- 58. The Title Of Your Presentation In Here Over Two Lines If Necessary Your name Your organisation Thanks for listening Dipesh Pala IBM