Upgrade to Pro — share decks privately, control downloads, hide ads and more …

ADN Columbus 2013 - Stories, Good and Bad

August 19, 2013

ADN Columbus 2013 - Stories, Good and Bad


August 19, 2013

More Decks by Improving

Other Decks in Education


  1. ©2009 Improving Enterprises, Inc. You will learn: •  Tricks &

    Traps When Writing User Stories •  Characteristics of ‘bad’ user stories •  How To Make Sure ‘Big Things’ Don’t Get Missed
  2. ©2009 Improving Enterprises, Inc. User Story Sample Format   Example

      As a < role > I want to < do something > So that < business value >   As an administrator I want to deactivate an account so that the account owner can no longer log in or receive email notifications  
  3. ©2009 Improving Enterprises, Inc. Characteristics User Story "  short narrative

    "  small piece of functionality "  business value "  fosters collaboration and communication
  4. ©2009 Improving Enterprises, Inc. We’ve already discussed these… "  Vague

    ‘user’ rather than specific actor "  Too big "  Refers to development (or analysis, design and/or testing)
  5. ©2009 Improving Enterprises, Inc. Parroting "  Example: I want to

    locate previous food order lists so that I can see all the lists that I have. "  Improvement: As a customer ordering food, I want to see my saved food order lists so that I can reuse the list for future orders, making ordering faster and more accurate.
  6. ©2009 Improving Enterprises, Inc. Excessive So That "  Example: As

    a Manny’s food service customer I need to save my list so that later I can save a copy, print, or email the list for other uses. "  Real (or additional) requirement hidden in So That "  So That too complex "  So That has multiple parts
  7. ©2009 Improving Enterprises, Inc. "  Improvement: As a Manny’s food

    service customer, I need to save, copy, print, and email my list so that I can edit it again, check a received shipment against a printed list, and send the list to a restaurant. ?
  8. ©2009 Improving Enterprises, Inc. Exercise •  Divide Up •  Select

    a product owner •  Rules: •  Can not say the words on the slide •  Can only use imperatives and similes (no ‘rhymes with’) to describe image •  No drawing!
  9. ©2009 Improving Enterprises, Inc. Round 1 Communication: In Writing Only

    •  Chair •  Wood •  Seat •  Legs •  Back
  10. ©2009 Improving Enterprises, Inc. Round 2 Communication: Speaking •  Teapot

    •  Kettle •  Spout •  Short/Stout •  Handle
  11. ©2009 Improving Enterprises, Inc. •  In addition to using some

    of the tips discussed today •  In software, we are rarely creating something that already exists. Without a common vocabulary, we are forced to communicate in imperatives and metaphors and, quite often, much is lost in translation. •  Iterative development with demonstrations allow us to hone in on what is really needed, rather than what is asked for.