How to create more business impact with flexible teams - Jan Hegewald, Zalando & Rebekka Beels, Zalando
Usually, Software Engineering teams are organized around a fixed set of components which they develop further and maintain. Such component teams gain a high level of expert knowledge about their services. However, with agile product development, it often is difficult to implement the most important initiatives with such teams. This leads to a situation where the teams do not work on the most relevant business topics but on those for the respective team. At Zalando, we introduced a new model where we shape teams flexibly around business goals to create the highest impact. How we organize these teams and which challenges especially for the software quality need to be addressed, will be explored in this talk.
how to create more
with ﬂexible teams
Founded in 2008.
2,000 colleagues working in 200 tech
delivery teams across Germany, Dublin,
2019 Revenue: >6.5Bn € revenue.
Q2 2020:+ 33% GMV.
More than 34 Mn active customers.
Operating in 17 countries.
Dedicated to sustainability.
Already carbon neutral.
We had stable
TEAM 3PRODUCT OFFER COMPOSITIONREPORTING UI
STOCK INFORMATION PRODUCT INFORMATION PRICE INFORMATION
No longer being specialised requires much
Lacking ownership can be a problem
Unfortunately, there is more than just plain
TYPES OF WORK
Mainly technical tasks with
varying urgency and impact.
Mission-related work that comes
up after the mission ﬁnished and
Design + Deliver for
Mission to accomplish a
Unplanned work on short notice,
mainly based on stakeholder
Work to resolve incidents, but
also to mitigate impact and
prevent further occurrences.
Small Work Package
Tasks that seem too big for
maintenance, but too small for
a Delivery Mission.
Work to deﬁne the technical
solution design for a major
(Discover &) Deﬁne
for Business Goal
Work to identify and
understand a customer
How to create more business impact with
⊖ No focus on biggest impact
⊖ A lot of WIP
⊖ Uneven load on teams
● Deﬁned goal & clear impact
● End-2-end responsibility for goal and aﬀected
components (in given context)
● Duration: 2 weeks - 4 months
● Freedom of choice
Flexible mission teams Process
⊕ Purpose, Mastery, Autonomy
⊕ Output → Outcome
⊕ Standardisation & Quality
⊕ Agile Prioritisation & Delivery
1. Discover &
4. Signing up
8. Switch to next
The information in this presentation has not been independently veriﬁed.
No representation or warranty, express or implied, is made as to the
accuracy or completeness of the presentation and the information
contained herein and no reliance should be placed on such information. No
responsibility is accepted for any liability for any loss howsoever arising,
directly or indirectly, from this presentation or its contents.