A Conversation on Culture: Our Journey
summary
CloudBees reports growth from ~100 employees in 2015 to ~520 now, spread across 18 countries, and recent acquisitions (Electric Cloud, Rollout) force culture integration and tool harmonization. Open-source project Jenkins X shifts from rapid innovation toward stability and security as customers arrive. Successful fixes include replacing a rotating bug boy role with a permanent ops team, launching cross-functional product business teams, and asking new hires to publish short “how I work” user manuals to increase accountability and onboard shared behaviors.
AI-written summary · about
chapters (30)
- 0:00Intro
- 1:22Why weve struggled
- 2:28Alex
- 3:06Ellen
- 3:58Mo
- 4:32Tracy
- 5:30Christina
- 6:11Level Setting
- 6:43How do you define culture
- 9:08Culture is never written down
- 13:18Jenkins X
- 16:15How to change culture
- 19:08How do you signal to employees
- 19:56Acknowledgement
- 22:16Open Source vs Corporate Culture
- 24:18HR Role in Culture
- 27:06Cultural Winds
- 28:33Engineering
- 29:03Bug Boy
- 31:54Blame Free Culture
- 33:23Blame
- 33:58Raise your hand
- 36:04People writing new user manuals
- 38:23Acquisitions
- 41:14Product Business Teams
- 43:08What we are getting wrong
- 44:45Globally distributed remote working
- 46:32Aligned with a corporate strategy
- 48:16Remote split
- 49:38Finishing meetings
related talks
42mAutomation, Innovation and Continuous Delivery
31mWhat I learned about teams from building the Jenkins project
30mA Journey Introducing Jenkins to Enterprise IT- 30mA Journey Introducing Jenkins to Enterprise IT
54mCloud Native Culture
34m(Re)building an Engineering Culture: DevOps at Target
15mEngineering Culture and Developer Productivity
45mPeople and Culture