Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.
Nächste SlideShare
What to Upload to SlideShare
What to Upload to SlideShare
Wird geladen in …3
×
1 von 57

What does devops culture mean for engineers

3

Teilen

Herunterladen, um offline zu lesen

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

Ähnliche Bücher

Kostenlos mit einer 30-tägigen Testversion von Scribd

Alle anzeigen

Ähnliche Hörbücher

Kostenlos mit einer 30-tägigen Testversion von Scribd

Alle anzeigen

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

Notizen

  • 5m mark:
    Serving clients across the world, deploying in airports, writing code.
  • To me, this is important.
    This is about allowing us to do what we love the most – build things, tinker, experiment, learn
    It’s about reducing conflict, making the places we work more exciting and enjoyable places to work out.

    Cannot escape the nerves that I've missed something out because there is no code, and I am not the only one!!
  • - Before we talk about what DevOps is, why we should care, and if we do, what we do about it, it is important to understand where it has come from.
  • The way we build has changed dramatically.
  • Traditional, building software was like classical architecture
    Very expensive materials, very expensive construction
    Known use case, build perfectly, rarely change.
    Build upon a rickety structure, software made of a foundation which was never designed to be adapted
  • A lot more change is happening
  • Nowadays, requirements of users are much more flexible
    Technology is cheaper & faster, change is much more common
    Now more like city planning: evolutionary architecture
    Hosting, Zoning, Infrastructure, Traffic, Capacity
    In the world of software this might be about designing small, modular components which we can swap in and out, or plugin like systems, or APIs which we can have multiple versions of
    In architecture, this might be containers, service orientation etc etc
  • A lot more change is happening
  • A lot more change is happening
  • Complicated systems
    Deterministic and predictable, laws are applicable again and again, learn to get *very* good at designing a bridge

    Role defining – setting job and task descriptions
    Decision making – find the ‘best’ choice
    Tight structuring – use chain of command and prioritise or limit simple actions
    Knowing – decide and tell others what to do
    Staying the course – align and maintain focus

    Complex adaptive systems
    Many interacting parts, which might be deterministic but chaotic, unexpected results, difficult to predict.
    Relationship building – working with patterns of interaction
    Sense making – collective interpretation
    Loose coupling – support communities of practice and add more degrees of freedom
    Learning – act/learn/plan at the same time
    Notice emergent directions – building on what works
  • - Before we talk about what DevOps is, why we should care, and if we do, what we do about it, it is important to understand where it has come from.
  • A lot more change is happening
    We enter a feedback loop
    We do whatever we can to build faster, better tech, better process, whatever
  • A lot more change is happening
    We enter a feedback loop
    We do whatever we can to build faster, better tech, better process, whatever
  • A lot more change is happening
    We enter a feedback loop
    We do whatever we can to build faster, better tech, better process, whatever
  • A lot more change is happening
  • A lot more change is happening
  • A lot more change is happening
  • Business attack anyone with a computer
  • Business attack anyone with a computer
  • Business attack anyone with a computer
  • Business attack anyone with a computer
  • Business attack anyone with a computer
  • Business attack anyone with a computer
  • Business attack anyone with a computer
  • Business attack anyone with a computer
  • Business attack anyone with a computer
  • A lot more change is happening
  • A lot more change is happening
  • This bullshit slows you down. It’s not fun. And in an organization where you are not learning, you are moving backwards.
    You can tell how happy I am by how much of my day I am in tmux.
    Healthy work environment.
  • Familiarise yourself with this. Read the books. Learn about lean. Come to conferences. Talk to people. Blog about it.
    There’s a lot of stuff in devops, getting it to work is not easy, learn about how other people have done it, and learn the skills to do it yourself.
  • A lot more change is happening
  • A lot more change is happening
  • - When someone objects to what you are doing, try to understand why
    This change takes a while to happen, as you go through it, peoples roles will change, peoples goals will change
    This is a cultural change
  • - Story: talking to a colleague who was paying to do his own exam
  • Think about the ‘human case’, when things fall back to human beings
  • A lot more change is happening
  • ×