Leveraging Community To Transform Ford's Software Development Teams
summary
Ford shifts from Cloud Foundry (started 2016) to Kubernetes to handle stateful workloads, reaches production by 2017, and standardizes a single GCP onboarding flow that includes an opinionated pipeline and runnable YAML examples from Kube By Example. Internal programs allocate PowerUp time (hours per week), run weekly demos, and use docs-as-code pipelines; paid project managers and technical engineers scale 600-student experiential projects. Result: instant‑run examples, fewer help requests, faster provisioning, and measurable cultural upskilling.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:01Ford’s Kubernetes investment
- 3:10Kubernetes adoption with community
- 7:00Developer culture transformation
- 12:04Developer journey at Ford
- 16:42Overcoming team fear
- 19:12Culture of innovation
- 21:46Spreading education and excitement
- 29:26Incentivizing knowledge sharing
- 33:19Closing remarks
related talks
17mKeynote: Cloud Foundry: The Open Community's Model Citizen
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
19mKeynote: The Makers of Marvels: How Developers Are Rebuilding the Enterprise, One Brick at a Time
21mKeynote: Engaging Engineers to Delight the Customer and Drive Business Results
23mThe Makers of Marvels: How Developers Are Rebuilding the Enterprise, One Brick at a Time
29mWe Have Always Done It This Way! Now Let’s Try Something Completely Different
27mLessons Learned from Corelogic's Year of Agile Development with Cloud Foundry
29mThe Key to Faster Delivery: Collaborative Platform Strategies