Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

What does devops culture mean for engineers

206 views

Published on

These are the slides from my paper at VoxxedDays Singapore 2018 on DevOps culture. The video is at: https://www.youtube.com/watch?v=oHhnq-3Q66U

Published in: Technology
  • Be the first to comment

What does devops culture mean for engineers

  1. 1. The Way We Work What does DevOps Culture mean for engineers? @dwmkerr Dave Kerr McKinsey & Company
  2. 2. Who am I? @dwmkerr
  3. 3. I am a technology consultant. @dwmkerr
  4. 4. What am I going to talk about? @dwmkerr
  5. 5. DevOps & Culture …and why does this matter to me? @dwmkerr
  6. 6. What’s the problem that DevOps is trying to solve? @dwmkerr
  7. 7. Situation We’ve got better at building and we make more changes @dwmkerr
  8. 8. “Bridge Builder”, 2000, Alex Austin @dwmkerr
  9. 9. Classical Architecture & Engineering Static requirements Well known strategies Plan well – change is expensive Detailed Roadmap Effective management & planning @dwmkerr
  10. 10. “Sim City 2000”, Maxis @dwmkerr
  11. 11. Dynamic requirements Test and learn Be flexible – change is inevitable Progressive Refinement Effective engineering & change control Evolutionary Architecture & Engineering @dwmkerr
  12. 12. Dynamic requirements Test and learn Be flexible – change is inevitable Progressive Refinement Effective engineering & change control Classical Architecture & Engineering Evolutionary Architecture & Engineering Static requirements Well known strategies Plan well – change is expensive Detailed Roadmap Effective management & planning @dwmkerr
  13. 13. Complicated Complex @dwmkerr
  14. 14. To deal with complexity, we need make changes. (and we’ve got good at doing that!) @dwmkerr
  15. 15. Build Faster @dwmkerr
  16. 16. Build Faster Set Higher Expectations Set Higher Demands @dwmkerr
  17. 17. Build Faster Set Higher Expectations Set Higher Demands @dwmkerr
  18. 18. Situation We’ve got better at building and we make more changes @dwmkerr
  19. 19. Situation Complication In many organisations, change causes conflict @dwmkerr
  20. 20. Development Responsible for building new products and services Assigned to build things @dwmkerr
  21. 21. Operations Responsible for maintaining existing products and services Assigned to maintain stability @dwmkerr
  22. 22. Development Responsible for building new products and services Assigned to build things Operations Responsible for maintaining existing products and services Assigned to maintain stability @dwmkerr
  23. 23. Change is the casus belli for a secret war in many organisations @dwmkerr
  24. 24. Release Feature @dwmkerr
  25. 25. Release Feature Feature Breaks @dwmkerr
  26. 26. Release Feature Feature Breaks Release Feature – Another Break @dwmkerr
  27. 27. Release Feature Feature Breaks Release Feature – Another Break New Processes @dwmkerr
  28. 28. Release Feature Feature Breaks Release Feature – Another Break New Processes Processes Skipped @dwmkerr
  29. 29. Release Feature Feature Breaks Release Feature – Another Break New Processes Processes Skipped Systems Locked Down @dwmkerr
  30. 30. Release Feature Feature Breaks Release Feature – Another Break New Processes Processes Skipped Systems Locked Down Late Feature @dwmkerr
  31. 31. Release Feature Feature Breaks Release Feature – Another Break New Processes Processes Skipped Systems Locked Down Late Feature Business Attack @dwmkerr
  32. 32. Release Feature Feature Breaks Release Feature – Another Break New Processes Processes Skipped Systems Locked Down Late Feature Business Attack Feature Breaks @dwmkerr
  33. 33. Situation Complication In many organisations, change causes conflict @dwmkerr
  34. 34. Situation Complication Resolution DevOps - a shared responsibility to manage change @dwmkerr
  35. 35. Development Operations Responsible for building new products and services Assigned to build things Responsible for maintaining existing products and services Assigned to maintain stability @dwmkerr
  36. 36. DevOps Responsible for building and maintaining new products and services Assigned to build and maintain robust and resilient things @dwmkerr
  37. 37. So why should we care? @dwmkerr
  38. 38. Situation Complication In many organisations, change causes conflict @dwmkerr
  39. 39. Conflict… Politics… Bureaucracy… Intransigence… @dwmkerr
  40. 40. …is boring. Show me the code! Conflict… Politics… Bureaucracy… Intransigence… @dwmkerr
  41. 41. DevOps Culture for Engineers …because engineers can make these changes happen! @dwmkerr
  42. 42. Learn about DevOps So that you can be an agent for change… @dwmkerr
  43. 43. @dwmkerr
  44. 44. Share your knowledge And be ready to learn… @dwmkerr
  45. 45. Programming Scripting APM Log Management Containers Container Orchestration Dependency Management Versioning Database Querying Database Admin Rack & Stack Physical Infrastructure Data Centre Management Infrastructure-As-Code Immutable Infrastructure SSL Secret Management TCP/IP HTTP DNS Networking VPN Automated Testing Static Analysis Functional Patterns Platforms Languages Mobile Browser Fat Clients Documentation CI/CD @dwmkerr Automation Artifact Management 12-factorCode Quality TDD Virtualisation Linux Sys Admin Backup & Restore
  46. 46. Programming Scripting APM Log Management Containers Container Orchestration Dependency Management Versioning Database Querying Database Admin Rack & Stack Physical Infrastructure Data Centre Management Infrastructure-As-Code Immutable Infrastructure SSL Secret Management TCP/IP HTTP DNS Networking VPN Automated Testing Static Analysis Functional Patterns Platforms Languages Mobile Browser Fat Clients Documentation CI/CD @dwmkerr Automation Artifact Management 12-factorCode Quality TDD Virtualisation Linux Sys Admin Backup & Restore
  47. 47. Empathise Because people have different challenges, and devops is a cultural transformation… @dwmkerr
  48. 48. Fight for institutional learning Healthy organistions invest heavily in learning @dwmkerr
  49. 49. Online Courses Certification Brown Bags Meetups Conferences Tech Blogging Hackathons Competitions Spikes & POCs Self-Study Hobby Projects Open Source @dwmkerr
  50. 50. Fight for institutional learning Because everyone has a lot to learn, and in tech if you are not learning then you are moving backwards @dwmkerr
  51. 51. Fight Toil You should be the first to automate @dwmkerr
  52. 52. @dwmkerr Copyright Randall Munroe, XKCD #1205 “Is it worth the time?” https://xkcd.com/1205/
  53. 53. Create observable systems Always think about monitoring, logging, analytics – and consider the ‘human process’ @dwmkerr
  54. 54. Elevate this discussion Make this topic important @dwmkerr
  55. 55. Thanks! @dwmkerr dwmkerr.com github.com/dwmkerr linkedin.com/in/dwmkerr

×