The Art of Storytelling

686 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
686
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

The Art of Storytelling

  1. 1. The Art of Storytelling By Fadi Stephan
  2. 2. Mike CohnJeff PattonUser Role Modeling
  3. 3. Simple, clear, short description ofcustomer valued functionality.3 C’s: Card, Conversation, Confirmation.Represents customer requirements.
  4. 4. Title: Priority:As a [type of user], I can [goal] so that[value]Notes:Assumptions:Constraints: Estimate:
  5. 5. Checkout Using Credit Card 25As a book shopper, I can checkout using mycredit card so that I can purchase a selectedbook.Notes: Support mc, visa, amexConstraint: Must use Chase payment service 13 pts
  6. 6. Given [context]When [some event]Then [outcome]
  7. 7. Checkout Using Credit CardTest with valid mc, visa, amex passesTest with valid other cards failsTest with expired card failsTest with invalid cvv failsTest with invalid zip fails
  8. 8. Title: Priority:As a [type of user], I can [goal] so that[reason]Notes:Assumptions:Constraints: Estimate:
  9. 9. Title: Priority:As a [type of user], I can[goal] so that [reason]Notes:Assumptions:Constraints: Estimate: “Get smaller cards”
  10. 10. How do I describewhat I want? How do I schedule this How do I work and validate track its What are the that this progress? details of work is what I need done? to code?
  11. 11. Other Options1. The system shall…2. Use Cases
  12. 12. Verbal Communication
  13. 13. Right Size
  14. 14. Understandable
  15. 15. Iterative Development
  16. 16. User Role Modeling
  17. 17. As a forgetful user, I can reset my passwordso that I can access my account.
  18. 18. As a customer support manager, I canautomate password resets so that I can reducesupport calls.
  19. 19. INVEST
  20. 20. Negotiable
  21. 21. Valuable
  22. 22. Estimatable
  23. 23. Small
  24. 24. Splitting Stories
  25. 25. Dependency
  26. 26. Too Big
  27. 27. Compound
  28. 28. Bugs
  29. 29. Ve Sr lt ii cc ea sl
  30. 30. Data Boundaries
  31. 31. Operational Boundaries
  32. 32. Cross Cutting Concerns
  33. 33. Performance
  34. 34. Priority
  35. 35. AgileJourneyman.com
  36. 36. References• Agile Estimating and Planning, Mike Cohn• User Stories Applied, Mike Cohn• Mountain Goat Software: http://www.mountaingoatsoftware.com• Agile Product Design: http://www.agileproductdesign.com

×