Downloaded 33 times
Uploaded byJagatveer Singh
DevOps without DevOps Tools
Patrick Debois emphasizes the necessity of cooperation between development (dev) and operations (ops) teams, highlighting the common blame game that arises when change is introduced. He advocates for a cultural shift that allows for more frequent updates and collaboration to minimize risks and enhance business readiness, rather than discouraging change for the sake of stability. The document discusses the challenges of communication within teams and encourages finding solutions for better coordination and operational efficiency.
In this document
Powered by AI
Introduction of Patrick Debois, a key figure in DevOps discussions.
Exploring the cooperation between Development (Dev) and Operations (Ops) with a focus on DevOps tools.
Conflict between Dev and Ops, highlighting their differing responsibilities and communication breakdowns.
Challenges faced due to stability versus change, including blame culture and risk associated with deployments.
Organizing DevOps events for collaboration and communication among roles like PM, Dev, and Ops.
Final thoughts on identifying value in collaboration and tools to enhance DevOps initiatives.
More Related Content
Similar to DevOps without DevOps Tools
DevOps without DevOps Tools
- 3.
- 4.
- 5. Introduced as anidea of cooperation between Dev and Ops
- 6. DevOps without DevOpstools - Jagatveer Singh
- 7.
- 8. “It’s not mymachines, it’s your code”
- 9. “It’s not mycode, it’s your machines!!”
- 11. Says “No” Allthe time Afraid that the new fangled things will break the site
- 12. They say “NO”all the time Because the application breaks unexpectedly Because no one tells them anything Because
- 13. Dev’s job isto add new features Ops’ job is to keep the site stable and fast
- 14. Ops’ job isNOT to keep the site stable and fast
- 15. Ops’ job isto enable the business <Psst>This is dev’s job too</Psst>
- 16. The business requireschange
- 17. Change is alsothe root cause of most outages!
- 18. Discourage change for stability Allowchange to happens as often as it needs to
- 19. Lowering risk ofchange through tools and culture
- 20. Problem!!! Nooooo! Freaking out, not talking, findingfault Blaming, covering ass Whining, hiding, hurt egos Figuring it out Fixingthings Fixed Time
- 21.
- 22.
- 23.
- 24. “10+ Deploys perDay: Dev and Ops Cooperation” at Velocity 2009 John Allspaw and Paul Hammond
- 25. Why not organizemy own Velocity event in Belgium? #DevOpsDays #DevOps
- 26.
- 27.
- 28.
- 29. • A greatconcept somehow limited to just coordinating two misfits • Figure out what your collaboration can bring in for the organization, be ready for paper planes • Noise or static?? Identify them. • Now chase tools
- 32.