Maria Neumayer at StaffPlus London 2023
summary
Autonomous teams keep ownership but drift; a concrete approach creates alignment: form a representative group from each squad, map problems by pain versus complexity, and adopt a documented process for changing production standards so engineers can propose and iterate. Expect slow adoption; add tooling to surface compliance, track a few metrics like delivery speed, and bundle small platform work into product sprints. Design system and language-unification examples show larger payoffs but require leadership buy-in.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:24Building alignment
- 2:49Peer collaboration
- 4:56Team prioritization
- 6:22Leadership alignment
- 8:29Documenting decisions
- 9:54Key takeaways
related talks
30mJames Stanier, Winter Wi, Janet Balneaves a panel discussion at LeadDev London 2023
18mAgile leadership and technical mastery, a harmonious alliance
41mWhy one model can’t fit all creating fulfilling engineering organizations
32mPanel discussion: The journey to building effective engineering teams
58mTeam Topologies Panel
21mAutonomous Teams
33mScaling Impact: Building High-Performing Product Teams Across Borders
32mBuild Teams as an Engineer