Using Astah to Explore User Wish Through Mindmapping

1,024
-1

Published on

Gathering requirements or "User Stories" is always a challenging activity in Agile or in any other approaches.In this session, I propose using mind mapping that focuses to explore "User Wish" - a vague shape of user requirements before it is written into a form of User Stories, using the modeling tool Astah.

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,024
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
17
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Using Astah to Explore User Wish Through Mindmapping

  1. 1. Exploring User Wishthrough Mind MappingKenji HIRANABEMind map by Michal Splho{Using for}
  2. 2. 2 Seeing is understanding.Seeing is understanding.
  3. 3. 3 Seeing is understanding.Seeing is understanding.AsakusaAsakusa,,TokyoTokyoFukuiFukuiFukuiFukuiAsakusaAsakusa
  4. 4. 4 Seeing is understanding.Seeing is understanding.Agenda• Introduction• What is a Mind Map and Why• Exploring User Wish using MindMapping• Demonstration using Astah• Conclusion
  5. 5. 5 Seeing is understanding.Seeing is understanding.Kenji HIRANABE(1/2)• (co-)Translator of …OO, UML books Mind Map bookXP/ Agile books• (co-)Author of …C++ bookScrum bookAgile and Scrum:Collaborative SoftwareDevelopment That ConnectsCustomers, Engineers andManagement
  6. 6. 6 Seeing is understanding.Seeing is understanding.Kenji HIRANABE(2/2)• CEO of Astah.net.• astah – UML editor (formerly known as “JUDE”)– With Mind Map, ERD– http://astah. net/– Runs on• PC, Mac, Linux, iPad
  7. 7. http://www.publickey1.jp/blog/11/10_innovation_sprint_2011.htmlInnovation Sprint 2011Jeff Sutherland Ikujiro Nonakame
  8. 8. Toyota ProductionSystemLeanLean SoftwareDevelopmentKanbanLean StartupAgileScrumXPThe New New ProductDevelopment GameFour stepsto the epiphanyAgile and LeanStartupPatternsManufacturing Industry in Japan2013 Yasunobu Kawaguchi
  9. 9. Copyright © 2005-2007 KenjiHIRANABE, Some rightsreserved9
  10. 10. 10
  11. 11. Exploring User Wishthrough Mind MappingKenji HIRANABEMind map by Michal Splho{Using for}
  12. 12. 12 Seeing is understanding.Seeing is understanding.Mind Map• Tony Buzan• Graphical note technique– And more than that• Visualize thoughts witha radiant structure
  13. 13. 13 Seeing is understanding.Seeing is understanding.da Vinci uses Pictures and Words at the same time
  14. 14. 15 Seeing is understanding.Seeing is understanding.“How it feels to have a stroke”Brain Scientist Jill Bolte Taylorhttp://www.youtube.com/watch?v=UyyjU8fzEYU
  15. 15. Mind map by Michal Splho
  16. 16. 17 Seeing is understanding.Seeing is understanding.
  17. 17. 18 Seeing is understanding.Seeing is understanding.Mind Mapping• Examples …
  18. 18. 19 Seeing is understanding.Seeing is understanding.Kent Beck’s XP 2nd
  19. 19. Product Feature Map in Release Planning
  20. 20. Seminar Ideas
  21. 21. Project Christmas Planning
  22. 22. Meeting Minutes Template
  23. 23. Guitar ChordDiagram
  24. 24. 25 Seeing is understanding.Seeing is understanding.“Mastering the Requirements” Process by Suzanne and James Robertson,1999.
  25. 25. 26 Seeing is understanding.Seeing is understanding.
  26. 26. 27 Seeing is understanding.Seeing is understanding.Mind Map1. Keyword Oriented2. Loose syntax and semantics3. Fast and Easy4. High level View5. Evocative6. Explore and Gather Ideas
  27. 27. 28 Seeing is understanding.Seeing is understanding.User Stores: Ron Jeffries’ 3 Cs• Card– Written on note cards.– Cards may be annotated with estimates, notes, etc.• Conversation– Details behind the story come out duringconversation with customer• Confirm– Acceptance tests confirm the story was codedcorrectly
  28. 28. 29 Seeing is understanding.Seeing is understanding.User Stories: Mike Cohn• Shift focus from writing to talking• Metaphor of Trawling (by Suzanne and JamesRobertson)– Requirements can be captured with different sizednets– Requirements change, mature, possibly die– Skill is a factor• Avoid “The user”, find “Roles”• In order to <benefit>,as a <role>,I want to <story>,
  29. 29. 30 Seeing is understanding.Seeing is understanding.Why Mind Map and User Stories Fit ?• Shift focus from writing to talking• Trawl requirements with coarse sized net first• Capture Emotion, Use your right brain !Colors, and Pictures !– To fully utilize broadband communication andpreserve it in your brain, as the same time, keep itinto a mind map as a memento of the situation. Inthe future conversation, you can use it to resumethe context back.
  30. 30. 31 Seeing is understanding.Seeing is understanding.User Wish Mind Map• The first step of getting what you want.• Get the Big Picture.• Who? first.• Semi-structured.• Gather info and mine UseCases/User Stories.
  31. 31. 32 Seeing is understanding.Seeing is understanding.Demonstration• City Library System Interview…
  32. 32. 33 Seeing is understanding.Seeing is understanding.Library Interview Mind Map
  33. 33. 34 Seeing is understanding.Seeing is understanding.UseCase Diagram
  34. 34. 35 Seeing is understanding.Seeing is understanding.User Stories Mind Map
  35. 35. 36 Seeing is understanding.Seeing is understanding.User Stories SpreadsheetAlso to PowerPoint!
  36. 36. 37 Seeing is understanding.Seeing is understanding.User WishUser WishBig Picture Mind MapBig Picture Mind MapUser Stories/ Use CasesUser Stories/ Use CasesWhy?Why?Who?Who?When?When?Estimate, Plan, Prioritize, TestvalueroleThe big picture of this presentation
  37. 37. 38 Seeing is understanding.Seeing is understanding.Conclusion• Mind Mapping is effective when– Gathering Information– Exploring topics freely• User interview with Mind Mapping– Is Semi-structured– Gives a high-level view of user wish– Creates a big picture of the user wish from whichyou can carve out good use cases or user stories.• Why, Who, When are good input to user stories.
  38. 38. 39 Seeing is understanding.Seeing is understanding.Stickyminds.com article“Agile Modeling with Mind Map and UML”Search: stickyminds Kenji HIRANABE
  39. 39. 40 Seeing is understanding.Seeing is understanding.
  40. 40. 41 Seeing is understanding.Seeing is understanding.Let’s make software developmentmore collaborative, productive and FUN!Free Evaluation of Astah from: http://astah.net/Follow me on twitter: @hiranabe, @astah_en
  41. 41. 42 Seeing is understanding.Seeing is understanding.ThankThank you for your attention!you for your attention!Requirements gathering is a critical and also slippery activity.Customer engagement and shared visualization is essential.
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×