Passionate Product Ownership
Certified Scrum Product Owner
Course
Travel Weather Case Study
The Weather Channel
LeanUX West, 2013
Discovery
release cycle
development
cycle
wraps delivery
Delivery
Answers four
questions
1. Do people want
(to buy) it?
2. Can they use it?
3. Can we build it?
4. Do stakeholders
support it?
3
Pushes
decisions down
David Chao,
CTO Crimson
Too much to ask of
a person, or role
Requires a core (balanced) team to own the
product or feature area
1. Understand
the problem
2. Explore
Ideas
3. Refine
and
Validate
4. Create
a plan
Diverges and converges
Applies Design Thinking
Frame.
“Design by community is not
design by committee.”
-- Leisa ReicheltLeisa Reichelt
www.disambiguity.com
Leah Buley
www.adaptivepath.com/aboutus/leah.php
“Design isn’t something that
designers produce, design is a
process that designers
facilitate.”
--Leah Buley
Practices team collaboration over
organizational consensus
Helps solve wicked problems
Connects with the user
Targets user behavior
Sees the experience from the eyes of the user
* Narrative Journey Map
courtesy Duncan Brown of
the Caplin Group
Practices team-level user learning
Promotes failing (and learning) fast
F i n d s t h e b e s t
i d e a s i n t h e
s h o r t e s t a m o u n t
o f t i m e
Iterates fast and cheap towards good enough
Interacts with users two to three times a week
Keeps work visible
Discovery Balances Development

Continuous discovery improves continuous flow

Editor's Notes

  • #2 There’s some others like cynefin, martycagan and I’m sure whoever
  • #5 “I have six people on the new product introduction council and over 200 people in engineering” –Thank Jeff
  • #11 Fold that up, in the complex space where software lives and hindsight is 20/20, the problem and solution interact with each otherRequires that Deming cycle gets going. More than once. Exploit the innovation loop by shoving into chaos
  • #13 Collects qualitative (and quantitative) information
  • #14 5 minutes
  • #18 Increase options and delay decisions