From Crash to World Class - Scaling Agile
summary
Ericsson scales a greenfield network-management program from 30 to 120 teams in 12 months, hits a global one‑year delay from deployment, CI, architecture and environment failures, then recovers by changing concrete practices: Onboarding 2.0 (quality gates and 30% buddy-team support), replacing the in‑house deployer with kpn deployment tool to cut upgrades from 22 to 3 hours, strengthening CI with queuing and a Docker-based fast feedback framework, centralizing test hardware and adding project managers; result: shipments every three weeks and feature turnaround in six weeks.
AI-written summary · about
chapters (7)
- 0:00ERICSSON AT A GLANCE
- 4:40CYCLE TIME
- 10:53PRODUCTIVITY VERSUS TEAMS
- 12:39MAJOR PROBLEMS
- 15:18HIGH PERFORMING TEAMS
- 17:50TEAM ONBOARDING 2.0
- 19:18CI INFRA AND PRACTICES
related talks
41mSabotaging an Agile Transformation
45mUnlocking technical excellence as a business advantage
37mLeading the Transformation (Applying Agile & DevOps Principles at Scale)
54mA Practical Experiences implementing Business Agility at Ericsson
44mScaling Agile With a Super-Effective Global Delivery Machine
15mAgility at scale: building feature teams for huge products
59mTech leadership, one year after
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World