Upgrade to Pro — share decks privately, control downloads, hide ads and more …

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.

Derik Evangelista

September 17, 2019

Other Decks in Business


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

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

    Derik Evangelista Software Engineer @ Pivotal @kirederik
  3. 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
  4. 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
  5. 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
  6. 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
  7. Temporary fix • Seeming reactive • Dealing with the symptoms

    • Postponing the need to change for later
  8. Culture status quo • The role doesn’t necessarily bring the

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

    on developer productivity PLATFORM Focus on the tech solution MODERN SOFTWARE ORG PROCESS
  10. 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
  11. 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
  12. 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
  13. Evangelise Be the voice that asks for change • Push

    for those cultural changes • Drive the change bottom-up rather than top-down
  14. 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
  15. Optimise for impact Listen for symptoms; Treat the disease •

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

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

    continual improvement” Jez Humble