Conway & Taylor Meet the Strangler (v2.0)
summary
Company reduces release incidents from 201 (2013) to 18 (Aug) — a 90% reduction to 18 incidents — and shortens release cadence from 28 to 14 weeks. CI/CD and infrastructure as code automate Jenkins farm provisioning (15 Windows VMs, 4×/year) and use infrastructure as code with Chef to make servers reproducible. Legacy migration uses the strangler pattern with SpecFlow ATDD comparing XML to preserve behavior, saves >$9M and drops cost per core from $217 to $144. Telemetry consolidates into StatHub (Elasticsearch, ~4,000 events/sec) and deployments hit every-2-weeks aiming for twice-weekly.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:50CSG in North America
- 2:10Release Recap
- 3:23Operations Engineers
- 4:23The Problem
- 5:34Technical Debt
- 6:15V2 Techniques
- 7:17Holistic Incident Visibility
- 9:53Dependency Visibility
- 10:42Conways Board
- 12:04Single Intake
- 13:03Move to one toolset
- 13:24Challenge shared KPIs
- 15:00Ghost See Roll
- 16:49Infrastructure as Code
- 18:15Double Loop Learning
- 20:54Legacy Test Automation TDD
- 23:12Results of Automated Testing
- 23:54Telemetry Shared Understanding
- 26:28Recap
related talks
49mThe road to continuous deployment: a case study
53mThe Road to Continuous Deployment: a Case Study
10mBeyond “try harder”: Effective strategies to tackle bugs
53mTransforming testing methodologies: From manual to robust strategies
22mFrom Code Commit to Production Within a Day
34mEnabling a Continuous Deployment Mindset
35mTaming a beast
32mClimbing the Mountain of CI/CD: A Tester’s Tale