Day 2 Ask the Speaker
summary
Companies describe concrete moves: migrating Jenkins pipelines into Jenkinsfile pipeline as code and to GitLab, running Sonar scans and Selenium tests in source control, and certifying hundreds of AWS engineers. Teams embed ops people with devs, form T‑shaped squads, and allow federated “emerging” services instead of forbidding shadow IT. First end‑to‑end teams take about six to nine months to reach maturity; some efforts fail and are retried. Practices highlighted include BDD with Cucumber for sensitive data and the organizing pattern alignment and autonomy for coarse‑to‑fine service decomposition.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 6:42Managing shadow IT
- 13:20DevOps in siloed environments
- 21:09Behavior-driven development
- 29:10Disney’s IT service plans
- 35:17Monolith to microservices
- 39:05Skills gaps in DevOps
- 45:32Educating business teams
- 48:54DevOps value to leadership
- 51:48Closing & Q&A
related talks
55mBuild your APIs and DevOps Hybrid Skills
54mFrom Code to Customer
23mHow to Build and Deploy Services in the Cloud fireside chat
44mFrom Zero to Federated at the Speed of Jenkins
27mExploring a DevOps Transformation Like a Tester
36mCI/CD BoF: Delivering Quality Quickly
27mConcept to Code to Runtime - Simplify, Enable, Exploit
41mPragmatic DevOps