The Operating Chasm

Slides from my keynote at CD Summit Seattle

Transcript

1. The Operating Chasm Transforming into a CD organization @gmiranda23 George Miranda Director of Product Marketing Chef Software, Inc.
2. @gmiranda23
3. TIME QUALITY COST @gmiranda23
4. VELOCITY QUALITY @gmiranda23
5. @gmiranda23
6. Low Performing Medium Performing High Performing Throughput (how often you deploy to production) Between once per month and once every 6 months On demand (multiple deploys per day) Lead times (from commit to deployment in production) Between one month and 6 months Less than one hour Change failure rates 16%-30% 0%-15% MTTR (service outage recovery times) Less than one day Less than one hour @gmiranda23
7. Low Performing Medium Performing High Performing Throughput (how often you deploy to production) Between once per month and once every 6 months Between once per week and once per month On demand (multiple deploys per day) Lead times (from commit to deployment in production) Between one month and 6 months Between one week and one month Less than one hour Change failure rates 16%-30% 31-45% 0%-15% MTTR (service outage recovery times) Less than one day* Less than one day Less than one hour @gmiranda23
8. Low Performing Medium Performing High Performing Change failure rates 16%-30% 31-45% 0%-15% MTTR (service outage recovery times) Less than one day* Less than one day Less than one hour Time spent on new work 38% 34% 49% Time spent doing rework 27% 32% 21% @gmiranda23
9. Low Innovation Low Scale Low Speed Low Customer Value High Innovation High Scale High Speed High Customer Value Operating Chasm @gmiranda23
10. @gmiranda23
11. Effective test data management @gmiranda23
12. Comprehensive, fast, and reliable test and deployment automation @gmiranda23
13. @gmiranda23
14. Application code and app & system configuration all in version control @gmiranda23
15. [ code ] @gmiranda23
16. Trunk-based development and continuous integration @gmiranda23
18. Incorporating security into the delivery process @gmiranda23
19. compliance as [ code ] @gmiranda23
21. "You can't change culture, but you can change tools. Certain tools enforce behaviors and those behaviors become your culture." @gmiranda23
22. In Review • Invest the time to manage your test data effectively • Comprehensive, fast, and reliable test automation • Apps are code, infrastructure is code, all code is in version control • Adopt trunk-based development and promote tiny deltas • Change your culture by proliferating everything as code @gmiranda23
23. Thank you! @gmiranda23 george@chef.io