From 6 Month Waterfall To 1h Code Deploys
summary
Claims migration from six‑month waterfall to shipping feature releases every two weeks and executing 170 SaaS production changes/day while enabling 1h code deploys. Pipeline uses Jenkins, Selenium with Sauce Labs, AWS staging, APM/monitoring (dynaTrace) and a pipeline visualizer; test strategy runs 31,000 unit and integration tests/hour with prioritized 10‑minute fast feedback and 60h UI tests per build. Developers own deploys and use production metrics so teams catch 93% of bugs in production before they impact users.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:43User-Driven Continuous Delivery through DevOps 1 Feature at a Time
- 11:40First Orchestration Engine to AWS
- 12:07Velocity uncovers new bottlenecks!
- 13:03Need to increase Sprint Quality
- 14:31Essential End User Feedback Loop
- 15:28Automated Error Analysis
- 16:28We started to understand "The Cloud"
- 18:23Pipeline quality + 10 min Builds
- 22:48Deploy, Fail & Recover Fast
- 23:23Biz: User Feedback Driven Decisions
- 30:30Dynatrace Transformation by the numbers
related talks
01h 01mA team's transition to Continuous Delivery
37mFrom Waterfall to Agile
33mFrom 0 to DevOps in 80 days
12mContinuous Deployment in a heavily regulated environment
47mContinuous Delivery Warstories
47mFrom bi-annual to fortnightly releases in 4 months for 15 teams and one monolith
30mContinuous Integration at Haptik : Our Journey to Hourly Releases
53mTransforming testing methodologies: From manual to robust strategies
