Exploring User Stories Through Mindmapping


Published on

I talked about using mind mapping to explore user context first to extract user stories effectively.
Using a mind mapping + UML software "JUDE".

Published in: Technology
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Exploring User Stories Through Mindmapping

  1. 1. Exploring User Stories through Mind Mapping Kenji HIRANABE Change Vision, Inc.
  2. 2. Objectives <ul><li>To understand what is Mind Mapping and how software development can benefit from it. </li></ul><ul><li>To experience how to use Mind Maps to explore user wish and carve out User Stories . </li></ul>
  3. 3. Agenda <ul><li>Introduction </li></ul><ul><li>What is a Mind Map and Why </li></ul><ul><li>How Software Development Benefits from Using Mind Maps </li></ul><ul><li>Exploring User Wish using Mind Mapping </li></ul><ul><li>Demonstration </li></ul><ul><li>Let’s try ! </li></ul><ul><li>Conclusion </li></ul>
  4. 4. Kenji HIRANABE(1/2) <ul><li>(co-)Translator of … </li></ul>XP/ Agile books <ul><li>(co-)Author of … </li></ul>C++ book OO, UML books Mind Map book
  5. 5. Kenji HIRANABE(2/2) <ul><li>CEO of Change Vision, Inc. </li></ul><ul><li>JUDE – UML editor </li></ul><ul><ul><li>With Mind Map, ERD </li></ul></ul><ul><ul><li>http://jude.change-vision.com/ </li></ul></ul><ul><li>TRICHORD – Agile Project Kanban Board </li></ul><ul><ul><li>Kanban, Parking Lot, </li></ul></ul><ul><ul><li>http://trichord.change-vision.com/ </li></ul></ul><ul><ul><li>Burndowns, Smiley Calendar </li></ul></ul>
  6. 6. Agile2008 <ul><li>I’ll talked about … </li></ul><ul><li>Learning Kaizen from Toyota [with Mind Maps] </li></ul><ul><li>New Car Development in Toyota </li></ul><ul><li>Exploring User Stories through Mind Mapping </li></ul><ul><li>Dear XP – song at the party </li></ul>
  7. 7. Stickyminds.com article “Agile Modeling with Mind Map and UML” Search: stickyminds Kenji HIRANABE
  8. 8. Mind Map <ul><li>Tony Buzan </li></ul><ul><li>Graphical note technique </li></ul><ul><li>Visualize thoughts with a radiant structure </li></ul><ul><ul><li>Keyword Oriented </li></ul></ul><ul><ul><li>Loose syntax and semantics </li></ul></ul><ul><ul><li>Fast and Easy </li></ul></ul><ul><ul><li>High level View </li></ul></ul><ul><ul><li>Evocative </li></ul></ul><ul><ul><li>Explore and Gather Ideas </li></ul></ul>
  9. 9. da Vinci uses Pictures and Words at the same time
  10. 10. Mind Mapping <ul><li>Examples … </li></ul>
  11. 11. Kent Beck’s XP 2nd
  12. 12. Retrospectives using Keep/Problem/Try format
  13. 13. Product Feature Map in Release Planning
  14. 14. Seminar Ideas
  15. 15. Project Christmas Planning
  16. 16. Meeting Minutes Template
  17. 17. Design Patterns
  18. 18. Mastering the Requirements Process by Suzanne and James Robertson, 1999.
  19. 19. Self-Introduction Mind Map <ul><li>Central Image </li></ul><ul><ul><li>Your name and your Icon </li></ul></ul><ul><ul><li>What describes you most </li></ul></ul><ul><li>BOI’s may be, </li></ul><ul><ul><li>Why (you came to Tronto)? </li></ul></ul><ul><ul><li>What (do you do) ? </li></ul></ul><ul><ul><li>Favorites (sessions so far) </li></ul></ul><ul><li>3-minute introduction in pairs </li></ul>
  20. 21. User Stores: Ron Jeffries’ 3 Cs <ul><li>Card </li></ul><ul><ul><li>Written on note cards. </li></ul></ul><ul><ul><li>Cards may be annotated with estimates, notes, etc. </li></ul></ul><ul><li>Conversation </li></ul><ul><ul><li>Details behind the story come out during conversation with customer </li></ul></ul><ul><li>Confirm </li></ul><ul><ul><li>Acceptance tests confirm the story was coded correctly </li></ul></ul>
  21. 22. User Stories: Mike Cohn <ul><li>Shift focus from writing to talking </li></ul><ul><li>Metaphor of Trawling (by Suzanne and James Robertson) </li></ul><ul><ul><li>Requirements can be captured with different sized nets </li></ul></ul><ul><ul><li>Requirements change, mature, possibly die </li></ul></ul><ul><ul><li>Skill is a factor </li></ul></ul><ul><li>Avoid “The user”, find “Roles” </li></ul><ul><li>In order to <benefit>, as a <role>, I want to <story>, </li></ul>
  22. 23. Mastering the Requirements Process by Suzanne and James Robertson, 1999.
  23. 24. User Wish Mind Map <ul><li>The first step of getting what you want. </li></ul><ul><li>Get the Big Picture . </li></ul><ul><li>Who ? first. </li></ul><ul><li>Semi-structured. </li></ul><ul><li>Gather info and mine UseCases / User Stories . </li></ul>
  24. 25. Demonstration <ul><li>City Library System Interview… </li></ul>
  25. 26. Library Interview Mind Map
  26. 27. UseCase Diagram
  27. 28. User Stories Mind Map
  28. 29. User Wish Big Picture Mind Map User Stories Why? Who? When? Estimate, Plan, Prioritize, Test value role
  29. 30. Conclusion <ul><li>Mind Mapping is effective when </li></ul><ul><ul><li>Gathering Information </li></ul></ul><ul><ul><li>Exploring topics freely </li></ul></ul><ul><li>User interview with Mind Mapping </li></ul><ul><ul><li>Is Semi-structured </li></ul></ul><ul><ul><li>Gives a high-level view of user wish </li></ul></ul><ul><ul><li>Creates a big picture of the user wish from which you can carve out good use cases or user stories. </li></ul></ul><ul><li>Why, Who, When are good input to user stories. </li></ul>
  30. 31. The mind map tool <ul><li>JUDE – UML editor </li></ul><ul><ul><li>With Mind Map, ERD, DFD </li></ul></ul><ul><ul><li>http://jude.change-vision.com/ </li></ul></ul>
  31. 32. User Stories Spreadsheet Also to PowerPoint!