Lean DevOps

DevOps is all about automation and moving issues closer to the source. Whether you're a developer, database admin/engineer, or in operations, your team can benefit from adopting a DevOps mentality. DevOps adopts many of it's practices from Lean Manufacturing. This session will help you identify the Value Stream and how the three primary principles of DevOps can make your team better and faster.

Transcript

1. LEAN DEVOPS Craig Berntson
2. EGO STUFF AUTHOR Continuous Integration in .NET Manning Publishing MICROSOFT MVP 22+ years, currently for Developer Tools .NET/DEVOPS ARCHITECT TECHNICAL SPEAKER 20+ years as international speaker AUTHOR Software Gardening column DNC Magazine
3. Agile Lean DevOps Three Principles Building Culture
5. Fixed Estimated
8. Lean is all about eliminating waste A systematic method for the elimination of waste - Wikipedia
9. Lead Time Story Created Work Started Work Completed Process Time Waiting for Delivery
10. Step 1 •Task 1A •Task 1B •Task 1C Step 2 •Task 2A •Task 2B Step 3 •Task 3A •Task 3B •Task 3C •Task 3D
12. Our technology value stream is the process required to convert a business hypothesis into a technology-enabled service that delivers value to the customer. - The DevOps Handbook
14. Development Operations
17. Principles of Feedback 1 2 3 Principles of Flow Principles of Continual Learning & Experimentation
18. 1 Flow
20. Backlog In Progress (WIP Limit=2) In Test In Beta In Production (Done)
21. Continuous Integration Continuous Deployment Continuous Delivery
22. Code/Scripts Manual Work Automated Tests Continuous Integration Quality Gate CI/Virtual Servers Automated and Manual Tests Quality Gate Promote to Test Test Automated and Manual Tests Quality Gate Promote to Beta Beta Promote to Prod Prod
24. PRINCIPLES OF FLOW • Make our work visible • Limit work in process • Reduce batch sizes • Continually identify and elevate constraints • Eliminate hardships and waste in the value stream
25. TECHNICAL PRACTICES OF FLOW • Create the foundations of our deployment pipeline • Enable fast and reliable automated testing • Enable and practice continuous integration • Automate and enable low-risk releases • Architect for low-risk releases
26. 2 Feedback
27. PRINCIPLES OF FEEDBACK • Working safely with complex systems • See problems as they occur • Swarm and solve problems to build new knowledge • Keep pushing quality closer to the source • Enable optimizing for downstream work centers
28. TECHNICAL PRACTICES OF FEEDBACK • Telemetry on all the things • Telemetry analysis • Alerting • Push data collection to the left • Build results • Static code analysis • Code security analysis • Testing results
29. 3 Continuous Learning & Experimentation
30. PRINCIPLES OF CONTINUOUS LEARNING & EXPERIMENTATION • Enable organizational learning and quality culture • Institutionalize the improvement of daily work • Transform local discoveries into global improvements • Inject resilience patterns into our daily work • Leaders reinforce a learning culture
31. TECHNICAL PRACTICES OF CONTINUOUS LEARNING & EXPERIMENTATION • Lessons Learned meetings close to issue date • Culture of quality, testing, & monitoring • Identify and refine failure signals • Inject production failures to enable resilience and learning
33. Always raising our level of awareness
34. Responding with a sense of urgency is the ante to play
35. Obsessed with finding a better way
36. It’s not about WHO is right, it’s about WHAT is right
37. Simplicity is genius
38. Innovation is rewarded. Execution is genius.
39. Do the right thing
43. DevOps is a journey, not a destination
44. CONTACT / QUESTIONS craigberntson@quickenloans.com @craigber www.dotnetcurry.com www.speakerdeck.com/craigber