This document discusses concepts related to agile product development and continuous learning. It explores comparing different processes and products to learn from them. It advocates applying lean startup principles like minimum viable products, measuring progress through customer feedback, and pivoting when needed. The document also discusses complexity in environments and how simplicity can help through approaches like checklists. Overall, it promotes questioning practices to ensure they align with intentions and creating value.

1. 9/17/2010
Products
Action
over
Process
Mechanics
Products and People
over
Process and Dogma
Choose a few words to How do those words
describe your process help your product?
What’s your story?
1

2. 9/17/2010
Learning by Comparing
Brown M and Ms Heart Surgery
Why compare these?
2

3. 9/17/2010
B-17 Rialto Restaurant
Or these?
Simple - Complicated - Complex
3

4. 9/17/2010
Complex Adaptive Systems
Dave Snowden
Complexities We Face
Agility and Complexity
Creating Community (Common Vision)
Form Communities (Chartering)
Composing Product (Personas - Story maps - Sketching)
Create an Eco-System (Iteration 0 - Common Workspace)
Discovery (Planning)
Product Releases (Value - Effort - Dependencies)
Iterative Delivery (Iterative (cycles) - Kanban (flow))
Delivery (Iterating)
Staying Connected (Daily Standup - Common Workspace)
Tracking Progress (Task Walls - Burncharts - Velocity)
Technical Agility (Continuous Integration - Test Driven)
Delivering Value (Acceptance Tests - Continuous Deploy)
Learning (Tuning)
Validating Progress (Reviews - User Testing)
Reflect and Improve (Retrospective – Market Feedback)
4

5. 9/17/2010
Continuous ( Product ) Learning
Discovery Delivery
What and Why How and When
“Pivot”
How well do you promote
product learning or “pivots”?
User Centered Delivery
Rethinking Development
( lean start up movement )
5

6. 9/17/2010
Intentional Investments
Imagine your project is a start up?
How would your approach differ?
Where would you invest your money?
process (how) vs. product (why)
Build – Measure - Learn
Customer Development
A “Customer Checklist”
6

7. 9/17/2010
So what about brown M & Ms?
The Story of Brown M & Ms
( complexity calls for simplicity )
Atul Gawande
Simple Process / Complex Environments
(author Checklist Manifesto)
Wendy Freedman
(on the laws of gravity )
V = GT F = MG
“Gravity is just a theory … there is always testing.”
7

8. 9/17/2010
Common Laws in Action
George Ohm’s
Ohm Law
What are the laws for agility?
Dude’s Law
8

9. 9/17/2010
Discussions around ”are we doing Agile?”
“Why are we doing what we are doing?”
{ Meaning = Intent / Action }
{ Worth = Purpose / Practice }
Dude’s Law: Value = Why / How
Questions?
W W
V= H V= H
Share, Compare, Learn
________________________________________
Coaching and Developing Agility
david.hussman@devjam.com
www.devjam.com
© 2010 DevJam - All rights reserved.
9