Post on 09-Jun-2015
description
Continuous Product Learning:
Story Maps, Customer Journeys and
Tools for Validated Learning
Part 1
September 16, 2014
#AgileLIVE
© 2014 VersionOne, Inc. 2
1. We’re recording today’s webinar.
2. We will be sending a link to the recording and slides.
3. You can claim 1 PDU credit:
Provider ID – 3576
Webinar ID – V1046
A few logistics…
Continuous Product Learning
David Hussman - DevJam
First things first: Context Matters
What can we do (tomorrow)?
Where are we today?
How did we get here?
What can we do (tomorrow)?
Where are we today?
How did we get here?
Let’s start with a simple sketch
Delivery was a welcome change
Unless your delivering the wrong thing
Shifting to teams was good (again)
But not always (and not forever)
Shifting from how many hours …
… to how many pts was good
But more pts ≠ more value
Story telling was refreshing
Until it became sentence reading
Automated builds and deploys
Automated unit and product testing
Retrospectives
And there is more things to appreciate …
Daily stands up / Scrum meetings
… and also to continuously question
Questions?
( about the past )
What can we do (tomorrow)?
Where are we today?
How did we get here?
More constant & frequent deliveries
But how much of what we deliver is wrong?
Creative visualizations are growing
Many groups have data …
… but fewer use it as evidence
Some people are moving to maps …
.. and Continuous Product Learning
Questions? ( about where we are today )
What can we do (tomorrow)?
Where are we today?
How did we get here?
Shift from more delivery to more learning
Product choices replace simple prioritization
Backlogs shift to maps based on examples
“Grooming” becomes product design cadence
Scale focuses on product learning
Continuous Product Learning
If you were sure you could deliver,
what would you change?
All Product Ideas
You might make braver choices
Product Choices
Collaborative Chartering
Pragmatic Personas
Story Maps
User Interviews
Market Research
Journeys
Product thinking over story prioritization
You might think investment over process
How much should you invest in discovery?
You might replace your backlog with …
… maps, examples / exploratory journeys
You might replace grooming with …
… a product design cadence
You might replace scaling process …
… with delivering products w/ teams
And there was much rejoicing?
Discovery is challenged and grows
Product design meets system thinking
Embrace change (again)
@davidhussman – www.devjam.com
Thank you
for joining us today!
#AgileLIVE