Beyond the Spotify Model - using Team Topologies for fast flow and organization evolution - DTX Manchester 2024

Slide 1

Slide 1 text

Beyond the Spotify model using Team Topologies for fast ﬂow and organization evolution Matthew Skelton, Conﬂux - co-author of Team Topologies Keynote at DTX Manchester | 2024-05-23 K37

Slide 2

Slide 2 text

Photo goes here Matthew Skelton Founder at Conﬂux Co-author of Team Topologies “Ecosystem engineering” LinkedIn: linkedin.com/in/matthewskelton Mastodon: mastodon.social/@matthewskelton 2

Slide 3

Slide 3 text

3 Book signing today Eﬁcode stand D54 @ 13:00

Slide 4

Slide 4 text

4 Would you like $millions in extra budget without having any lay-oﬀs or oﬀshoring?

Slide 5

Slide 5 text

5 c.500 people

Slide 6

Slide 6 text

6 $16 million +

Slide 7

Slide 7 text

7 Unneeded coupling: c.$30k to $60k+ PPPY

Slide 8

Slide 8 text

8 Unblock innovation via fast ﬂow

Slide 9

Slide 9 text

9 We help you to unblock innovation via fast ﬂow and Team Topologies Coaching & consulting | Cohort learning | Community conﬂuxhq.com

Slide 10

Slide 10 text

Team Topologies Organizing business and technology teams for fast ﬂow Matthew Skelton & Manuel Pais IT Revolution Press, September 2019 Order via stores worldwide: teamtopologies.com/book 10 Over 150k copies sold!

Slide 11

Slide 11 text

“...innovative tools and concepts for structuring the next generation digital operating model” Charles T. Betz, Principal Analyst, Forrester Research 11

Slide 12

Slide 12 text

topology the way in which constituent parts are interrelated or arranged Greek: τοπολογία (τόπος == ‘place’) 12

Slide 13

Slide 13 text

Origins - DevOps Topologies 13 CC BY-SA devopstopologies.com conﬂuxhq.com/devops-topologies

Slide 14

Slide 14 text

14 Philip Fisher-Ogden, Director of Engineering at Netﬂix: “thanks for your insightful articulations of devops topologies. They inspired many discussions and helped us to think about what model Netﬂix teams could be/are using.” https://twitter.com/philip_pfo/status/999074792123740160

Slide 15

Slide 15 text

15 Crystal Hirschorn, Director of Engineering at Condé Nast International “Your topological models resonated extremely well on both the Dev and Ops side btw! I like the balanced arguments, e.g. diﬀerent perspectives, for each pattern.” https://twitter.com/cfhirschorn/status/1103387659890819073

Slide 16

Slide 16 text

Team Topologies 📗 16 Research over 5 years across multiple industry sectors Informed by 50+ peer-reviewed journal articles 30+ client organizations - consulting and training since 2013 with orgs in CN, EU, IN, US, UK, + Book: 12+ case studies from well-known organizations

Slide 17

Slide 17 text

Team Topologies - since 2019 17 Top 10 ‘Best Product Management Books’ (Book Authority) Adopted by 1000s of organizations worldwide: JP Morgan, ClearBank, Fidelity, Docker, Zalando, NatWest Group, USAF, GOV.UK, … Unlocking $10bn+ extra value in organizations around the world annually

Slide 18

Slide 18 text

Beyond the Spotify model using Team Topologies for fast ﬂow and organisation evolution 18

Slide 19

Slide 19 text

The Spotify Model 19 Limitations of the Spotify Model Team Topologies Getting started

Slide 20

Slide 20 text

Slide 21

Slide 21 text

Slide 22

Slide 22 text

The Spotify model of team design for software delivery 22

Slide 23

Slide 23 text

23 Henrik Kniberg & Anders Ivarsson, 2012 https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScaling.pdf

Slide 24

Slide 24 text

24 The Spotify model Squad: semi-autonomous delivery team Tribe: family of Squads - related work Chapter: line management within a Tribe Guild: cross-Tribe interest/specialist group

Slide 25

Slide 25 text

25 The Spotify model has been hugely helpful to 100s of organizations

Slide 26

Slide 26 text

The Spotify model helps to... 26

Slide 27

Slide 27 text

27 Encourage ﬂow of value

Slide 28

Slide 28 text

28 Establish and clarify team responsibilities

Slide 29

Slide 29 text

29 Promote good kinds of team collaboration

Slide 30

Slide 30 text

30 Plan and budget for cross-team enablers

Slide 31

Slide 31 text

31 The Spotify model helps to Encourage ﬂow of value Establish and clarify team responsibilities Promote good kinds of team collaboration Plan and budget for cross-team enablers

Slide 32

Slide 32 text

Limitations of the Spotify model 32

Slide 33

Slide 33 text

“This article is only a snapshot of our current way of working - a journey in progress, not a journey completed. By the time you read this, things have already changed.” - Kniberg & Ivarsson 33

Slide 34

Slide 34 text

There is No Spotify Model 34 Marcin Floryan, 2016 https://www.infoq.com/presentations/spotify-culture-stc

Slide 35

Slide 35 text

35 What’s missing from the (non-existent) Spotify model?

Slide 36

Slide 36 text

36 Team-ﬁrst thinking and cognitive load

Slide 37

Slide 37 text

37 Heuristics for Conway’s Law

Slide 38

Slide 38 text

38 Patterns for team interactions

Slide 39

Slide 39 text

39 Sensing for evolution

Slide 40

Slide 40 text

