ADN Columbus 2013 - Stories, Good and Bad

Transcript

1. ©2009 Improving Enterprises, Inc. Anita Shankar Me I love working for
2. ©2009 Improving Enterprises, Inc. User Stories, Good and Bad
3. ©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
4. ©2009 Improving Enterprises, Inc. Customer Bad Good User Actor
5. ©2009 Improving Enterprises, Inc. Program Actor
6. ©2009 Improving Enterprises, Inc. Just the right size
7. ©2009 Improving Enterprises, Inc. Demonstrable
8. ©2009 Improving Enterprises, Inc. Quantifiable and Testable
9. ©2009 Improving Enterprises, Inc. Value
10. ©2009 Improving Enterprises, Inc. For the business
11. ©2009 Improving Enterprises, Inc. Communication < Getting things done
12. ©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  
13. ©2009 Improving Enterprises, Inc. Characteristics User Story "  short narrative "  small piece of functionality "  business value "  fosters collaboration and communication
14. ©2009 Improving Enterprises, Inc. Characteristics of Bad User Stories
15. ©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)
16. ©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.
17. ©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
18. ©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. ?
19. ©2009 Improving Enterprises, Inc. Making sure you don’t miss something
20. ©2009 Improving Enterprises, Inc. Personas
21. ©2009 Improving Enterprises, Inc. Auditors, Accountants, and information consumers
22. ©2009 Improving Enterprises, Inc.
23. ©2009 Improving Enterprises, Inc. Outside Review
24. ©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!
25. ©2009 Improving Enterprises, Inc. Round 1 Communication: In Writing Only •  Chair •  Wood •  Seat •  Legs •  Back
26. ©2009 Improving Enterprises, Inc. Round 2 Communication: Speaking •  Teapot •  Kettle •  Spout •  Short/Stout •  Handle
27. ©2009 Improving Enterprises, Inc. Round 3 •  Motorcycle •  Trailer •  Seat •  Camper
28. ©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.
29. ©2009 Improving Enterprises, Inc. Thank You Anita Shankar – anita.shankar@improvingenterprises.com