From the Trenches - Remote Scaled Trunk-Based Development
summary
Grown from a six-person co-located Scrum team to a remote 20-developer continuous-flow org, the project adopts trunk-based development with a maintained CI pipeline (green-only, quick revert within ~10 minutes), keeps code in a mono-repo, and splits a monolith into Kafka-driven services. Practices include weekly dev talks, ADRs, two days of per-sprint slack time, and stable streams (five streams ≈20 devs) plus a rotating response stream for ops. The setup reduces meeting overhead and produces steady velocity and deployable mainline.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:45Why big projects fail
- 7:26Think big act small
- 9:13Politics in projects
- 11:03Scaling teams evolutionarily
- 16:21Spring team setup
- 22:03Select time and trunk-based development
- 29:03Summer two teams and monolith split
- 32:13Autumn dynamic feature streams
- 35:12Winter five teams and stable streams
- 43:56Summary and key takeaways
- 46:29Q&A session
related talks
29mTrunk Based Development – Optimizing for Team Performance
36mDistributed & Local: Getting the Best of Both Worlds
42mA Modern Development Culture for a Modern Development Process.
45mPeople and Culture
35mBuilding and Growing an Agile Team
36mFrom massive pull requests to trunk-based development with Ruby
45mFrom 5 to 100 in Product Development team in just 5 years
11mWorking with sharp tools - A case study of Continuous deployment