Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Splitting user stories

544 Aufrufe

Veröffentlicht am

Presentation from Scrum Day Twin Cities 2014

Veröffentlicht in: Software
  • Als Erste(r) kommentieren

Splitting user stories

  1. 1. Better User Stories = Better Sprints How to Split User Stories By Lonnie Weaver-Johnson
  2. 2. Agenda • Why split stories • How to split stories • Practice • Summary
  3. 3. What is the Value of Splitting Stories? • Smaller Stories allows a team a better chance for success – More clarity/less ambiguity – Ability to see progress easier – More opportunity to ID potential issues • More stories moving to the “done” column means: – Higher level of satisfaction – More motivated teams – Happy customers
  4. 4. Lots of Ideas for Splitting Stories • Chris Sims and Bill Wake have useful information in this area • Be careful about splitting stories into: design story, development story, test story. Why? • Look at Smallerstories.com (Sims) • Look at http://xp123.com/articles/twenty-ways- to-split-stories/ (Wake)
  5. 5. Idea #1 Look for connectors with words or punctuation • Words like “and, or, if, when, but, then, as well as, etc.” • Punctuation: commas Activity
  6. 6. Idea #2 Look for generic words that could be replaced with more specific terms • Watch for generic adverbs, adjectives, nouns, and verbs and replace them with something specific • Example: A word like “easy” could be replaced with phrases like: “simple to use”, “fewer key strokes”, “obvious to the user”, etc. Activity
  7. 7. Idea #3 Use acceptance criteria to break the story up further • Often if you have a large number of acceptance criteria it is an indication that there are probably user stories hidden in them Activity
  8. 8. Idea #4 Use acceptance criteria to break the story up further • If acceptance criteria need their own explanations then there are probably hidden user stories in the acceptance criteria Activity
  9. 9. Summary: Use Smaller Stories • Large User Stories can lead to troubled Sprints • Help teams be successful by breaking stories up into very granular pieces of work • Highly successful teams get a lot of work done
  10. 10. Introduction • Lonnie Weaver-Johnson • BA, University of MN • Local Agile Coach, Trainer, CST • 25 years in IT (BA and SLT Member) • Reach Out: – Lonnie@Lwjsolutions.com – @Lonniewj – LinkedIn

×