Seeing is understanding.Seeing is understanding.

Exploring User Storiesthrough Mind Mapping

Kenji HIRANABE

Change Vision, Inc.

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

3 Seeing is understanding.Seeing is understanding.

Agenda

• Introduction• What is a Mind Map and Why• How Software Development Benefits from

Using Mind Maps• Exploring User Wish using Mind Mapping• Demonstration• Let’s try !• Conclusion

4 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

5 Seeing is understanding.Seeing is understanding.

Kenji HIRANABE(2/2)• CEO of Change Vision, Inc.

• JUDE – UML editor– With Mind Map, ERD

– http://jude.change-vision.com/

• TRICHORD – Agile Project Kanban Board– Kanban, Parking Lot,

– http://trichord.change-vision.com/

– Burndowns, Smiley Calendar

6 Seeing is understanding.Seeing is understanding.

Agile2008

• I’ll talked about …

• Learning Kaizen from Toyota [with Mind Maps]

• New Car Development in Toyota

• Exploring User Stories through Mind Mapping

• Dear XP – song at the party

7 Seeing is understanding.Seeing is understanding.

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

Search: stickyminds Kenji HIRANABE

8 Seeing is understanding.Seeing is understanding.

Mind Map

• Tony Buzan• Graphical note technique• Visualize thoughts with

a radiant structure – Keyword Oriented– Loose syntax and semantics– Fast and Easy– High level View– Evocative– Explore and Gather Ideas

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

10 Seeing is understanding.Seeing is understanding.

Mind Mapping

• Examples …

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

Retrospectives using Keep/Problem/Try format

Product Feature Map in Release Planning

Seminar Ideas

Project Christmas Planning

Meeting Minutes Template

Design Patterns

18 Seeing is understanding.Seeing is understanding.Mastering the Requirements Process by Suzanne and James Robertson, 1999.

19 Seeing is understanding.Seeing is understanding.

Self-Introduction Mind Map

• Central Image– Your name and your Icon– What describes you most

• BOI’s may be, – Why (you came to Tronto)?– What (do you do) ?– Favorites (sessions so far)

• 3-minute introduction in pairs

20 Seeing is understanding.Seeing is understanding.

21 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 during

conversation with customer

• Confirm– Acceptance tests confirm the story was coded

correctly

22 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>,

23 Seeing is understanding.Seeing is understanding.Mastering the Requirements Process by Suzanne and James Robertson, 1999.

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

25 Seeing is understanding.Seeing is understanding.

Demonstration

• City Library System Interview…

26 Seeing is understanding.Seeing is understanding.

Library Interview Mind Map

27 Seeing is understanding.Seeing is understanding.

UseCase Diagram

28 Seeing is understanding.Seeing is understanding.

User Stories Mind Map

29 Seeing is understanding.Seeing is understanding.

User WishUser Wish

Big Picture Mind MapBig Picture Mind Map

User StoriesUser Stories

Why?Why?

Who?Who?

When?When?

Estimate, Plan, Prioritize, Test

valuerole

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

31 Seeing is understanding.Seeing is understanding.

The mind map tool• JUDE – UML editor

– With Mind Map, ERD, DFD– http://jude.change-vision.com/

32 Seeing is understanding.Seeing is understanding.

User Stories Spreadsheet

Also to PowerPoint!