DevOps Is Not What You Have Been Told It Is
2 likes239 views
The document discusses the concept of DevOps, highlighting misconceptions and emphasizing that DevOps is more than just technical practices; it requires a cultural and organizational approach. It underscores the need for collaboration, continuous improvement, and broader transformations beyond merely integrating development and operations. The author, Christian Melendez, advocates for a holistic view of DevOps, considering aspects like people, processes, and products to create value.
More Related Content
Similar to DevOps Is Not What You Have Been Told It Is (20)
More from Christian Melendez (20)
![Strategic Picks — Prioritising the Right Agentic Use Cases [2/6]](https://cdn.slidesharecdn.com/ss_thumbnails/session-2-250902135931-4c97717a-thumbnail.jpg?width=560&fit=bounds)
DevOps Is Not What You Have Been Told It Is
- 1. T R A C K : C U LT U R A L T R A N S F O R M A T I O N N OV E M B E R 1 2 , 2 0 2 0 Christian Melendez DevOps Is Not What You Have Been Told It Is
- 2. T R A C K : C U LT U R A L T R A N S F O R M A T I O N Solutions Architect at Equinix Developer at heart, Engineer by nature! I like to talk/write/teach about DevOps, Kubernetes, Cloud, Security, Go, and other buzzwords J cmelendeztech.com | @christianmldz $whoami
- 3. T R A C K : C U LT U R A L T R A N S F O R M A T I O N By no means I’ll try to define what DevOps is … bear with me, I haven’t even started yet J Disclaimer!
- 4. T R A C K : C U LT U R A L T R A N S F O R M A T I O N
- 5. T R A C K : C U LT U R A L T R A N S F O R M A T I O N A Tool DevOps Team Jenkins DevOps Engineer
- 6. T R A C K : C U LT U R A L T R A N S F O R M A T I O N • A DevOps team • Sysadmins => DevOps engineers / SREs • Focus on creating CI/CD pipelines only What we’re seeing now?
- 7. T R A C K : C U LT U R A L T R A N S F O R M A T I O N https://dev.to/scalyr/why-are-engineers-getting-devops-fatigue-15hi
- 8. T R A C K : C U LT U R A L T R A N S F O R M A T I O N It started as an Ops movement
- 9. T R A C K : C U LT U R A L T R A N S F O R M A T I O N And after so many years …
- 10. T R A C K : C U LT U R A L T R A N S F O R M A T I O N Everybody wants DevOps
- 11. T R A C K : C U LT U R A L T R A N S F O R M A T I O N
- 12. T R A C K : C U LT U R A L T R A N S F O R M A T I O N Reasons why DevOps is not what you’ve been told it is …
- 13. T R A C K : C U LT U R A L T R A N S F O R M A T I O N Focus on three aspects • Technical • Organizational • Cultural Technical practices alone aren’t enough After 10 years of Continuous Delivery https://www.infoq.com/news/2020/02/ten-years-continuous-delivery/
- 14. T R A C K : C U LT U R A L T R A N S F O R M A T I O N “It’s about engineering, applying rational scientific thinking to solving practical problems within economic constraints” Dave Farley
- 15. T R A C K : C U LT U R A L T R A N S F O R M A T I O N Beyond Dev and Ops https://www.infoq.com/news/2020/03/devops-complexity-lessons/
- 16. T R A C K : C U LT U R A L T R A N S F O R M A T I O N “If you have the idea of dev and ops just working together to try to fix a problem of the build pipeline, the problem is way bigger. And we can attribute way more to the organization than we think. Always think about where the next bottleneck is.” Patrick Debois
- 17. T R A C K : C U LT U R A L T R A N S F O R M A T I O N Team Topologies (2015) https://www.infoq.com/articles/devops-team-topologies/
- 18. T R A C K : C U LT U R A L T R A N S F O R M A T I O N DevOps Team with an Expiry Date https://web.devopstopologies.com/
- 19. T R A C K : C U LT U R A L T R A N S F O R M A T I O N Encourages an iterative approach Has 4 dimensions: • People • Products • Partners • Processes Focus on co-creating value together! DevOps Influenced ITIL V4
- 20. T R A C K : C U LT U R A L T R A N S F O R M A T I O N • DevOps team/role? Temporary • Start with infra-as-code? Sure, but keep moving • Avoid eating the elephant in one bite • C O L L A B O R A T I O N • E M P A T H Y It’s Continuous Improvement
- 21. T R A C K : C U LT U R A L T R A N S F O R M A T I O N • Single VMs => Microservices in Docker • 2 – 3 days deployments => 5 minutes • We had DevOps evangelists • Multi-disciplinary team The name didn’t matter at the end! A Continuous Improvement Story
- 22. T R A C K : C U LT U R A L T R A N S F O R M A T I O N The NAME is not that important!
- 23. T R A C K : C U LT U R A L T R A N S F O R M A T I O N Some transformations are still focusing only on Development + Operations + Tooling We need to think more broadly! Nonetheless …
- 24. T R A C K : C U LT U R A L T R A N S F O R M A T I O N “You have to be aware that whenever a new idea or buzzword comes around, like DevSecOps or SRE, there’s value to it because it brings a new perspective to the table. It doesn’t mean that DevOps as a term will exist forever.” Patrick Debois
- 25. T R A C K : C U LT U R A L T R A N S F O R M A T I O N Thank You! •Christian Melendez • Cloud Architect at Equinix • cmelendeztech.com | @christianmldz