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

DevOps – How our mental model of IT has evolved over more than decade

DevOps – How our mental model of IT has evolved over more than decade

75cf8176bf14811428f77d8fe737f0d5?s=128

Konstantin Diener

June 17, 2021
Tweet

More Decks by Konstantin Diener

Other Decks in Technology

Transcript

  1. Konstantin Diener | konstantin.diener@cosee.biz | @coseeaner DevOps – How our

    mental model of IT has evolved … … over more than decade
  2. Konstantin Diener CTO and Co-Founder of cosee

  3. Start Scale product development

  4. Discovery- Phase Backlog Expert-Teams Billing Models Iterative Delivery Software- Releases

  5. None
  6. The IT scene looked completely di ff erent more than

    a decade ago …
  7. None
  8. • as many features as possible • quick response •

    Scrum: Shippable Product • stable application • no incidents or major bugs • no Downtimes >> throughput >> stability Development Operations
  9. https://de.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/

  10. https://de.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr/ Ops’ job is to enable the business (this is

    dev’s job too)
  11. What has changed?

  12. When we say Products …

  13. User Story Mapping Je ff Patton

  14. Je ff Patton, User Story Mapping, https://jpattonassociates.com/

  15. Focus on Outcome, not on Output.

  16. When we say Responsibility …

  17. None
  18. None
  19. Product development has become a cross-functional team sport.

  20. When we say Releases …

  21. Firma Auslieferungs- frequenz Code Deployment Lead Time Reaktion auf Kundenwunsch

    Amazon 23.000/Tag Minuten hoch Google 5.500/Tag Minuten hoch Netflix 500/Tag Minuten hoch Facebook 1/Tag Stunden hoch klassisch 1/alle 9 Monate Monate/Quartale niedrig/mittel The Phoenix Project
  22. The Phoenix Project Gene Kim, Kevin Behr, George Spa ff

    ord
  23. When we say infrastructure …

  24. None
  25. None
  26. First Virtualisierung

  27. then Cloud

  28. AWS has only existed since 2006.

  29. Infrastructure as Code, not „as configuration“

  30. When we say infrastructure components …

  31. None
  32. None
  33. Managed Services

  34. When we say handling infrastructure …

  35. None
  36. None
  37. When we say failure …

  38. None
  39. Everything fails all the time. “ Werner Vogels

  40. None
  41. Chaos Engineering

  42. When we say Dealing with failure …

  43. None
  44. None
  45. None
  46. Blameless Postmortems

  47. None
  48. Is this called DevOps culture?

  49. • Use shared goals & shared responsibility • Make business

    & customers successful. • Release o ft en & in small batches. • Use Infrastructure as Code & Managed Services. • Avoid PET infrastructure. • Accept failure happens to be part of IT. • Learn from failure and share your learnings. Cheat Sheet
  50. konstantin.diener@cosee.biz | @onkelkodi Picture credits: Cover: https://www.shutterstock.com/de/g/GaudiLab Silos: https://www.shutterstock.com/de/g/davotibarna Server:

    https://www.shutterstock.com/de/g/shock Let’s keep in touch? Konstantin Diener | cosee GmbH cosee.biz