From Git Push to Exit
summary
A startup builds continuous deployment from day one using GitHub with a single master branch, feature flags via Launch dly, AWS CDK (Python), AWS Secrets Manager, CodePipeline/CodeBuild, CloudWatch and Sentry, Selenium robots and anonymized copies of production data for tests. Empirically the org averages 11 deployments per day, median release lead time is 13 minutes (90% between 3–100), story median is 3 days (95% 2h–21d), two major incidents in five years, and the approach helps capture ~20% market share and a 2024 acquisition.
AI-written summary · about
chapters (12)
- 0:00Introduction and Speaker Background
- 0:51Overview of the Startup and Initial Challenges
- 1:44Introduction to DORA Metrics
- 2:52Continuous Deployment Explained
- 4:51Building Blocks of Continuous Deployment
- 7:00Environment Setup and Pipeline
- 9:37Empirical Results and Metrics
- 10:49Operational and Financial Metrics
- 12:57Feature Factories vs. Empowered Teams
- 14:41Product Discovery and Experimentation
- 18:31Story Workflow and Delivery
- 23:05Conclusion and Q&A
related talks
01h 01mA team's transition to Continuous Delivery
47mContinuous Delivery Warstories
24mContinuous Deployment at Scale
01h 00mReliability and speed by 'push to main' mentality
43mContinuous Deployment: The GitOps, The Pipelines, and The Ugly
30mPushing to master - adopting trunk based development
46mContinuous Deployment Workflows
30mRelease Early and Release Often: Reducing deployment friction