Team evolution with DDD and Dynamic Reteaming
summary
Vinted aligns domain, teams and architecture by applying Domain-Driven Design and Dynamic Reteaming into a subdomain operating model with mission briefs, code stewardship and platform teams; the domain unit is ~700 people inside a 2,000-person group. Reorgs move from years to two months after iterating 20+ structure models; cross-subdomain work uses short missions (one-person tasks < a day) and A/B-analysis templates to cut lead time. Some feedback loops still fail; evolution continues.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker welcome
- 1:10Context about Vinted and team evolution
- 2:37Initial challenges and systemic issues
- 6:35Exploring Team Topologies approach
- 8:01Monolithic architecture constraints
- 9:50Discovering DDD for architecture and teams
- 13:27Three essential team capabilities
- 15:58Subdomain and mission-based structure
- 20:12Mission briefs and team formation
- 22:56Side missions and code stewardship
- 24:56Feedback loops and iterative learning
- 27:37Achieving faster team shifts
- 29:44Adapting to new strategy and scope
- 33:03Personal learnings and framework insights
- 36:00Embracing complexity and experimentation
- 38:26Q&A and closing remarks
related talks
49mTeam evolution with DDD and Dynamic Reteaming
01h 37mDynamic Reteaming, The Art and Wisdom of Changing Teams
47mDynamic Reteaming at Fast-Changing Companies
41mDynamic Reteaming at Fast Changing Companies
51mDynamic Reteaming at Fast-Growing Companies
47mDynamic Reteaming at fast Growing Companies
46mDynamic Reteaming
49mDomain-Driven Design & Team Topologies For Product-led Organizations