Becoming the bottleneck
summary
Five years on one codebase creates a single-person queue: five–six active projects, two simultaneous stand-ups, and a calendar as full as a PM’s, which leads to delayed handoffs and features stuck in another team’s backlog — e.g., a preview-image pipeline that generates and stores 6k thumbnails but never gets surfaced because the API owner never prioritizes the integration. The cure is operational: enforce low barrier of entry, push pull requests across team boundaries, add tests/monitoring and clear documentation so ownership can be handed off and meetings reduced.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:18How did it happen
- 3:15A few years back
- 4:55New projects
- 8:07Accumulation of responsibility
- 9:46Abandon ship?
- 11:57Things to try?
- 13:22Open source
- 14:48Kanban across contexts 1
- 17:02Tales from reality
- 19:09Kanban across contexts 4
- 20:01Piling up
- 21:11Challenges
- 22:14Don't adopt everything
- 22:44Horisontal vs Feature teams
- 23:36Components do not auto-follow
- 24:29Guilds
- 25:09Full agile
- 27:27Conclusion
related talks
20mDoing Things the Hard Way
15mStories from the Trenches
46mLeading Distributed Teams
46mWhen Software Becomes Everyone's Job
18mAgile leadership and technical mastery, a harmonious alliance
23mManaging diverse engineers for high-impact deliveries
25mTransforming legacy software
01h 01mFixing the Ultimate Legacy System: You