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.

1. Exploring User Wish
through Mind Mapping
Mind map by Michal Splho Kenji HIRANABE, Astah.net
Seeing is understanding.

2. Agenda
• Introduction + Agile in Japan
• What is a Mind Map and Why
• Exploring User Wish using Mind
Mapping
• Demonstration
• Conclusion
2 Seeing is understanding.

3. Kenji HIRANABE(1/2)
• (co-)Translator of …
Agile and Scrum:
Collaborative Software
C++ book XP/ Agile books Development That Connects
• (co-)Author of … Customers, Engineers and
Management
OO, UML books Mind Map book Scrum book
3 Seeing is understanding.

4. 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
4 Seeing is understanding.

5. Innovation Sprint 2011
me
Jeff Sutherland Ikujiro Nonaka
http://www.publickey1.jp/blog/11/10_innovation_sprint_2011.html

6. Agile and Lean
Patterns
The New New Product
Development Game
Manufacturing Industry in Japan
XP
Toyota Production Scrum
System
Lean Software
Development Agile
Lean Kanban
Lean Startup
Four steps
2013 Yasunobu Kawaguchi
Startup to the epiphany

7. Copyright © 2005-2007 Kenji 7
HIRANABE, Some rights
reserved

8. 8

9. Nonaka’s Text Agile/Scrum (Software)
“The New New Product Development Game” 1986
“Scrum”
“The Knowledge Creating Company”(HBR) 1991
1993 Org. Patterns(by Jim Coplien) (at PLoP)
SECI-model
1994/1 First Sprint of Scrum by Jeff Sutherland
1994/2 Second Sprint of Scrum (with Cope’s Ideas)
Fractal Scrum Master Daily Scrum
Organization アメリカ海兵隊(U.S. Marine) 1995
2001 “Agile Software Development with Scrum”
(by Ken Schwaber, Mike Beedle)
2001 “The Agile Manifesto”
Phronetic “Managing Flow” 2008
Leadership “Wise Leadership”(HBR) 2010
2012 “Software in 30 days”
2013
“アジャイル開発とスクラム-顧客・技術・経営をつなぐ協調的ソフトウェエア開発”
9
Collaborative Software Development That Connects Customers, Engineers, and Management

10. “Agile” google trends
India
Brazil
USA
UK
Japan
http://www.google.com/trends/explore#q=Agile%20-chevrolet%20-ltz%20-novo%20-carro%20-gm%20-messenger&cmpt=q

11. Scrum Masters
100
300
10,000
US UK China Denmark Brazil Japan India
# of CSM and CSPO by countries(2012/3 + India 2013/2)
(Data Source: IPA report http://sec.ipa.go.jp/reports/20120611.html and
data from Renee Mzyk at Scrum Alliance)
11 Seeing is understanding.

12. Exploring User Wish
through Mind Mapping
Mind map by Michal Splho Kenji HIRANABE, Astah.net
Seeing is understanding.

13. Mind Map
• Tony Buzan
• Graphical note technique
– And more than that
• Visualize thoughts with
a radiant structure
13 Seeing is understanding.

14. 14 Seeing is understanding.
da Vinci uses Pictures and Words at the same time

16. “How it feels to have a stroke”
Brain Scientist Jill Bolte Taylor
16 Seeing is understanding.
http://www.youtube.com/watch?v=UyyjU8fzEYU

17. Mind map by Michal Splho

18. 18 Seeing is understanding.

19. Mind Mapping
• Examples …
19 Seeing is understanding.

20. 20 Seeing isKent Beck’s XP 2nd
understanding.

21. Product Feature Map in Release Planning

22. Seminar Ideas

23. 23 Seeing is understanding.
Thanks! Bruce Taylor

24. Project Christmas Planning

25. Meeting Minutes Template

26. Guitar Chord
Diagram

27. “Mastering the Requirements” Process by Suzanne and James Robertson,1999.
27 Seeing is understanding.

28. Mind Map
1. Keyword Oriented
2. Loose syntax and semantics
3. Fast and Easy
4. High level View
5. Evocative
6. Explore and Gather Ideas
28 Seeing is understanding.

29. Ice Breaker
STEP 1:
• Self-introduction Mind Map
• Central Image
– Your name and your Icon
• BOI’s may be,
but not have to be;
– Why ?
– Who ?
– Favorites
• Leave the other side of the card blank !
29 Seeing is understanding.

30. Ice Breaker
STEP 2:
• Your Name and Icon
(again)
in the lower half
of the back side.
30 Seeing is understanding.

31. STEP 3:
31 Seeing is understanding.

32. 32 Seeing is understanding.

33. 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 during
conversation with customer
• Confirm
– Acceptance tests confirm the story was coded
correctly
33 Seeing is understanding.

34. 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 <benefit>,
as a <role>,
I want to <story>,
34 Seeing is understanding.

35. 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.
35 Seeing is understanding.

36. 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.
36 Seeing is understanding.

37. Demonstration
• City Library System Interview…
37 Seeing is understanding.

38. Library Interview Mind Map
38 Seeing is understanding.

39. UseCase Diagram
39 Seeing is understanding.

40. User Stories Mind Map
40 Seeing is understanding.

41. User Stories Spreadsheet
41 Also to PowerPoint! Seeing is understanding.

42. The big picture of this presentation
User Wish
User Wish
Why?
Why?
Big Picture Mind Map Who?
Who?
Big Picture Mind Map
value
role
When?
When?
User Stories/ Use Cases
User Stories/ Use Cases
Estimate, Plan, Prioritize, Test
42 Seeing is understanding.

43. 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.
43 Seeing is understanding.

44. Stickyminds.com article
“Agile Modeling with Mind Map and UML”
Search: stickyminds Kenji HIRANABE
44 Seeing is understanding.

45. 45 Seeing is understanding.

46. Thank you !
• Make your software development more
collaborative, productive and FUN!
For Mindmap + UML tool, visit our site:
http://astah.net
46 Seeing is understanding.