Spinnaker Summit Opening Keynote
summary
Advice centers on prioritizing what is core: stop rebuilding deployment tooling and adopt Spinnaker (originally built at Netflix) to manage pipelines and checks. Organizations must create psychological safety so teams can experiment and fail, and reward learning behaviors. Draw on open source communities and channels (Slack, mailing lists, GitHub issues) to accelerate work instead of reinventing. A surprising concrete metric offered: reach about eight deployment pipelines before Spinnaker’s value tips for an enterprise.
AI-written summary · about
chapters (13)
- 0:00Welcome and 2020 reflections
- 1:03Focus challenges in 2020
- 2:30Building core business vs reinventing
- 4:56Psychological safety and failure
- 6:18Digital transformation in 2020
- 7:42Open source community benefits
- 9:06DevOps community and values
- 11:13Chopping wood and carrying water
- 12:37Rewarding learning and experimentation
- 13:43Importance of sharing work
- 14:46Self-care and community engagement
- 15:49Spinnaker adoption tips
- 16:31Closing remarks and encouragement
related talks
21mKeynote: Cloud Native CD: Spinnaker and the Culture Behind the Tech
43mAll Aboard: Transforming Software Delivery Using Spinnaker
19mKeynote: Spinnaker - The Future of Your Enterprise CD? Three Reasons Why
01h 04mOpening Keynote [Full]
16mSpinnaker State of the Union (Opening Keynote)
16mIsaac Mosquera (Day 2 Keynote, Armory) - Spinnaker Summit 2019
05mOvercoming Organizational Challenges in Continuous Delivery with Spinnaker
31mHow Spinnaker is Shaping Delivery Excellence at SAP