- @matthewpskelton Beyond the Spotify model Matthew Skelton, Conflux · 2019-04-10 ·...

TeamTopologies.com@TeamTopologies

Beyond the Spotify modelusing Team Topologies for

organisation dynamics with software deliveryMatthew Skelton, Conflux

co-author of Team Topologies - @matthewpskelton

IPEXPO Mancs, 03 April 2019, Manchester

2

The Spotify Model

Limitations

Team Topologies

Getting started

3

4

The Spotify model of team design for

software delivery5

6

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

7

The Spotify modelSquad: semi-autonomous delivery team

Tribe: family of Squads - related work

Chapter: line management within a Tribe

Guild: cross-Tribe interest/specialist group

8

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

The Spotify model helps to...

9

10

Encourage flow of change

11

Establish and clarify team

responsibilities

12

Promote good kinds of team collaboration

13

Plan and budget for cross-team

enablers

14

The Spotify model helps toEncourage flow of change

Establish and clarify team responsibilities

Promote good kinds of team collaboration

Plan and budget for cross-team enablers

@matthewpskelton / @TeamTopologies

Limitations of the Spotify model

15

“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

16

There is No Spotify Model

17

Marcin Floryan, 2016https://www.infoq.com/presentations/spotify-culture-stc

18

Software sizing and cognitive load

19

Heuristics for Conway’s Law

20

Patterns for team interactions

21

Triggers for change and evolution

22

We also need to addressSoftware sizing and cognitive load

Heuristics for Conway’s Law

Patterns for team interactions

Triggers for change and evolution

@matthewpskelton / @TeamTopologies

Team Topologies

23

topology

the way in which constituent parts are interrelated or arranged

Greek: τοπολογία (τόπος == ‘place’)

24

Team Topologies

25

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

Origins - DevOps Topologies

26

CC BY-SA devopstopologies.com

@matthewpskelton / @TeamTopologies

27

Philip Fisher-Ogden, Director of Engineering at Netflix:

“thanks for your insightful articulations of devops topologies. They inspired many discussions and helped us to think about what model Netflix teams could be/are using.”

https://twitter.com/philip_pfo/status/999074792123740160

28

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. different perspectives, for each pattern.”

https://twitter.com/cfhirschorn/status/1103387659890819073

Team Topologies

29

Organizing business and technology teams for fast flow

Matthew Skelton and Manuel PaisPublication date: Sept 2019IT Revolution Press

Pre-order from Amazon.com: https://teamtopologies.com/book

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

30

Team Topologies for fast flow

Conway’s LawTeam-first Thinking

Team Interactions

Sensing for Evolution

31

32

Software sizing and cognitive load

33

Team-first Thinking

34

Team-first Thinking

The team is the means of delivery

35

Team-first Thinking

Design for team cognitive load

36

Team-first Thinking

Choose boundaries for team ownership

37

Team-first Thinking

Physical and digital workspace

38

Team-first Thinking

The team is the means of deliveryDesign for team cognitive load

Choose boundaries for team ownershipPhysical and digital workspace

@matthewpskelton / @TeamTopologies

39

Heuristics for Conway’s Law

40

Conway’s Law

41

Conway’s Law

Heuristic for ‘natural’ expected design

42

Conway’s Law

Mirroring in tech system + human system

43

Conway’s Law

Reverse Conway to mitigate worst effects

44

Conway’s Law

Constraint on solution search space

45

Conway’s Law

Heuristic for ‘natural’ expected designMirroring in tech system + human systemReverse Conway to mitigate worst effects

Constraint on solution search space

@matthewpskelton / @TeamTopologies

46

Patterns for team interactions

47

Team Interactions

48

Team Interactions

3 defined Interaction Modes

49

Team Interactions

Collaboration: 2 teams working together

50

Team Interactions

X-as-a-Service: 1 provides, 1 consumes

51

Team Interactions

Facilitating: 1 team helps another

52

Team Interactions

3 defined Interaction ModesCollaboration: 2 teams working together

X-as-a-Service: 1 provides, 1 consumesFacilitating: 1 team helps another

@matthewpskelton / @TeamTopologies

4 fundamental topologies

53

Stream-aligned team

Enabling team

Complicated Subsystem team

Platform team

4 fundamental topologies

54

Flow of change

3 core interaction modes

55

Flow of change

X-as-a-Service

Facilitating

Collaboration

56

Triggers for change and evolution

57

Sensing for Evolution

58

Sensing for Evolution

Not all teams in the org look the same

59

Sensing for Evolution

Discover, then push to Platform

60

Sensing for Evolution

Awkward team interactions are signals

61

Sensing for Evolution

Evolve the org with changing ecosystem

62

Sensing for Evolution

Not all teams in the org look the sameDiscover, then push to Platform

Awkward team interactions are signalsEvolve the org with changing ecosystem

@matthewpskelton / @TeamTopologies

Getting started with the Team Topologies

approach63

Getting started

64

Explicit cognitive load

Large Conway mismatches

Team Interactions

Thinnest Viable Platform

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

65

Getting started

66

Explicit cognitive load

Large Conway mismatches

Team Interactions

Thinnest Viable Platform

Are there major mismatches between the team interactions and the required software / system architecture?

What could be easily adjusted?

Large Conway mismatches

67

Getting started

68

Explicit cognitive load

Large Conway mismatches

Team Interactions

Thinnest Viable Platform

What would change if we adopted the 3 team interaction patterns?

Collaboration, X-as-a-Service, Facilitating

How would teams react & behave?

Team Interactions

69

Getting started

70

Explicit cognitive load

Large Conway mismatches

Team Interactions

Thinnest Viable Platform

How is your Platform defined?

What is the thinnest platform that could work?

What’s needed to run an support it?

Thinnest Viable Platform

71

Getting started

72

Explicit cognitive load

Large Conway mismatches

Team Interactions

Thinnest Viable Platform

Review

73

74

The Spotify model helps toEncourage flow of change

Establish and clarify team responsibilities

Promote good kinds of team collaboration

Plan and budget for cross-team enablers

@matthewpskelton / @TeamTopologies

75

We also need to addressSoftware sizing and cognitive load

Heuristics for Conway’s Law

Patterns for team interactions

Triggers for change and evolution

@matthewpskelton / @TeamTopologies

Team Topologies for fast flow

Conway’s LawTeam-first Thinking

Team Interactions

Sensing for Evolution

76

Getting started

77

Explicit cognitive load

Large Conway mismatches

Team Interactions

Thinnest Viable Platform

Sign up for news and tips:

TeamTopologies.com

78

Thank you!info@teamtopologies.com

79

Matthew Skelton, Conflux@matthewpskelton

Manuel Pais, Independent@manupaisable

Copyright © Conflux Digital Ltd 2018-2019. All rights reserved.Registered in England and Wales, number 10890964

Icons made by Freepick from www.flaticon.com - used under license