Panel discussion: The journey to building effective engineering teams
summary
Shows how teams map work across 60 teams, selecting 22 problematic teams to visualize supply and demand and prove systemic bottlenecks; uses value stream mapping to expose waste (36‑hour SLA vs eight‑day postal delay) and prioritize fixes. Describes adopting Copilot/CodeWhisperer cautiously because LLM hallucinations matter, shifting SREs to product teams, building an internal platform brand (Collab) with OKRs and usage metrics, and tracking 5–8 year code ownership costs that make pair programming and automated tests pay off.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:08Visualization is the key
- 3:35Map across a long wall
- 5:16Two kinds of people
- 7:50value stream maps
- 10:20engineering practices
- 12:03executive majoring
- 15:40Onboarding
- 16:59Realtime analytics
- 17:50Internal platform themes
- 21:30Audience questions
- 22:56Outsource
- 24:53Programming Question
- 27:42Testing Question
- 30:05Efficiency and Effectiveness
related talks
31mImproving engineering effectiveness: A journey for the entire organization
22mLeading software teams with context (visibility)
46mPanel Discussion | Building Strong Testing Teams: Management, Development, and Diversity
23mManaging diverse engineers for high-impact deliveries
32mDeveloper productivity 2.0
35mBuilding and Growing an Agile Team
43mThe Joys of Managing Engineering Teams
46mBuilding memorable software engineering teams