build-lists: true footer: PagerDuty slidenumbers: true
"To have a shared common understanding of Lean Software Development, and a shared vocabulary for discussing how it applies to PagerDuty."
- Decide what we want to improve
- Make an introductory presentation
- Note what could be better
Lather, rinse, repeat until "done."
^ "Our process"
- Decide what we want to improve: "Think"
- Make an introductory presentation: "Make"
- Note what could be better: "Check"
^ "The simplest possible lean"
^ How can this be the simplest?
- We're "done" when we have some better/higher use of our time...
- In other words: We're done when we have a higher priority.
Our priorities now will be the same when we're done with Make
^ Our priorities change as time passes
- Our customers advance their understanding of our products
- We engineers advance our understanding of our code
- Our competitors shift the product landscape
- Our management team advances its understanding of how to win
- Have one thought at a time.
- Build one thing at a time.
- Check one thing at a time.
Delay decisions as long as possible
Build the simplest thing that could possibly work
Make it easy to throw away, not easy to change
Small, isolated changes are the easiest to measure
^ Summary
^ http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp
^ Henrik Kniberg
