creating knowledge with users
DESCRIPTION
(1) Nonaka's Original Scrum and Knowledge Creation (2) Mindmapping for exploring User WishTRANSCRIPT
Seeing is understanding.Seeing is understanding.
Creating Knowledge
With Users
Change Vision, Inc.
Kenji Hiranabe
By Yasunobu Kawaguchi
Seeing is understanding.Seeing is understanding.
Seeing is understanding.Seeing is understanding.
SAP Waldorf
Seeing is understanding.Seeing is understanding.
Agenda
• Introduction
• Part I:–Nonaka’s Scrum: People As The
Conveyor of Knowledge
• Part II:–Exploring User Wish Through
Mindmapping
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
Scrum book
Agile and Scrum:
Collaborative Software
Development That Connects
Customers, Engineers and
Management
Seeing is understanding.Seeing is understanding.
Kenji HIRANABE(2/2)• CEO of Astah.net.
• astah – UML editor
– With Mind Map, ERD, SysML
– http://astah. net/
– Runs on• PC, Mac, Linux, iPad
Seeing is understanding.Seeing is understanding.
Part I
Nonaka’s ScrumPeople as the Conveyor of Knowledge
Change Vision, Inc.
Kenji Hiranabe
By Yasunobu Kawaguchi
Seeing is understanding.Seeing is understanding.
Scrum
Seeing is understanding.Seeing is understanding.
Seeing is understanding.Seeing is understanding.
Do you know where the word “Scrum”came from ?
http://www.publickey1.jp/blog/11/10_innovation_sprint_2011.html
Innovation Sprint 2011
Jeff Sutherland Ikujiro Nonaka
me
Quote from the first
Scrum Book
• “Agile Software Development with Scrum” (by
Ken Schwaber, Mike Beedle) starts with the
following quote.
The "relay race" approach to product development ... may conflict with the goals of maximum speed and flexibility. Instead a holistic or "rugby" approach – where the team tries to go the distance as a unit, passing the ball back and forth – may better serve today's competitive requirements.
-- “The New New Product Development Game”
Copyright © 2005-2007 Kenji
HIRANABE, Some rights
reserved
14
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
Prof. Ikujiro Nonaka
1
The New New Product Development Game(HBR)
ScrumStop the relay race, take up rugby
2
The Knowledge Creating Company
SECI-modelSpiral transformation of
Tacit knowledge and Explicit knowledge
3Managing Flow, The Wise Leadership(HBR)
PhronesisThe third knowledge type after
Science (explicit knowledge)
And art (tact knowledge)
U.S. Marine
Fractal
OrganizationSelf-similar structure
at all levels
4
Seeing is understanding.Seeing is understanding.
SECI model
Copyright Nonaka I. 2010Copyright Nonaka I. 2010
Two Types of Knowledge
Spiral up through Spiral up through dynamic interactiondynamic interaction
AnalogAnalog--Digital SynthesisDigital Synthesis
Objective and rational knowledge that can be expressed in words, sentences, numbers, or formulas (context-free)
Theoretical approachProblem solvingManualsDatabase
Subjective and experiential knowledge that can not be expressed in words, sentences, numbers, or Formulas (Context-specific)Cognitive Skills
beliefsimagesperspectivesmental models
Technical Skillscraftknow-how
Tacit Knowledge Explicit Knowledge
http://www.flickr.com/photos/visitabudhabi/6708954439/
Tacit
Knowledge
Subjective and
experiential
knowledge that
can not be
expressed in
words, sentences,
numbers, or
Formulas
(Context-specific)
• Explicit
Knowledge
• Objective and
rational
knowledge that
can be
expressed in
words,
sentences,
numbers, or
formulas
(context-free)http://www.flickr.com/photos/stuartpilbrow/4264302708/
“Sticky” Information
• Product developers need two types of information in order to succeed at their work: need and context-of-use information (generated by users) and generic solution information (often initially generated by manufacturers specializing in a particular type of solution) Bringing these two types of information together is not easy. Both need information and solution information are often very “sticky”—that is, costly to move from the site where the information was generated to other sites�.
• -- “Democratizing Innovation” (by Eric Von Hippel)
Copyright Nonaka I. 2010
SECI Model
Explicit
Explicit
Tacit
Tacit Tacit
Explicit
Explicit
Tacit
SocializationSocialization ExternalizationExternalization
InternalizationInternalization CombinationCombination
OG
E
I
Environment
Individual
I G
G
G
G
Org.
E
I
I
I
I
I
Group
IE O
Copyright Nonaka I. 2010
Copyright Nonaka I. 2010
Organizational Knowledge CreationSECI Model
Sharing and creating tacit knowledge through direct experience
I = Individual, G = Group, O = Organization, E = Environment
Learning and acquiring new tacit knowledge in practice
1. Perceiving reality
as it is
2. Sensing and
Empathizing with
others and the
environment
3. Transferring of
tacit knowledge
9. Embodying explicit
knowledge through
action and reflection
10. Using simulation and
experiments
Articulating tacit knowledge through dialogue and reflection
4. Articulating tacit
knowledge using
symbolic language
5. Translating tacit
knowledge into a
concept or prototype
Systemizing and applying explicit knowledge and information
6. Gathering and
integrating explicit
knowledge
7. Breaking down the
concept and finding
relationships among
the concepts
8. Editing and
systemizing explicit
knowledge
Explicit
Explicit
Tacit
Tacit Tacit
Explicit
Explicit
Tacit
SocializationSocialization ExternalizationExternalization
InternalizationInternalization CombinationCombination
OG
E
I
Environment
Individual
I G
G
G
G
Org.
E
I
I
I
I
I
Group
IE O
Seeing is understanding.Seeing is understanding.
A Story of
Matsushita Electric’s
“Home Bakery”(Bread Making Machine)
Source: http://panasonic.co.jp/ism/bakery/vol01/index.html
Ms. Ikuko TanakaCurrent Title: Senior Engineer at Living Environment Development CenterEver since she joined the company, she has involved in development of cooking software.“I have been studying cooking science, and I feel a calling in this job, that is development of cooking appliance software.”
In 1984, 3 divisions “Rice-Cooker Division”, “Heating Appliances Division”, “Rotation Division” were integrated into New “Cooking Appliances Division”.
Source: http://panasonic.co.jp/ism/bakery/vol01/index.html
Let me do it!
Copyright Nonaka I. 2010
First Internal AttemptFailed miserably. Crust was overcooked leaving the
dough inside raw.
Bread is very sensitive. Proper cooking time changes 1
hour if the temperature of the dough differs in 1°C
Compared machine-kneaded dough and professional
baker-kneaded dough using X rays.
→ But no meaningful data
She proposed an idea�
Let me work with
“him” as an apprentice!
Copyright Nonaka I. 2010
At Osaka International Hotel�Apprentice to the head baker
“A software engineer kneads dough and bakes bread, exploring what is the best set of conditions, and the hardware engineer make a prototype that clears the conditions. With that prototype the software engineer make another try, and… this process repeats like playing catch obsessively.”
I ate 5,000 piece of breadin those 3 years!
Copyright Nonaka I. 2010
“I was always watching the master to steal the way he kneaded the dough and tried it myself. He not only slaps but also “twists and stretches” the dough. When I found it, I went straight to the hardware engineer and talked about it.”
This “Twisting Stretch” is implemented (or transformed to explicit knowledge) as this Special Rib.
“The rotated dough is trapped by this rib and this effect realized the master’s hand movements.”
Copyright Nonaka I. 2010
Results�536,000 units in its first year.
�Exported to the United States, West Germany, and Hong Kong. Later to Sweden, Thailand, Australia, and New Zealand.
�1,000,000 units sold by the timecompetitors released their version.
�Users' voices to the engineers, fresh air to theCooking Appliances Division.
�Inspired other divisionsthroughout Matsushita.
Seeing is understanding.Seeing is understanding.
Design ThinkingRelationship with
Design Thinking
“Design thinking is a human-centered approach to innovation that draws
from the designer's toolkit to integrate the needs of people, the
possibilities of technology, and the requirements for business success.”
—Tim Brown, president and CEO
Seeing is understanding.Seeing is understanding.
IDEO Method Cards
There’s also an App !
Seeing is understanding.Seeing is understanding.
Seeing is understanding.Seeing is understanding.
Source: Tobias Hildenbrandhttp://de.slideshare.net/hildenbrand/keynote-alm-days-2012-combining-design-and-development
Socialization
• “Sharing and creating tacit knowledge through direct experience
• 1. Perceiving reality as it is
• 2. Sensing and empathizing with others
and the environment
• 3. Transferring of tacit knowledge”
Source: Tobias Hildenbrandhttp://de.slideshare.net/hildenbrand/keynote-alm-days-2012-combining-design-and-development
Seeing is understanding.Seeing is understanding.
ScrumBack to
SECI Model and Agile Practices
Explicit
Explicit
Tacit Tacit
Explicit
Explicit
Tacit
SocializationSocialization ExternalizationExternalization
InternalizationInternalization CombinationCombination
Sprint DemoSprint Demo
Visit UsersVisit UsersCoding StandardCoding StandardT
acit
Sprint PlanningSprint Planning
Story WritingStory Writing
Everything about
Learning�
Everything about
Learning�
Daily StandupDaily Standup
Sit TogetherSit Together
Pair ProgrammingPair Programming
RetrospectivesRetrospectives
SECI As Knowledge Creation Machine
E
E
T
T T
E
E
T
SS EE
II CCT
T
Created Knowledge
Knowledge about
How to create it
Knowledge about
User and Usage
Growing Working
Software
Learning Scrum
Team
Implemented as
1. Design Thinking
2. Agile
Product People
Copyright Nonaka I. 2010Copyright Nonaka I. 2009
Contemplation in Action:Indwelling in Actuality with Deep Thinking
“I can see many things
when I see a machine. How
can we maneuver through
that curve? We should do
this, we should do that....
Then I think about the next
machine. We can make a
faster machine if we think
like this, and so on. It’s a
natural progress into the
next step.”
- Soichiro Honda
Source: Honda Motor Corporation
(Picture at the Automobile Hall of Fame, Detroit)
Copyright Nonaka I. 2010
Copyright Nonaka I. 2010Copyright Nonaka I. 2010
Concept Building: Dialoguing on the Spot
Soichiro Honda
Drawing on
the floor
Words and
actionsBy articulating into
language, we
clearly understand
what we are
thinking
Source: Honda Motor Corporation
Automobile Hall of Fame (Detroit)
What’s the product owner ?
The person(s) who had the first belief, should run through the whole process
As the conveyer of knowledge.
Seeing is understanding.Seeing is understanding.
FEEL,BeforeyouTHINK!
Seeing is understanding.Seeing is understanding.
Part II
Exploring User Wish
Through Mindmapping
Change Vision, Inc.
Kenji Hiranabe
By Yasunobu Kawaguchi
Seeing is understanding.Seeing is understanding.
Exploring User Wish through
Mind Mapping
Kenji HIRANABE
Mind map by Michal Splho
Seeing is understanding.Seeing is understanding.
Agenda
• Introduction
• What is a Mind Map and Why
• Exploring User Wish using Mind
Mapping
• Demonstration
• Conclusion
Seeing is understanding.Seeing is understanding.
Mind Map
• Tony Buzan
• Graphical note technique
– And more than that
• Visualize thoughts with
a radiant structure
Seeing is understanding.Seeing is understanding.
IDEO Method Cards
Seeing is understanding.Seeing is understanding.
Affinity Diagrams
Seeing is understanding.Seeing is understanding.da Vinci uses Pictures and Words at the same time
Seeing is understanding.Seeing is understanding.
“How it feels to have a stroke”
Brain Scientist Jill Bolte Taylor
http://www.youtube.com/watch?v=UyyjU8fzEYU
Mind map by Michal Splho
Seeing is understanding.Seeing is understanding.
Seeing is understanding.Seeing is understanding.
Mind Mapping
• Examples �
Seeing is understanding.Seeing is understanding.Kent Beck’s XP 2nd
Seminar Ideas
Project Christmas Planning
Meeting Minutes Template
Guitar Chord
Diagram
Seeing is understanding.Seeing is understanding.
“Mastering the Requirements” Process by Suzanne and James Robertson,1999.
Seeing is understanding.Seeing is understanding.
Seeing is understanding.Seeing is understanding.
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
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
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>,
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.
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.
Seeing is understanding.Seeing is understanding.
Demonstration
• City Library System Interview�
Seeing is understanding.Seeing is understanding.
Library Interview Mind Map
Seeing is understanding.Seeing is understanding.
UseCase Diagram
Seeing is understanding.Seeing is understanding.
User Stories Mind Map
Seeing is understanding.Seeing is understanding.
User Stories Spreadsheet
Also to PowerPoint!
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
Seeing is understanding.Seeing is understanding.
Seeing is understanding.Seeing is understanding.
Stickyminds.com article“Agile Modeling with Mind Map and UML”
Search: stickyminds Kenji HIRANABE
Seeing is understanding.Seeing is understanding.
Seeing isUnderstanding