Slide 1

Slide 1 text

TeamTopologies.com @TeamTopologies Fast Flow Blockers & Pitfalls Manuel Pais co-author of Team Topologies Fast Flow BCN - 18 Jan 2024 Image by Simon Berger

Slide 2

Slide 2 text

Team Topologies 2 Organizing business and technology teams for fast flow Matthew Skelton & Manuel Pais IT Revolution Press (2019) https://teamtopologies.com

Slide 3

Slide 3 text

3 What is fast flow?

Slide 4

Slide 4 text

4 A safe, rapid flow of changes to our services (textbook definition)

Slide 5

Slide 5 text

5 A safe, rapid flow of changes to our systems value to our customers

Slide 6

Slide 6 text

6 A flow-based process delivers information on a regular cadence in small batches (The Principles of Product Development FLOW)

Slide 7

Slide 7 text

8 What prevents fast flow?

Slide 8

Slide 8 text

9 The Classics

Slide 9

Slide 9 text

10 Figure 1.2: Obstacles to Fast Flow

Slide 10

Slide 10 text

11 “We need the new operating model in place in 3 months”

Slide 11

Slide 11 text

12 Re-orgs towards an ideal end state (on paper)

Slide 12

Slide 12 text

13 Continuous org evolution (small batch)

Slide 13

Slide 13 text

14 “Hiring freeze in place but still asked to grow revenue”

Slide 14

Slide 14 text

15 Asking teams to do more with less capacity

Slide 15

Slide 15 text

16 Clarify value streams Make hard product decisions Re-align team responsibilities

Slide 16

Slide 16 text

17 New Kids on the Block

Slide 17

Slide 17 text

18 “We can’t learn new skills because of cognitive load”

Slide 18

Slide 18 text

19 Cognitive load as a blocker to fast flow

Slide 19

Slide 19 text

20 Cognitive load as a constraint on fast flow

Slide 20

Slide 20 text

teamperature.com

Slide 21

Slide 21 text

22 XaaS XaaS XaaS XaaS XaaS XaaS XaaS XaaS XaaS XaaS XaaS XaaS XaaS

Slide 22

Slide 22 text

23 All services are known and stable (on paper)

Slide 23

Slide 23 text

24 Expect most services to be in flux, XaaS as a temporary interaction

Slide 24

Slide 24 text

25 “Teams are locked in to services, we can't adapt to significant market changes”

Slide 25

Slide 25 text

26 Misunderstanding “long lived” as “static” (never changing teams)

Slide 26

Slide 26 text

27 Keep team as an entity, change composition or responsibilities when it makes sense

Slide 27

Slide 27 text

28 “Team Topologies mandates using microservices”

Slide 28

Slide 28 text

29 Feature

Slide 29

Slide 29 text

30 Team-sized services with cognitive load in mind

Slide 30

Slide 30 text

33

Slide 31

Slide 31 text

academy.teamtopologies.com

Slide 32

Slide 32 text

35 Copyright © Team Topologies Ltd 2024. All rights reserved. teamtopologies.com