The document discusses how user stories could be improved by writing them in a clearer, simpler manner that is understandable to a 13-year-old. Better user stories clarify what data or features are needed and why, rather than using vague terminology. A sample is given of transforming a unclear story using technical jargon into a clear story about getting customer purchase history to identify customers to contact. Writing better stories upfront can help avoid misunderstandings that lead to extra work and costs down the road.

1. Your user stories could be better (and why you should care) Elliot Susel, Agile Project Manager

2. Agile embraces change… Why care but why change what you could have done correctlythe first time?

4. Misunderstood feature motivationSolution: Write better stories

5. That sounds nice… Better Stories But how do we write better stories?

6. Would a 13-year old understand? Better Stories If not, replace terminology with simplewording

7. Better Stories Sample (Yes, this actually happened) “As a salesman, I want to get ABC data from XYZ system so that I can view reports” What the heck does that mean?

8. Better Stories ABC data from XYZ system Customer Data ABC data from XYZ system Customer Data A history of customer purchases Clarify Feature

9. Clarify Motivation Better Stories View reports Identify relevant customers View reports Identify relevant customers Identify customers that I want to contact

10. “As a salesman, I want to get ABC data from XYZ system so that I can view reports” -> As a salesman, I want a history of customer purchases so that I can identify customers that I want to contact Better Stories Translation Notice a difference?

11. Because the story was simple… Better Delivery we were able to innovate!

12. Major Cost Savings Better Delivery 100+ points Additional development in XYZ system -> 30points

13. Questions? elliot.susel@gmail.com online presence: about.me/ElliotSusel