Continuously Improving Culture through Design Decisions
summary
Two Sigma builds COIN, a CI/CD platform that centralizes Jenkins on Kubernetes and drives culture through design: Jenkins on Kubernetes, 90+ Jenkins instances, 1300+ pipelines, and 40,000 integration tests/day back a claimed 10x increase in deployment frequency. Hard rules (admin-only Jenkins config, pipelines in source control, enforced container updates), incentives (free CD, success stories), and extensibility (internal integrations, dynamic worker images, Slack community and classes) produce measurable shifts in automation, cohesion and release confidence.
AI-written summary · about
chapters (30)
- 0:00Intro
- 0:37Who Am I?
- 1:45Culture Disclaimer
- 2:56Tech Culture Can Work Against Us
- 4:09Change the Culture
- 4:42Benefits of a Healthy Culture
- 7:19Collaborate
- 7:48Control
- 8:19Compete
- 8:44OCAI Types of Culture
- 9:26Values of Technology
- 10:30Hard to Quantify
- 10:58Harder to Change
- 11:47Your Product(s) Influence Cultural Outcomes
- 12:52Actions Speak Louder Than Words
- 13:29DevOps Values
- 14:34TS DevOps
- 17:39Be the change you want to see in the world
- 18:38Set the Example
- 20:01Create Incentives
- 23:16Create Hard Rules
- 25:57Facilitate Innovation
- 26:45Tools For Innovation
- 28:43Build a Community
- 29:31Community Initiatives
- 32:02Have a Tight Feedback Loop
- 34:00Measure Impact
- 34:44Measurements of Impact
- 35:56Tech Culture Can Work For Us
- 37:10COIN's Success
related talks
42mAutomation, Innovation and Continuous Delivery
27mArchitect CI/CD on Enterprise level
30mA Journey Introducing Jenkins to Enterprise IT
58mBuilding a Culture of Continuous Delivery
30mCI/CD - the game where all win!
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
31mWhat I learned about teams from building the Jenkins project
14mHow We Decided the Time Was Now - Choosing Spinnaker