Opening Keynote: The Enterprise DevOps Mind Trap
summary
Argues enterprise DevOps fails from four influence forces—personal and social motivation and ability plus structural counterparts—so adoption succeeds only when those are changed, not just tooling; cites 500 deploys a day at GitHub as achievable because the company designs support for it. Recommends pilots and a tiger team, making the pipeline as policy (Jenkins, Sonar, automated security/compliance checks), avoiding big‑bang transforms, and measuring time to recover from red to green and lead time rather than raw green builds or coverage.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:53Why this talk
- 2:45Agenda
- 3:26What is an Enterprise
- 5:37Influencer
- 11:28Structural Motivation
- 15:20Behavior
- 15:50Behavior Chart
- 17:04Checklist
- 18:43Enterprise Challenges
- 21:40Change
- 21:53Big Bag Transformation
- 23:05Boiling the Ocean
- 23:29Pilot Projects
- 24:14Pilot Teams
- 24:59Bidirectional Support
- 26:23Simple Pipeline
- 27:59Pipeline Policy
- 29:24Tiger Team
- 31:11Value Stream
- 35:13Metrics
- 38:02Red is good
- 40:23Other metrics
- 43:10Summary
related talks
01h 02mThe Enterprise DevOps Challenge
44mOpening Keynote: Testing in the age of DevOps
48mNew barriers for DevOps adoption
54mEffective DevOps for Organizations
11mDevOps Pitfalls, Beyond The Technology
33mWhat Got Us Here Won’t Get Us There: A Story of Transformations
47mOvercoming Obstacles to DevOps
01h 02mThe Enterprise DevOps Challenge