Click here to load reader

Exploring User Wish through Mindmapping

  • View
    6.627

  • Download
    1

Embed Size (px)

DESCRIPTION

Using Mindmapping to explore user with and find use cases, or user stories.

Text of Exploring User Wish through Mindmapping

  • 1.Exploring User Wish through Mind MappingMind map by Michal Splhohttp://michalsplho.sk/?p=267 Kenji HIRANABE Seeing is understanding.

2. Objectives To understand what is Mind Mapping andhow software development can benefit from it. To experience how to use Mind Maps toexplore user wish and carve out UseCases orUser Stories.2 Seeing is understanding. 3. Agenda Self-introduction What is a Mind Map and Why Exploring User Wish using MindMapping Demonstration Conclusion3Seeing is understanding. 4. Father and Grandfather of Scrumhttp://scrum.jeffsutherland.com/2011/02/meeting-nonaka-san-in-tokyo.html 5. Kenji HIRANABE(1/2) (co-)Translator of C++ bookXP/ Agile books (co-)Author of OO, UML booksMind Map book 2008 Gordon Pask Award Recipient for Contributions to Agile practice7 Seeing is understanding. 6. Kenji HIRANABE(2/2) CEO of Astah.net. astah UML editor (formerly known as JUDE) With Mind Map, ERD http://astah. net/8 Seeing is understanding. 7. Mind Map Tony Buzan Graphical note technique Visualize thoughts witha radiant structure Keyword Oriented Loose syntax and semantics Fast and Easy High level View Evocative Explore and Gather Ideas9 Seeing is understanding. 8. 10 Seeing is understanding. da Vinci uses Pictures and Words at the same time 9. Mind map by Michal Splhohttp://michalsplho.sk/?p=267 10. 13 Seeing is understanding. 11. Mind Mapping Examples 14Seeing is understanding. 12. 15 Seeing isKent Becks XP 2nd understanding. 13. Seminar Ideas 14. Project Christmas Planning 15. Meeting Minutes Template 16. Guitar ChordDiagram 17. Mastering the Requirements Process by Suzanne and James Robertson, 1999.20Seeing is understanding. 18. 21 Seeing is understanding. 19. Ice Breaker STEP 1: Self-introduction Mind Map Central Image Your name and your Icon BOIs may be,but not have to be; Why ? (you come here) What ? (do you do) Favorites Leave the other side of the card blank !22Seeing is understanding. 20. Ice Breaker STEP 2: Your Name and Icon(again)in the lower halfof the back side.23Seeing is understanding. 21. STEP 3:24 Seeing is understanding. 22. User Stories: Ron Jeffries 3 Cs Card Written on note cards. Cards may be annotated with estimates, notes, etc. Conversation Details behind the story come out during conversation with customer Confirm Acceptance tests confirm the story was coded correctly25Seeing is understanding. 23. User Stories: Mike Cohn Shift focus from writing to talking Metaphor of Trawling (by Suzanne and James Robertson) Requirements can be captured with different sized nets Requirements change, mature, possibly die Skill is a factor Avoid The user, find Roles In order to , as a , I want to .26Seeing is understanding. 24. 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 and preserve it in your brain, as the same time, keep it into a mind map as a memento of the situation. In the future conversation, you can use it to resume the context back.27 Seeing is understanding. 25. 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.28 Seeing is understanding. 26. Demonstration City Library System Interview I will visit my client at a city library And Using mindmapping, I interview to gather user wish. Bit goes like (have fun)29Seeing is understanding. 27. Library Interview Mind Map30Seeing is understanding. 28. UseCase Diagram31Seeing is understanding. 29. User Stories Mind Map32Seeing is understanding. 30. User Stories Spreadsheet33 Also to PowerPoint! Seeing is understanding. 31. The big picture of this presentation User Wish User Wish Why? Why? Big Picture Mind MapWho? Who?Big Picture Mind Mapvalue roleWhen?When? User Stories/ Use Cases User Stories/ Use Cases Estimate, Plan, Prioritize, Test34Seeing is understanding. 32. 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 which you can carve out good use cases or user stories. Why, Who, When are good input to user stories.35Seeing is understanding. 33. Stickyminds.com article Agile Modeling with Mind Map and UMLSearch: stickyminds Kenji HIRANABE36 Seeing is understanding. 34. 37 Seeing is understanding. 35. Thank you, Agile New England! Make your software developmentmore collaborative, productive andFUN! Whitepaper available.http://astah.net/resources/documents/zen-and-the-art-of-user-requirements.pdf Visit http://astah.net for the free version.38Seeing is understanding.