Going Big With DevOps

Going Big With DevOps

Scaling sustainable, continuous and solid success

21f588b59e5b0a7d92be27f14405747a?s=128

Xavier Bruhiere

December 04, 2019
Tweet

Transcript

  1. Going Big with DevOps 1 Scaling Sustainable, Continuous and Solid

    success
  2. 2 Hello world Meet github.com / kelseyhightower / nocode Not

    made up: • 33.7k stars • 3k forks • 2,634 issues • 394 pull requests
  3. 3 Hello world Hey, I’m Xavier Bruhiere Head of Data

    Engineering at Lazada eLogistics 4 50 120 8000 pax Companies I deployed things for
  4. 4 Hello world All happy families are alike; Each unhappy

    family is unhappy in its own way -- Anna Karenina principle
  5. 5 Introduction The elephant in the room: what is DevOps?

  6. 6 Introduction Instead: why DevOps? 50 years

  7. 7 Introduction Instead: what is DevOps success? > Agility >

    Reliability > Velocity > Cost > Confidence spoiler
  8. 8 Introduction Again: what is DevOps success? > Scalable >

    Sustainable > Impactful Keep in sight
  9. 9 1. Cross-team collaboration 2. Spread enterprise-wide 3. Business impact

    that matters AGENDA
  10. 01 Cross-team collaboration 10

  11. 11 Cross-team Cross-team brain DevOps Journey • Customer expectations •

    Business goals • Tech trade-off • Operational capacity Dev Sys QA Business Track releases – Align incentives
  12. 12 Cross-team The culture glue Recipe for success • Top-down

    • Single-team mindset • Growth mindset DevOps Journey not my job
  13. 13 Cross-team 3 ownership models Collaboration Squads Role Platform End-to-end

    Vertical skills Consultant Versatile More capacity More specific/generic
  14. 14 Cross-team Bonus ownership model Collaboration The unicorn data scientist

  15. 15 Cross-team The product owner Key Buffer Role • Translate

    requirements • Understand domain • Filter requests • Document Collaboration
  16. 16 Cross-team What to share Tech skills Tech capacity Knowledge

    Make everyone responsible Rotate on-call Company transparency Help trade-off
  17. 17 Cross-team What to share (2) Business domain Teams KPI

    Knowledge Empower engineers Connect people Legitimate efforts Foster empathy
  18. 02 Spread enterprise-wide 18

  19. 19 Spread Engineering a good Strategy Horizontal scaling: across tech

    Vertical scaling: across functions & departments
  20. 20 Spread Engineering a good Strategy (2) Manage legacy Identify

    where it matters
  21. 21 Spread Getting started - Tech Scaling horizontally Engineers to

    learn from each-other • Open the tooling repositories • Lunch and learn • Mentorship • Hackathons • Experimentation • All-hands • …
  22. 22 Spread Scaling horizontally You build it – you ship

    it – you fix it Central tooling Building stuff
  23. 23 Spread Scaling horizontally & vertically Opt-in model Managed Tech

    platform Legacy stuff That works
  24. 24 spread Your deploys should be as boring, straightforward and

    stress-free as possible -- Zach Holman (How to deploy software)
  25. 25 Spread Scaling vertically Get people involved Production Feature Staging

    Dev User Business Product Owner Engineer Feedback
  26. 26 Spread Scaling vertically Testing in production Eating your own

    dog food v5 v4 10% 90%
  27. 27 Spread Risks & Challenges (1) Optimizing local optimums Limiting

    scopes of knowledge Falling in love with the tech Infinite feedback loop Security
  28. 28 Spread Risks & Challenges (2) Machine learning and Big

    Data
  29. 03 Business impact that matters 29

  30. 30 Business impact Build it and they will come --

    someone with no customers
  31. 31 Business impact 1. The right things to fix McKinsey

    coined the 2 speeds IT • Identify high-leverage areas • Understand legacy
  32. 32 Business impact 2. Communicate DevOps is not a side

    project Set ambitious expectations Plan transparently Educate as you go
  33. 33 Business impact 3. Measure For a good impact, take:

    Good KPIs Great feedback loop Lots of iterations
  34. 34 Business impact 4. Let them know | Customer Care

    # Brag about it # Replicate success # Train customers # On-board new features # Share knowledge # Open source # Improve # Promote # Survey
  35. 35 Culture Sharing Cross-* Communication Iteration Results Wrapping Up

  36. 36 Thanks Talk deployed

  37. 37