DevOps – It’s all about experiments

‚The Phoenix Project‘ is a must read for all DevOps practitioners. It describes the main principles of DevOps culture as ‚three ways‘. The third way is about creating a culture of continual experimentation. I’ll take you on a journey through Agile and DevOps, product development and organizational development. We’ll discover all the small places in this culture where the principle of experimentation is hidden. Some of them may surprise you.

Transcript

1. DevOps It’s all about experiments Konstantin Diener | cosee GmbH konstantin.diener@cosee.biz | @onkelkodi
2. KONSTANTIN DIENER CTO and Founder of cosee
3. The Phoenix Project Gene Kim, Kevin Behr, George Spafford
4. „The Third Way is about creating a culture that fosters two things: continual experimentation, which requires taking risks and learning from success and failure, and understanding that repetition and practice is the prerequisite to mastery. The Phoenix Project
5. But why experiments?
7. Outcome over Output
9. Product Development
10. User Story Mapping Jeff Patton
11. Jeff Patton, User Story Mapping, https://jpattonassociates.com/
12. Do you always have the right ideas?
13. No!
14. 60% - 90% of ideas do not have a positive impact …
15. … based on experiments at Microsoft
16. But …
17. If our product is based on hypotheses, …
18. … our User Stories can’t be requirements!
19. User Story = Hypothesis + Experiment
21. Experimenting means Measuring
23. Measure outcomes in production
24. Continuous Delivery
25. Business Metrics
26. small experiments hard job
27. Lean Experimentation in Action Kylie Castellaw, Maryam Aidini
29. Organizational Development
30. Experimentation and risk taking are what enable us to relentlessly improve our system of work, which often requires us to do things very differently than how we’ve done it for decades. The Phoenix Project
33. Best Practices
34. Kent Beck Spotify didn’t implement the Spotify model by copying Spotify. Why do folks at other companies think they can implement the Spotify model by copying Spotify? “
36. Is there a problem for our solution?
38. Goal to problem is connected to Hypothesis <Problem> Experiment - What’s the minimum we could try to proof our hypothesis? • Measurement 1 • Measurement 2
39. How to gather topics for your Org task board?
40. Retrospectives
41. Person Team Organisation • 1 on 1 • Jour Fixe • Personal Retrospective • Sprint Retro • Release Retro • Postmortem
42. Successful cross-functional teams Goal Missing cross cutting link for „developer species“ Hypothesis Backend Developers felt disconnected from each other Try Community of Practice for Backend Developers Experiment • each Developer knows at least two peers he can ask for help. How to measure
43. Scaling Lean & Agile Development Craig Larman, Bas Vodde
44. Try … … Cultivating Communities of Practice … Use CoPs for functional learning
45. Disclaimer on experiments
47. Ester Derby Ppl seem to think about adding processes, policies, procedures… but not retiring any of them. Sort of like always buying new clothes, without ever clearing out the closet of stuff that now longer works or fits. “
48. Dispose experiments!
49. If your journey is an easy one, it is a trap. @KNeferhetep
50. Konstantin Diener | cosee GmbH konstantin.diener@cosee.biz | @onkelkodi Technologieentscheidungen in selbstorganisierten Teams Mittwoch, 15:00 - 16:00 | Gutenberg-Saal 4 > blog.cosee.biz > cosee.jobs Picture credits: Kata: http://www.istockphoto.com/portfolio/PointImages Project Plan: https://www.istockphoto.com/de/portfolio/kemaltaner Armchair: https://www.istockphoto.com/de/portfolio/FilippoBacci Cat & Mouse: https://www.istockphoto.com/de/portfolio/bllkcbs >> https://cosee.biz