Team Topologies 📗 40

Slide 41

Slide 41 text

41 Team Topologies helps with Team-ﬁrst thinking and cognitive load Heuristics for Conway’s Law Patterns for team interactions Triggers for change and evolution

Slide 42

Slide 42 text

42 Team-ﬁrst thinking and cognitive load

Slide 43

Slide 43 text

43 Team-ﬁrst thinking

Slide 44

Slide 44 text

44 Team-ﬁrst thinking The team is the means of delivery

Slide 45

Slide 45 text

45 Team-ﬁrst thinking Design for team cognitive load

Slide 46

Slide 46 text

46 Team-ﬁrst thinking Discover boundaries for team ownership

Slide 47

Slide 47 text

47 Team-ﬁrst thinking Physical and digital workspace

Slide 48

Slide 48 text

48 Team-ﬁrst Thinking The team is the means of delivery Design for team cognitive load Choose boundaries for team ownership Physical and digital workspace

Slide 49

Slide 49 text

49 Heuristics for Conway’s Law

Slide 50

Slide 50 text

50 Conway’s Law Any organization that designs a system (deﬁned broadly) will produce a design whose structure is a copy of the organization's communication structure. — Melvin E. Conway

Slide 51

Slide 51 text

51 Conway’s Law Heuristic for ‘natural’ expected design

Slide 52

Slide 52 text

52 Conway’s Law Mirroring in tech system + human system

Slide 53

Slide 53 text

53 Conway’s Law Reverse Conway to mitigate worst eﬀects

Slide 54

Slide 54 text

54 Conway’s Law Constraint on solution search space

Slide 55

Slide 55 text

55 Conway’s Law Heuristic for ‘natural’ expected design Mirroring in tech system + human system Reverse Conway to mitigate worst eﬀects Constraint on solution search space

Slide 56

Slide 56 text

56 Patterns for team interactions

Slide 57

Slide 57 text

57 Team interactions

Slide 58

Slide 58 text

58 Team interactions 3 deﬁned Interaction Modes

Slide 59

Slide 59 text

59 Team interactions Collaboration: 2 teams working together

Slide 60

Slide 60 text

60 Team interactions X-as-a-Service: 1 provides, 1 consumes

Slide 61

Slide 61 text

61 Team interactions Facilitating: 1 team helps another

Slide 62

Slide 62 text

62 Team interactions 3 deﬁned Interaction Modes Collaboration: 2 teams working together X-as-a-Service: 1 provides, 1 consumes Facilitating: 1 team helps another

Slide 63

Slide 63 text

4 fundamental topologies 63 Stream-aligned team Enabling team Complicated Subsystem team Platform team grouping

Slide 64

Slide 64 text

4 fundamental topologies 64 Flow of change

Slide 65

Slide 65 text

3 core interaction modes 65 X-as-a-Service Facilitating Collaboration Flow of change

Slide 66

Slide 66 text

66 Sensing for evolution

Slide 67

Slide 67 text

67 Sensing for evolution

Slide 68

Slide 68 text

68 Sensing for Evolution Not all teams in the org look the same

Slide 69

Slide 69 text

69 Sensing for evolution Discover, then push to Platform

Slide 70

Slide 70 text

70 Sensing for evolution Awkward team interactions are signals

Slide 71

Slide 71 text

71 Sensing for evolution Evolve the org with changing ecosystem

Slide 72

Slide 72 text

72 Sensing for evolution Not all teams in the org look the same Discover, then push to Platform Awkward team interactions are signals Evolve the org with changing ecosystem

Slide 73

Slide 73 text

Getting started with the Team Topologies approach 73

Slide 74

Slide 74 text

74 Explicit team cognitive load

Slide 75

Slide 75 text

How well can the team as a unit “grok” the systems they own and develop? Push some things into a Platform? Are skills or capabilities missing? Explicit cognitive load 75

Slide 76

Slide 76 text

76 Large Conway mismatches

Slide 77

Slide 77 text

Are there major mismatches between the team interactions and the required software / system architecture? What could be easily adjusted? Large Conway mismatches 77

Slide 78

Slide 78 text

78 Team interactions

Slide 79

Slide 79 text

What would change if we adopted the 3 team interaction patterns? Collaboration, X-as-a-Service, Facilitating How would teams react & behave? Team Interactions 79

Slide 80

Slide 80 text

80 Thinnest viable platform

Slide 81

Slide 81 text

“A TVP is a careful balance between keeping the platform small and ensuring that the platform is helping to accelerate and simplify software delivery for teams building on the platform.” (p.101, Team Topologies) 81

Slide 82

Slide 82 text

How is your Platform deﬁned? What is the thinnest platform that could work? What’s needed to run an support it? Thinnest Viable Platform 82

Slide 83

Slide 83 text

Review 83

Slide 84

Slide 84 text

Team Topologies helps with… 84

Slide 85

Slide 85 text

85 Team-ﬁrst thinking and cognitive load

Slide 86

Slide 86 text

86 Heuristics for Conway’s Law

Slide 87

Slide 87 text

87 Patterns for team interactions

Slide 88

Slide 88 text

88 Sensing for evolution

Slide 89

Slide 89 text

89 Unblock innovation via fast ﬂow

Slide 90

Slide 90 text

90 Accelerate your journey today! Join the waitlist: Or sign up via conﬂuxhq.com

Slide 91

Slide 91 text

91 We help you to unblock innovation via fast ﬂow and Team Topologies Coaching & consulting | Cohort learning | Community conﬂuxhq.com