Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

177 splitting epics and user stories (dave todaro)

67 views

Published on

ProductCamp Boston May 12 2018

Published in: Marketing
  • Be the first to comment

177 splitting epics and user stories (dave todaro)

  1. 1. Using Micro Milestones to Boost Momentum Splitting Epics and User Stories
  2. 2. Dave Todaro linkedin.com/in/dtodaro CEO Ascendle
  3. 3. Business Innovation Strategy BuildingSupport
  4. 4. 480% 3 year revenue growth 114% 1 year revenue growth +20% Net income 200+ Software and quality assurance engineers $500,000 Typical project value 3,000 hours Typical project effort 35+ years Software development experience Typical project duration 7 months 5 Development centers (US and Eastern Europe)
  5. 5. Epic Story Story Epic Sprint Sprint Sprint Don’t Fit Into a Sprint
  6. 6. Scrum Rule •One or more stories must be shippable by the end of the sprint •Part of a story doesn’t count •Problem: Stories are too big to get done in one sprint •Solution: Make smaller stories
  7. 7. Epic Story Story Epic Sprint Sprint Sprint Story Story Story Story Only split what you need for the next sprint 25% - 33% of Average Velocity Example: Average Velocity = 15 5 story points or smaller Involve the whole Scrum team
  8. 8. Database Data Access Layer Business Layer Presentation Layer 1 2 3 4 You can’t ship a layer!
  9. 9. Database Data Access Layer Business Layer Presentation Layer 1 2 3 4 Every story is shippable Avoids YAGNI
  10. 10. Splitting Strategies •Data boundaries •Operational boundaries •CRUD operations •Cross-cutting concerns •Performance •Different priorities
  11. 11. Data Boundaries •Group related data together into separate stories •Example: Banking app •View recent transactions •View details for a check •View statements
  12. 12. Operational Boundaries •Start with simple functionality •Then make it more fancy •Example: Streaming music app •Listen to a random selection of music •Create my own playlist •Share my playlist with others
  13. 13. CRUD Operations •Create/Read/Update/Delete •Example: Word processing app •View a Microsoft Word document •Modify and save existing document •Create new document from template
  14. 14. Cross-cutting Concerns • Functionality that applies to most or all stories • Examples: • Security • Validation • Error handling • Logging • Encryption
  15. 15. Cross-cutting Concerns •Example: Human resources web app •Anyone can see/modify salary information •Only specific users can see/modify salary information •Only users with specific security role permissions can see/modify salary information
  16. 16. Performance •“Make it work, then make it fast.” •Start by focusing on functionality •Then worry about meeting performance requirements •Example: Internet of things web service •Process location updates from devices •Handle 1,000 location updates per second
  17. 17. Different Priorities •Split out less-important functionality •Move it down the product backlog •Example: Social media app •Upload photos •Tag friends •Facial recognition for auto-tagging friends
  18. 18. User Story: Spell Checker Operational Priority As an author I want to check my spelling so I can avoid spelling errors • I can check spelling in English • I can check spelling in Spanish • I can see a wavy line under misspelled words • I can get suggestions for a misspelled word • I can ignore all instances of a misspelled word • I can add a word to the dictionary
  19. 19. Split Spell Checker Stories • As an author I want an indication of misspelled words so I can prevent spelling errors in my document • As an author I want to get suggestions for each misspelled word so I don’t have to look it up • As an author I want to ignore certain misspelled words so I can avoid an indication for special words I use • As an author I want to add a word to the dictionary so I can make the spell check more accurate • As an author I want to check spelling in Spanish so I can check spelling when I write in that language
  20. 20. Summary • Split stories and epics that are too big to fit into a sprint • Split just enough to fit into the next sprint • Involve the whole Scrum team • Maximum size guideline for a story entering a sprint: 25% to 33% of average velocity • Multiple splitting strategies to choose from
  21. 21. http://bit.ly/davescrumtips • Short tips in your inbox • Not available anywhere else • Early access to new book
  22. 22. THANK YOU! ascendle.com/blog dave@ascendle.com ascendle.com http://bit.ly/davescrumtips linkedin.com/in/dtodaro

×