Bringing DevOps into the Enterprise
summary
Shows concrete numbers and fixes so decide by specifics not platitude: enterprises run 1.5 year release cycles then move to 2 week sprints and discover ops must provision five servers in weeks not months; tooling lifetimes matter, expect ~10 year enterprise windows on tool choice and debates like CapEx vs OpEx when moving to AWS or cloud; practical fixes are automating provisioning and network, involving finance and security early, requiring C‑level commitment, avoiding mythical “DevOps engineer” hires and using brown bag coaching to retrain staff which proves effective when leadership backs it.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 1:12The story
- 1:43What are enterprises
- 2:20DevOps
- 3:15Large enterprises
- 4:16Different management levels
- 5:20Project management
- 8:18Why DevOps
- 12:22DevOps Principle
- 14:30DevOps Finance
- 17:24DevOps Culture
- 18:11Automation
- 19:14Transparency
- 20:02Agility
- 20:34DevOps kata
- 22:06Challenges
- 23:43Change Management
- 25:06High Planning Effort
- 26:22The People
- 27:24The Management
- 28:02Expectations
- 29:51Customer feedback
- 32:17Possibilities
- 32:49Top level commitment
- 34:46Processes
- 35:35Security
- 36:14Conclusion
- 36:44How do we do it
- 37:07Move to Agile
- 37:53Coaching
- 38:19Survival
related talks
29mHunting the DevOps Whale
01h 02mThe Enterprise DevOps Challenge
34mDevOps Transformation from the C-Level point of view
32mDevOps as Driver of Organization-Wide Change
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
50mAdopting DevOps? You are Aiming at the Wrong Target!
30mAdopting DevOps? You are aiming at the wrong target!
25mDevOps for Pointy-Haired Bosses