This document summarizes a presentation about lean DevOps practices. It discusses how companies can optimize for innovation through experimentation while balancing factors like cost, availability, scalability, speed, security, and developer happiness. The presentation outlines lessons learned, including that quality pays off by reducing technical debt, metrics are important, and competing priorities like speed and cost can conflict so teams must find the right balance. It concludes that lean approaches benefit companies and DevOps teams by encouraging innovation, but also add risk, so processes are needed to optimize across concerns like customer experience, infrastructure stability, and business outcomes.
19. What does that depend on?
● Developing velocity
● Impact
● Inversely correlated with probability of
being paged in the middle of the night
DevOps Happiness
36. Conclusions
● Both companies and devops teams benefit from
being lean
● Being lean adds instability and risk
● Devops need to measure and optimize across the different
dimensions of CASSSH
● Lean Devops can implement processes that optimize
CASSSH and encourage innovation