The Continuous Culture
summary
Argues that moving to continuous delivery and DevOps retools company DNA by forcing experiments, faster feedback and small deployments rather than long roadmaps. Cites State of DevOps numbers: 10% success for large projects vs 74% for small, 64% unused features in big projects vs 14% in small. Describes concrete practices that worked: 7,648 deployments/day benchmark, monthly hacking sessions, Jenkins pipelines, automated security scanners, canary releases, feature flags, ~400 microservices, daily visible management standups and revamped HR to enable autonomy.
AI-written summary · about
chapters (33)
- 0:00Intro
- 0:34The Continuous Culture
- 3:02The Kinetic Model
- 5:26Change Often
- 6:08Incremental Change
- 6:30Safely and sustainably deliver software
- 7:18What is continuous
- 9:35Roadmaps
- 10:14Stop reading sprints
- 10:34Make things small
- 11:49Quadrants
- 13:35Youre not the only one
- 14:46Security
- 16:21Release
- 17:17Reinvent HR
- 17:28Do things differently
- 19:41Agile HR Manifesto
- 20:12Autonomy
- 20:43Feedback
- 21:58Teams
- 22:24DevOps
- 22:47Learning
- 23:16Academy
- 23:30Microservice Architecture
- 24:14Test Pyramid
- 26:09Branching
- 26:19Code Integration
- 27:43Rehearsal
- 28:58Customers dont want continuous delivery
- 29:13Broken interest
- 29:49Take them along
- 30:15Wrapping it up
- 30:58Be ready for a surprise
related talks
59mThe continuous culture
24mWhy, What, and How of Continuous Delivery
34mDevOps: Next
51mBetter software, faster: principles of Continuous Delivery and DevOps
37mWant to do the DevOps? Change Everything
50mThe Structure of Software Revolutions
34mYou only have to change one thing to do the DevOps
54mEffective DevOps for Organizations