Exploring User Wish through Mindmapping

Seeing is understanding.Seeing is understanding.

Exploring User Wish

through Mind Mapping

Kenji HIRANABEMind map by Michal Splhohttp://michalsplho.sk/?p=267

2 Seeing is understanding.Seeing is understanding.

Objectives

• To understand what is Mind Mapping and

how software development can benefit from it.

• To experience how to use Mind Maps to

explore user wish and carve out UseCases or

User Stories.

3 Seeing is understanding.Seeing is understanding.

Agenda

• Self-introduction

• What is a Mind Map and Why

• Exploring User Wish using Mind

Mapping

• Demonstration

• Conclusion

Father and Grandfather of Scrum

http://scrum.jeffsutherland.com/2011/02/meeting-nonaka-san-in-tokyo.html

7 Seeing is understanding.Seeing is understanding.

Kenji HIRANABE(1/2)• (co-)Translator of …

OO, UML books Mind Map book

XP/ Agile books

• (co-)Author of …C++ book

• 2008 Gordon Pask Award Recipient for Contributions to Agile practice

8 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/

9 Seeing is understanding.Seeing is understanding.

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 Ideas

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

Mind map by Michal Splhohttp://michalsplho.sk/?p=267

13 Seeing is understanding.Seeing is understanding.

14 Seeing is understanding.Seeing is understanding.

Mind Mapping

• Examples …

15 Seeing is understanding.Seeing is understanding.Kent Beck’s XP 2nd

Seminar Ideas

Project Christmas Planning

Meeting Minutes Template

Guitar Chord

Diagram

20 Seeing is understanding.Seeing is understanding.

Mastering the Requirements Process by Suzanne and James Robertson, 1999.

21 Seeing is understanding.Seeing is understanding.

22 Seeing is understanding.Seeing is understanding.

Ice Breaker

• Self-introduction Mind Map

• Central Image

– Your name and your Icon

• BOI’s may be, but not have to be;

– Why ? (you come here)

– What ? (do you do)

– Favorites

• Leave the other side of the card blank !

STEP 1:

23 Seeing is understanding.Seeing is understanding.

Ice Breaker

• Your Name and Icon

(again)

in the lower half

of the back side.

STEP 2:

24 Seeing is understanding.Seeing is understanding.

STEP 3:

25 Seeing is understanding.Seeing is understanding.

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 correctly

26 Seeing is understanding.Seeing is understanding.

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>.

27 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 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.

28 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.

29 Seeing is understanding.Seeing is understanding.

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)

30 Seeing is understanding.Seeing is understanding.

Library Interview Mind Map

31 Seeing is understanding.Seeing is understanding.

UseCase Diagram

32 Seeing is understanding.Seeing is understanding.

User Stories Mind Map

33 Seeing is understanding.Seeing is understanding.

User Stories Spreadsheet

Also to PowerPoint!

34 Seeing is understanding.Seeing is understanding.

User WishUser Wish

Big Picture Mind MapBig Picture Mind Map

User Stories/ Use CasesUser Stories/ Use Cases

Why?Why?

Who?Who?

When?When?

Estimate, Plan, Prioritize, Test

valuerole

The big picture of this presentation

35 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 which

you can carve out good use cases or user stories.

• Why, Who, When are good input to user stories.

36 Seeing is understanding.Seeing is understanding.

Stickyminds.com article“Agile Modeling with Mind Map and UML”

Search: stickyminds Kenji HIRANABE

37 Seeing is understanding.Seeing is understanding.

38 Seeing is understanding.Seeing is understanding.

Thank you, Agile New England!

• Make your software development

more collaborative, productive and

FUN!

• Whitepaper available.

http://astah.net/resources/documents/

zen-and-the-art-of-user-requirements.pdf

• Visit http://astah.net for the free version.