Exploring User Wish through Mindmapping at Agile India 2013

Seeing is understanding.Seeing is understanding.

Exploring User Wish

through Mind Mapping

Kenji HIRANABE, Astah.netMind map by Michal Splho

2 Seeing is understanding.Seeing is understanding.

Agenda

• Introduction + Agile in Japan

• What is a Mind Map and Why

• Exploring User Wish using Mind

Mapping

• Demonstration

• Conclusion


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

OO, UML books Mind Map book

XP/ Agile books

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

Scrum book

Agile and Scrum:

Collaborative Software

Development That Connects

Customers, Engineers and

Management


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

http://www.publickey1.jp/blog/11/10_innovation_sprint_2011.html

Innovation Sprint 2011

Jeff Sutherland Ikujiro Nonaka

me

Toyota Production System

Lean

Lean Software Development

Kanban

Lean Startup

Agile

Scrum

XP

The New New Product Development Game

Four steps to the epiphany

Agile and Lean

Startup

Patterns

Manufacturing Industry in Japan

2013 Yasunobu Kawaguchi

Copyright © 2005-2007 Kenji

HIRANABE, Some rights

reserved

7

8

9

Nonaka’s Text Agile/Scrum (Software)

1993 Org. Patterns(by Jim Coplien) (at PLoP)

2001 “Agile Software Development with Scrum”

(by Ken Schwaber, Mike Beedle)

“The Knowledge Creating Company”(HBR) 1991

SECI-model

アメリカ海兵隊(U.S. Marine) 1995Fractal

Organization

1994/1 First Sprint of Scrum by Jeff Sutherland

Scrum Master

1994/2 Second Sprint of Scrum (with Cope’s Ideas)

Daily Scrum

“The New New Product Development Game” 1986

“Scrum”

2012 “Software in 30 days”

“Wise Leadership”(HBR) 2010

Phronetic

Leadership

“Managing Flow” 2008

2001 “The Agile Manifesto”

2013“アジャイル開発とスクラム-顧客・技術・経営をつなぐ協調的ソフトウェエア開発”

Collaborative Software Development That Connects Customers, Engineers, and Management

“Agile” google trends

http://www.google.com/trends/explore#q=Agile%20-chevrolet%20-ltz%20-novo%20-carro%20-gm%20-messenger&cmpt=q

India

USA

UK

Brazil

Japan


Scrum Masters

# of CSM and CSPO by countries(2012/3 + India 2013/2)

US UK China Denmark Brazil Japan India

10,000

300100

(Data Source: IPA report http://sec.ipa.go.jp/reports/20120611.html and

data from Renee Mzyk at Scrum Alliance)

Seeing is understanding.Seeing is understanding.

Exploring User Wish

through Mind Mapping

Kenji HIRANABE, Astah.netMind map by Michal Splho


Mind Map

• Tony Buzan

• Graphical note technique

– And more than that

• Visualize thoughts with

a radiant structure

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


“How it feels to have a stroke”

Brain Scientist Jill Bolte Taylor

http://www.youtube.com/watch?v=UyyjU8fzEYU

Mind map by Michal Splho



Mind Mapping

• Examples …

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

Product Feature Map in Release Planning

Seminar Ideas

23 Seeing is understanding.Seeing is understanding.Thanks! Bruce Taylor

Project Christmas Planning

Meeting Minutes Template

Guitar Chord

Diagram


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


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


Ice Breaker

• 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 !

STEP 1:


Ice Breaker

• Your Name and Icon

(again)

in the lower half

of the back side.

STEP 2:


STEP 3:



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


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


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.


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.


Demonstration

• City Library System Interview…


Library Interview Mind Map


UseCase Diagram


User Stories Mind Map


User Stories Spreadsheet

Also to PowerPoint!


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


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.


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

Search: stickyminds Kenji HIRANABE



Thank you !

• Make your software development more

collaborative, productive and FUN!

For Mindmap + UML tool, visit our site:

http://astah.net

Technology

Exploring User Wish through Mindmapping at Agile India 2013