The Scale-up, Autonomy and the Nuclear Submarine
summary
A French-scaleup case study about growing from ~120 to ~500 people and expanding dev teams from ~15 to ~140 across ~60 products, addressing autonomy as a necessity. Describes concrete failures (a divergent local instruments repo, a transient document service handed to a legacy team that couldn’t deploy) and fixes including Domain-Driven Design and splitting the monolith, Azure migrations with stress tests, SRE-style platform work, 20% time refactoring sprints, guilds and contract tests, and experiments in intent-based leadership.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 2:20AUTONOMY IS IMPORTANT
- 3:02WHY START-UP?
- 3:41ENDLESS HISTORY...
- 4:07SOMETIMES DECISION-MAKING...
- 10:02THE SHADOW MICRO-SERVICE
- 11:21#1. THE ENTERPRISE REFERENTIAL
- 12:48TURN THE SHIP AROUND
- 13:12US NAVY: MANAGEMENT BY TENDERNESS
- 13:35A LITTLE RISK NEVERTHELESS...
- 14:30LESSONS FROM DAVID
- 17:03CREATE THE SPACE FOR THINKING
- 20:09FEARS TO ADDRESS
- 21:06IN A PREVIOUS LIFE
- 23:19FROM START-UP... TO SCALE-UP
- 23:38MY ACTION PLAN
- 25:47WHAT WE WERE ABLE TO EXPERIMENT
- 27:27SPLITTING THE MONOLITH
- 28:42XMAS REFACTORING
- 31:45OBJECTIVES & KEY RESULTS (OKR)
- 32:51GUILDS OF..
- 35:27SRE (SITE RELIABILITY ENGINEER) INITIATIVE
- 38:37THE BOY SCOUT ANIMATOR RULE
related talks
30mThe Elements of Scaling
52mDevops @Scale
20mDoing Things the Hard Way
28mFrom Startup to Scale Up: How to Scale Engineering teams
31mScaling
22mOrganising a fast growing DevOps team a real life use case
45mFrom 5 to 100 in Product Development team in just 5 years
21m600 Days of LeSS: A Practice Chronicle