Patterns & Anti Patterns for Scaling & Enabling DevOps Adoption
summary
Argues that enterprise DevOps fixes actual bottlenecks by building a pipeline that produces a single binary stored in Nexus/artifactory, runs infrastructure-as-code (Terraform/Chef/Puppet) and ephemeral environments, and uses blue‑green/feature flags for safe rollouts. Measures to drive behavior are mean time to recovery, change failure rate, cycle time and release frequency. Recommends pilot/tiger teams, automating compliance as pipeline quality gates, and proving ROI with an Excel model (example: 30‑minute builds vs. buying ~20 agents).
AI-written summary · about
chapters (8)
- 0:00Introduction to Enterprise DevOps
- 5:09Bottlenecks and Bus Factors
- 12:36Measuring DevOps Success
- 20:08Everything as Code and Pipelines
- 34:16Enterprise DevOps Pipeline Mentality
- 41:04Pilot Projects and Baby Steps
- 45:20Cultural Change and Team Dynamics
- 52:09Q&A and Recommended Books
related talks
18mDesign Patterns For Efficient DevOps Processes
40mContinuous Delivery Anti-Patterns
54mEffective DevOps for Organizations
01h 02mThe Enterprise DevOps Challenge
46mContinuous delivery antipatterns
01h 02mThe Enterprise DevOps Challenge
47mOvercoming Obstacles to DevOps
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
