Slide 1

Slide 1 text

TeamTopologies.com @TeamTopologies Overview of Team Topologies Organizing business and technology teams for fast flow Large Insurance Company - 08 Nov 2023

Slide 2

Slide 2 text

Manuel Pais 2 Independent IT organizational consultant and trainer LinkedIn instructor on CI/CD LinkedIn: manuelpais

Slide 3

Slide 3 text

Team Topologies 3 Organizing business and technology teams for fast flow Matthew Skelton & Manuel Pais IT Revolution Press, 2019 teamtopologies.com/book

Slide 4

Slide 4 text

4 Rapid flow of change

Slide 5

Slide 5 text

5 Rapid feedback from running systems

Slide 6

Slide 6 text

Blockers to Flow 6

Slide 7

Slide 7 text

7 Waiting too long for things to get done?

Slide 8

Slide 8 text

Functional silos 8 Dev UX PMO QA Ops Compliance Functional silos?

Slide 9

Slide 9 text

9 Software too big for your teams?

Slide 10

Slide 10 text

Unclear value streams? 10

Slide 11

Slide 11 text

11 Teams pulled in multiple directions?

Slide 12

Slide 12 text

Multiple stakeholders? 12

Slide 13

Slide 13 text

13 Disengaged teams?

Slide 14

Slide 14 text

14 Confused about how to change things?

Slide 15

Slide 15 text

15 Maybe just one more re-org?

Slide 16

Slide 16 text

Instead, we need to talk about… 26

Slide 17

Slide 17 text

27 Heuristics for Conway’s Law

Slide 18

Slide 18 text

28 Managing team cognitive load

Slide 19

Slide 19 text

29 Patterns for team interactions

Slide 20

Slide 20 text

30 Triggers for change and evolution

Slide 21

Slide 21 text

32 Heuristics for Conway’s Law

Slide 22

Slide 22 text

Who designs the architecture of the software systems? 33

Slide 23

Slide 23 text

34

Slide 24

Slide 24 text

35

Slide 25

Slide 25 text

“Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure.” – Mel Conway, 1968 36 Conway’s Law

Slide 26

Slide 26 text

HR department acts as accidental architects of the software system 37

Slide 27

Slide 27 text

38

Slide 28

Slide 28 text

39

Slide 29

Slide 29 text

40 (reversing) Conway’s Law

Slide 30

Slide 30 text

Design the organisation to mirror the desired architecture (value flow) 41

Slide 31

Slide 31 text

42

Slide 32

Slide 32 text

43

Slide 33

Slide 33 text

44

Slide 34

Slide 34 text

45

Slide 35

Slide 35 text

“if the architecture of the system and the architecture of the organization are at odds, the architecture of the organization wins” – Ruth Malan, 2008 46

Slide 36

Slide 36 text

48 Managing team cognitive load

Slide 37

Slide 37 text

49 Handovers kill flow

Slide 38

Slide 38 text

50 Handovers (can) kill flow

Slide 39

Slide 39 text

51

Slide 40

Slide 40 text

52 Remember A team is a stable, jelled, long-lived group of 5-9 people with a shared purposed aligned to a value stream

Slide 41

Slide 41 text

53 Team-first approach The team is the unit of delivery. Plan, reward, and optimize for the whole team, not individuals.

Slide 42

Slide 42 text

54 Team-first thinking Design for team cognitive load. Choose & evolve adequate boundaries for team ownership.

Slide 43

Slide 43 text

55 https://github.com/TeamTopologies/Team-API-template

Slide 44

Slide 44 text

Fundamental team types Stream-aligned team Enabling team Platform team Complicated subsystem team 56

Slide 45

Slide 45 text

57 enable stream-aligned teams to deliver work with substantial autonomy and reduced cognitive load Platform Team Purpose

Slide 46

Slide 46 text

“A digital platform is a foundation of self-service APIs, tools, services, knowledge and support which are arranged as a compelling internal product.” – Evan Bottcher, 2018 58

Slide 47

Slide 47 text

Fundamental team types Stream-aligned team Enabling team Platform team Complicated subsystem team 60

Slide 48

Slide 48 text

61 team of experts to help bridge capability gaps by mentoring and coaching teams “on the ground” Enabling Team Purpose

Slide 49

Slide 49 text

62 reduce dependencies on experts by teaching rather than executing the work Enabling Team Purpose

Slide 50

Slide 50 text

Fundamental team types Stream-aligned team Enabling team Platform team Complicated subsystem team 63

Slide 51

Slide 51 text

64 building and maintaining part of a system which requires specialist, hard to gain knowledge Complicated Subsystem Team Purpose

Slide 52

Slide 52 text

65

Slide 53

Slide 53 text

🔍 Track dependencies and separate as “blocking” vs “non-blocking” 66

Slide 54

Slide 54 text

⏳ ⏳ Blocking Non- Blocking 67

Slide 55

Slide 55 text

⚠ Compliance mindset shift: Permitting to Enabling 68

Slide 56

Slide 56 text

Team dependencies tracking 69 https://github.com/TeamTopologies/Team-Dependencies-Tracking

Slide 57

Slide 57 text

70 Patterns for team interactions

Slide 58

Slide 58 text

“Problems that arise in organisations are almost always the product of interactions of parts, never the action of a single part.” Russell Ackoff 71

Slide 59

Slide 59 text

72 Well-defined interactions are key to effective teams

Slide 60

Slide 60 text

Team Interaction Modes Collaboration X-as-a-service Facilitation 73

Slide 61

Slide 61 text

74 Team Interaction Modes Collaboration: 2 teams working together X-as-a-Service: 1 provides, 1 consumes Facilitating: 1 team helps another

Slide 62

Slide 62 text

75 Core Interaction Modes Collaboration: 2 teams working together X-as-a-Service: 1 provides, 1 consumes Facilitating: 1 team helps another Why, When, How Long

Slide 63

Slide 63 text

76 Teams we currently interact with: Team Name Interaction Mode Purpose Duration Test Automation Enabling team Facilitating Understand test automation and data mgmt examples for iOS 2 months (from Mar 30 to May 29, 1 day per week) Monitoring & Telemetry Platform team Collaboration Store and visualize data on product features usage 3 weeks (from Apr 13 to Apr 30, 2h per day) Team API example

Slide 64

Slide 64 text

Team Interaction Patterns A D E C B A is collaborating with C C provides X as a service to B D provides X as a service to B E is facilitating with A to enable new capabilities Indicates the flow of change 77

Slide 65

Slide 65 text

Getting started

Slide 66

Slide 66 text

81 Identify the kind of teams you currently have

Slide 67

Slide 67 text

82 Map current teams to fundamental team types

Slide 68

Slide 68 text

83 Limit cognitive load

Slide 69

Slide 69 text

84 Use reverse Conway maneuver

Slide 70

Slide 70 text

85 Define purposeful interactions

Slide 71

Slide 71 text

86 Evolve team structures over time

Slide 72

Slide 72 text

87 Use team interactions for organizational sensing

Slide 73

Slide 73 text

Getting started: Team Topologies Download the infographic: https://teamtopologies.com/getting-started 88

Slide 74

Slide 74 text

Industry Examples teamtopologies.com/examples 89

Slide 75

Slide 75 text

What’s next? 90

Slide 76

Slide 76 text

Free Resources 91 teamtopologies.com/resources (links, slides, video) teamtopologies.com/tools (templates, assessments, etc)

Slide 77

Slide 77 text

academy.teamtopologies.com 92