Why DevOps Fails to Deliver?
summary
Examines why many organizations that claim to do DevOps don’t get the expected benefits by revisiting what “DevOps” actually means. Covers the gap between developer and operations worlds, shares concrete on-the-ground practices (good and bad), and offers practical tips to start the cultural transformation while avoiding common pitfalls.
AI-written summary · about
chapters (23)
- 0:00Start
- 6:50Optimizing the value delivered to users
- 7:00Fostering communication and collaboration
- 7:16Historically different goals
- 8:06Aligning goals?
- 9:03A quick game with 2 possible answers
- 10:37Telling Ops "my Jenkins build isn't working"
- 11:37Notifying Ops in the morning about a prod deployment
- 13:48Using version control software
- 14:47Blaming the team responsible for the last prod bug
- 16:23Empirical walk
- 16:49How to do DevOps in a large-scale context?
- 18:31Cross-functional Ops team
- 21:12The impact of organization: An Ops integrated into each team
- 24:05Take Away
- 27:53Key takeaways: Leading by example and reliability
- 30:01Human interactions: Seizing collaboration opportunities
- 34:18Human interactions: Re/establishing trust
- 35:29Restoring trust: Example: A3 Problem solving
- 36:54Adapting rules to remote work
- 37:22Human interactions: Adapting to remote work
- 39:52Evolving goals
- 41:07Conclusion
related talks
46mWhy DevOps Does Not Deliver on Its Promises
45mDevOps is neither the Answer, nor the Question!
25mDevOps: Why do we Keep Messing Up?
11mDevOps Pitfalls, Beyond The Technology
38mKill DevOps
33mThe DevOps disaster: 15 ways to fail at DevOps
45mWhat is DevOps and why should you care?
30m3 Practices for Effective DevOps Adoption