How to create more business impact with flexible teams
summary
Zalando replaces component-tied squads with short-lived “missions” that form around business goals, staffing ~15 engineers to run three concurrent missions on average; the Product Offer Platform serves 40,000 offers/sec. Missions last two weeks to four months (typical ~two months) and produced features like a sneaker release calendar, Zalando Lounge in Czechia and local shop onboarding during COVID. Processes include a 4D flow (discover/define/design/deliver), Bob weekly rotation for small ops, maintainer-reviewed PRs and a cleanup window so teams must leave code at equal or better quality.
AI-written summary · about
chapters (10)
- 0:00Introduction to Zalando
- 2:21Advantages of stable teams
- 5:15Drawbacks of stable teams
- 9:26The mission-based model
- 13:51Mission operations
- 18:36Mission lifecycle
- 21:04Practical challenges
- 25:36Handling diverse work types
- 33:15Results and mindset shift
- 36:50Lessons and Q&A
related talks
27mTeam Purpose vs Company Purpose
38mFrom Monolith to Microservices at Zalando
34mAutonomous Teams in Technology Organisations
45mSoftware delivery with skills-based, self organising teams
47mKeynote: Where Teams Choose Autonomy, Accountability and Scaling a Platform
52mCross functional teams are great - but what about the business?
58mDevs fight your Battle! A Pledge for cross-functional Teams
33mScaling Impact: Building High-Performing Product Teams Across Borders