Building memorable software engineering teams
summary
A practical playbook from Docker that codifies four priorities—company values (e.g., developer obsession, bias to action, humility and open collaboration), team topology, distinct manager vs engineer career ladders, and remote hiring/salary strategy. It uses concrete metrics (Dunbar threshold ~150, team sizes of 5–10, 40% of teams fully autonomous) and describes reorganizing around stream‑aligned and platform teams, applying Team Topologies, XP practices, and remote policies to remove Conway‑law bottlenecks and restore engineering velocity during a major reorg.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:47Taille d'organisation
- 13:38Organisation par défaut
- 16:17La loi de Conway
- 24:36Topologie d'Equipe
- 26:25Software Engineering Ladder
- 29:38Engineering Management Ladder
- 31:35Impact equivalent
related talks
59mTeam Topologies Methodologies - Renavigating & Rescaling the Industry Standard for Containerization
01h 06mLeading successful remote teams
45mReflections on How to Build and Run an Effective Software Engineering Organization
32mPanel discussion: The journey to building effective engineering teams
40mEnabling teams for happier and more productive engineers
16mEnlarge your team!
48mHow to Build and Maintain Engineering Teams Focused on Product through Culture and Values
30mThe Art of Team Design