You are not a DevOps Engineer

You are not a DevOps Engineer

Is hiring a “DevOps Engineer” the answer to your organisational problems? Or is it the tools you use? NO! In this talk, we’ll discuss how to bring the DevOps culture to your organisation and transform how your team develop, test, deploy and deliver software in a fast, reliable and sustainable way.

76244562f2d2b88d11c6746e24f588ef?s=128

Derik Evangelista

September 17, 2019
Tweet

Transcript

  1. None
  2. © Copyright 2018 Pivotal Software, Inc. All rights Reserved. Felisia

    Martini Derik Evangelista September 2019 You are not a DevOps Engineer
  3. Who are we? Felisia Martini Software Engineer @ Pivotal @felisiamartini

    Derik Evangelista Software Engineer @ Pivotal @kirederik
  4. What we will talk about ▪ What is DevOps trying

    to fix ▪ How companies start charging to adopt DevOps ▪ How to optimise that change ▪ Q&A
  5. Why was DevOps created? Competing incentives • Development teams aim

    to create new features • Operations teams aim to provide reliable service • Produce unstable, unreliable and insecure services Human cost • Burnout • Not empowered teams/individuals • Unsustainable pace Silos • Development and Operations work in almost isolation • Energy spend coordinating between teams • Rework
  6. improve organizational performance achieve the goals of all the roles

    improve the human condition THE PROMISE
  7. None
  8. Changes Rename an existing team Hire DevOps

  9. DevOps Role The title • DevOps Engineer • DevOps Manager

    • Head of Digital DevOps What you will be doing • Infrastructure • Operating systems • Containers engine and orchestration • Platforms • CI/CD • Databases • Applications
  10. What is happening? SEVERAL MONTHS LATER ...

  11. New Silo • Devs and Ops are not communicating •

    The DevOps role/team becomes the new gate to production • You are creating new tools - pipelines, infrastructure, etc - but no one is using
  12. Temporary fix • Seeming reactive • Dealing with the symptoms

    • Postponing the need to change for later
  13. Why? IT IS NOT WORKING

  14. Organisational status quo • Not letting go of functional-oriented organisation

    • Everyone has well defined, separated roles
  15. Culture status quo • The role doesn’t necessarily bring the

    cultural change • Developers and Operators silos were not addressed • Human cost
  16. DevOps TECHNOLOGY CULTURE Build empathy PROCESS Continuously improve TOOLS Focus

    on developer productivity PLATFORM Focus on the tech solution MODERN SOFTWARE ORG PROCESS
  17. None
  18. What can companies do?

  19. Find the organisation pain points Spend time understanding the root

    of the issues • Identify the flow and the bottlenecks • Make the smallest cheapest change first • Drive the change bottom-up rather than top-down
  20. Be service focused Reduce inefficiencies by focusing on creating teams

    around services • Reorganise around a service • Allows for the roles to emerge • Optimise for self service
  21. Empower teams Allow people to invest time in learning and

    experimenting with the practices • You build it, you run it • Build around experimentation • Team rotations • Cross team pairing
  22. What can you do?

  23. Evangelise Be the voice that asks for change • Push

    for those cultural changes • Drive the change bottom-up rather than top-down
  24. Share experience Make others more aware of what your work

    includes • Pair with Devs and Operations • Share any pain-point you experience • Align your expertise closer to other roles • Be available
  25. Optimise for impact Listen for symptoms; Treat the disease •

    Find the pain points • Identify the root cause • Iterate towards a solution
  26. And much more! • Learn ◦ “The Phoenix Project” and

    “The DevOps Handbook” are a great place to start • Experiment • Talk to people
  27. “DevOps is not a goal, but a never-ending process of

    continual improvement” Jez Humble
  28. None
  29. Thanks!