How sure are you that you are “building the right thing?” How often do you validate your assumptions versus simply measuring your progress? While agile methods often help organizations build products faster, many software teams get hyper-focused on points completed over real value delivered – or, more important, learning about customers and validating product ideas. Some people obsess over “backlog grooming,” but still produce weak stories that do not provide the context needed for teams and programs to deliver valuable products. Watch the webinar recording here: http://ow.ly/C5F09

1. Continuous Product Learning:
Story Maps, Customer Journeys and Tools for Validated Learning
Part 1
September 16, 2014
#AgileLIVE

2. © 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…

3. Continuous Product Learning
David Hussman - DevJam

4. First things first: Context Matters

5. What can we do (tomorrow)?
Where are we today?
How did we get here?

6. What can we do (tomorrow)?
Where are we today?
How did we get here?

7. Let’s start with a simple sketch

8. Delivery was a welcome change

9. Unless your delivering the wrong thing

10. Shifting to teams was good (again)

11. But not always (and not forever)

12. Shifting from how many hours …
… to how many pts was good

13. But more pts ≠ more value

14. Story telling was refreshing

15. Until it became sentence reading

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

17. Questions?
( about the past )

18. What can we do (tomorrow)?
Where are we today?
How did we get here?

19. More constant & frequent deliveries
But how much of what we deliver is wrong?

20. Creative visualizations are growing

21. Many groups have data …
… but fewer use it as evidence

22. Some people are moving to maps …
.. and Continuous Product Learning

23. Questions?
( about where we are today )

24. What can we do (tomorrow)?
Where are we today?
How did we get here?

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

26. If you were sure you could deliver, what would you change?

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

28. You might think investment over process
How much should you invest in discovery?

29. You might replace your backlog with …
… maps, examples / exploratory journeys

30. You might replace grooming with …
… a product design cadence

31. You might replace scaling process …
… with delivering products w/ teams

49. And there was much rejoicing?

50. Discovery is challenged and grows

52. Product design meets system thinking

53. Embrace change (again)
@davidhussman – www.devjam.com

54. Thank you
for joining us today!
#AgileLIVE