Slide 1

Slide 1 text

TeamTopologies.com @TeamTopologies Business and Technical Agility with Team Topologies (dealing with legacy systems) Matthew Skelton co-author of Team Topologies @matthewpskelton Reliance Jio - 16 September 2021

Slide 2

Slide 2 text

2 Manuel Pais Independent IT organizational consultant and trainer Ex-dev, ex-build manager, ex-tester, ex-QA lead Twitter: @manupaisable LinkedIn: manuelpais Matthew Skelton Founder at Conflux Experience as: software developer, technical director, change enabler, conference organizer... Twitter: @matthewpskelton LinkedIn: matthewskelton

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

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

Slide 5

Slide 5 text

5 What is business agility? Being agile, not doing ‘Agile’ Valuable: product mindset Team Topologies examples

Slide 6

Slide 6 text

How does Team Topologies help with business & technical agility? 6

Slide 7

Slide 7 text

Team Topologies encourages decoupling of business concepts to help make the organization more responsive

Slide 8

Slide 8 text

Team Topologies patterns help to turn blocking compliance checks into self-service, flow-aligned, API-driven checks

Slide 9

Slide 9 text

Team Topologies is partly a sense-making approach to help organizations gain situational awareness and therefore agility

Slide 10

Slide 10 text

Team Topologies helps the organization to focus tightly on its core mission via streams and limiting team cognitive load

Slide 11

Slide 11 text

11 What is business agility? Being agile, not doing ‘Agile’ Valuable: product mindset Team Topologies examples

Slide 12

Slide 12 text

What is business agility? 12

Slide 13

Slide 13 text

Business Agility: the ability to respond rapidly* to changing internal and external conditions (* in hours)

Slide 14

Slide 14 text

14 Photo by Daniele Levis Pelusi on Unsplash Remote-first

Slide 15

Slide 15 text

15 Photo by chuttersnap on Unsplash Speed of change: technology, climate, geopolitical

Slide 16

Slide 16 text

16 Photo by chuttersnap on Unsplash Increased global and local competition

Slide 17

Slide 17 text

Questions to answer How would we optimize for a fast flow of change?

Slide 18

Slide 18 text

Questions to answer How would we make sure we focus on user needs?

Slide 19

Slide 19 text

Questions to answer How would we easily ‘course-correct’ when we need to adjust?

Slide 20

Slide 20 text

26 What is business agility? Being agile, not doing ‘Agile’ Valuable: product mindset Team Topologies examples

Slide 21

Slide 21 text

Being agile, not doing ‘Agile’

Slide 22

Slide 22 text

28 State of DevOps reports 2013 2014 2015 2016 2017 2018 2019 Annual survey of 1000-5000 IT professionals worldwide using rigorous statistical methods 2020 2021

Slide 23

Slide 23 text

29 State of DevOps 2019 Analysis from responses of over 31,000 IT professionals worldwide over 6 years “an independent view into the practices and capabilities that drive high performance” + “Four Key Metrics”

Slide 24

Slide 24 text

30 State of DevOps 2019 “The use of cloud… is predictive of software delivery performance and availability.” “High performers favor strategies that create community structures at both low and high levels in the organization...”

Slide 25

Slide 25 text

31 State of DevOps 2019 “Heavyweight change approval processes, such as change approval boards, negatively impact speed and stability. In contrast, having a clearly understood process for changes drives speed and stability, as well as reductions in burnout.”

Slide 26

Slide 26 text

32 State of DevOps 2019 Key technical practices ● Lightweight change process ● Real DR testing ● Maintainable code ● Loosely-coupled systems ● Monitoring ● Trunk-based development ● Deployment automation

Slide 27

Slide 27 text

Accelerate Building and Scaling High Performing Technology Organizations Nicole Forsgren, Jez Humble, Gene Kim IT Revolution Press, 2018 Order via stores worldwide: https://itrevolution.com/book/accelerate/ 33

Slide 28

Slide 28 text

34 4 key metrics: ‘Accelerate’ lead time deployment frequency Mean Time To Restore change fail percentage

Slide 29

Slide 29 text

35 State of DevOps 2021 “...principles and patterns from Team Topologies are helping organisations in every sector and geography become more high-performing.” https://puppet.com/resources/report/2021-state-of-devops-report/

Slide 30

Slide 30 text

36 Fast feedback via deployment pipelines

Slide 31

Slide 31 text

37 Good technical practices (TDD, …)

Slide 32

Slide 32 text

38 Team ownership of software & services

Slide 33

Slide 33 text

39 Configuration in version control (Git)

Slide 34

Slide 34 text

40 Cloud-native: transparent in operation

Slide 35

Slide 35 text

41 Cloud-native: designed for automation

Slide 36

Slide 36 text

43 Re-aligned architecture

Slide 37

Slide 37 text

45 Domain-driven design (DDD) Untangle business concepts for faster flow

Slide 38

Slide 38 text

47 Wardley Maps Increase situational awareness and apply the right techniques - custom/product/utility

Slide 39

Slide 39 text

49 Team Topologies Fast flow, rapid feedback, team interactions, org evolution, team cognitive load, ...

Slide 40

Slide 40 text

50 Rapid flow of change

Slide 41

Slide 41 text

51 Rapid feedback from running systems

Slide 42

Slide 42 text

52 Handovers kill flow

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

54

Slide 45

Slide 45 text

55

Slide 46

Slide 46 text

56 Flow of change

Slide 47

Slide 47 text

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

Slide 48

Slide 48 text

⏳ ⏳ Blocking Non- Blocking

Slide 49

Slide 49 text

Remove barriers to flow: hand-offs, approval gates, manual inspections Replace with self-service APIs 59

Slide 50

Slide 50 text

⚠ Compliance mindset shift: Permitting to Enabling 60

Slide 51

Slide 51 text

61

Slide 52

Slide 52 text

“What would be needed for us to be compliant with security/finance/PII rules with multiple, decoupled, rapid flows of change?” (Self-service APIs) Scaled Expertise 62

Slide 53

Slide 53 text

Compliance as Code (API) 63 Flow of change Domain experts as Enabling team for compliance / governance

Slide 54

Slide 54 text

64 What is business agility? Being agile, not doing ‘Agile’ Valuable: product mindset Team Topologies examples

Slide 55

Slide 55 text

The value of a product mindset

Slide 56

Slide 56 text

Product: Holistic User Experience Functionality + Design + Monetization + Content – Marty Cagan, 2010 66 Source: https://svpg.com/defining-product/

Slide 57

Slide 57 text

67

Slide 58

Slide 58 text

68 A product is optional to use - no-one is forced to use the product

Slide 59

Slide 59 text

69

Slide 60

Slide 60 text

70 A product is carefully designed and curated

Slide 61

Slide 61 text

71

Slide 62

Slide 62 text

72 A product simplifies something for users

Slide 63

Slide 63 text

73

Slide 64

Slide 64 text

74 A product evolves to take advantage of technology changes

Slide 65

Slide 65 text

A strong focus on user needs drives good software #UX

Slide 66

Slide 66 text

The software should ‘get out of the way’ - design for usability

Slide 67

Slide 67 text

⚠ Product Management for internal platforms 77

Slide 68

Slide 68 text

78

Slide 69

Slide 69 text

79 A platform is optional to use - no team is forced to use the platform

Slide 70

Slide 70 text

Platforms must advocate for their platform product and “market” it to internal teams (User Personas, UX, talking...) Internal Marketing 80

Slide 71

Slide 71 text

81 A platform is a curated experience for engineers (the customers of the platform).

Slide 72

Slide 72 text

82 What is business agility? Being agile, not doing ‘Agile’ Valuable: product mindset Team Topologies examples

Slide 73

Slide 73 text

Team Topologies examples

Slide 74

Slide 74 text

[Before Team Topologies]

Slide 75

Slide 75 text

85

Slide 76

Slide 76 text

86 Challenge Hiscox needed to increase the pace of change to release new products quickly into a highly competitive and fast-moving market. Solution Introduced DevOps practices and infrastructure automation

Slide 77

Slide 77 text

87 Results ● Reduced cost per release on a major app by 97%. ● Release cycle improved from 10 weeks per deployment to 50 deployments per week. ● Reduced time per release by 89%. ● Reduced staff required to release by 75%. https://www.uk.cdw.com/files/2515/3555/5104/Hiscox-Case-Study-20180411.pdf

Slide 78

Slide 78 text

88 https://techbeacon.com/devops/5-lessons-how-devops-cloud-reinvented-it-ops-hiscox Jonathan Fletcher, CTO at Hiscox Insurance

Slide 79

Slide 79 text

89 < 2015 2016 2017 data center flooded data storage failures 2015 POCs for cloud Infrastructure as Code - config in version control New capabilities: upskilling and awareness Ops: learn to code Dev: learn infra Migrate core UK policy admin to cloud Rework apps to be more cloud-native https://blog.weareconvivio.com/how-hiscox-insurance-adopted-agile-working-in-a-0-5bn-bet-on-the-cloud-d613955d3ef9

Slide 80

Slide 80 text

90 https://www.youtube.com/watch?v=V4FQjOyKwRo&feature=youtu.be&t=662

Slide 81

Slide 81 text

91 “DevOps has meant big improvements in reliability and visibility, and those lead directly to improved productivity and speed of releases. With more reliability in your delivery process, you get a faster pace of change.” Jonathan Fletcher, CTO at Hiscox Insurance https://www.uk.cdw.com/files/2515/3555/5104/Hiscox-Case-Study-20180411.pdf

Slide 82

Slide 82 text

92 “We decided to limit DevOpsifying to our crown jewels: the five applications we care about most.” Jonathan Fletcher, CTO at Hiscox Insurance https://www.uk.cdw.com/files/2515/3555/5104/Hiscox-Case-Study-20180411.pdf

Slide 83

Slide 83 text

93 “We moved people into roles that were more aligned with the business unit — “product focused” is probably the right term, as I mentioned earlier. Each product team has its own business analysts, developers, testers and other functions as needed. These teams are the masters of their own destiny, rather than trying to beg and borrow capacity from a big group function.” Jonathan Fletcher, CTO at Hiscox Insurance https://www.uk.cdw.com/files/2515/3555/5104/Hiscox-Case-Study-20180411.pdf

Slide 84

Slide 84 text

94 “We needed a team to evangelize and support the adoption of DevOps. … We created a platform services team (which I run). That team learned continuous delivery and other DevOps practices...” Jonathan Fletcher, CTO at Hiscox Insurance

Slide 85

Slide 85 text

95 Results ● Reduced cost per release on a major app by 97%. ● Release cycle improved from 10 weeks per deployment to 50 deployments per week. ● Reduced time per release by 89%. ● Reduced staff required to release by 75%. https://www.uk.cdw.com/files/2515/3555/5104/Hiscox-Case-Study-20180411.pdf

Slide 86

Slide 86 text

Case studies in the TT book 96

Slide 87

Slide 87 text

97 ...

Slide 88

Slide 88 text

Sept 2021: 24 months since publication of TT Photo by noor Younis on Unsplash 98

Slide 89

Slide 89 text

Industry examples on the TT website 99

Slide 90

Slide 90 text

100

Slide 91

Slide 91 text

Organizations that Matthew and Manuel have worked with since 2019... 101

Slide 92

Slide 92 text

A large European banking group A major cloud technology company GOV: Brazil, Canada, Norway, UK, US Several major telecoms companies A scale-up in Open Banking An aerospace laboratory Healthcare providers Several mortgage companies 102

Slide 93

Slide 93 text

Case Study 103

Slide 94

Slide 94 text

● Founded 2005 ● 70 stores in the UK ● £260m revenue ● 2500 employees ● 2019: changes to make IT more responsive 104

Slide 95

Slide 95 text

High fragmentation of work and focus 105 Jan 2019

Slide 96

Slide 96 text

Identify boundaries - business domain 106 m id-2019

Slide 97

Slide 97 text

Team Topologies at DOES London 2019 107 Jun 2019

Slide 98

Slide 98 text

Team Topologies for Product Managers 108 Jun 2019 “The Product Managers from each team took special interest in the team interaction types as it helped them to have useful, directed conversations about upcoming work, they could essentially fact-check their different roadmaps and make sure that the interactions required were lined up in advance. “ -- Andy Norton, Software Development Manager, Footasylum

Slide 99

Slide 99 text

Align to Team Topologies concepts 109 Aug 2019

Slide 100

Slide 100 text

Combine with Wardley Mapping 110 Jan 2020

Slide 101

Slide 101 text

Adopt the Thinnest Viable Platform 112 Feb 2020 Static data fine to begin with: shops rarely move!

Slide 102

Slide 102 text

Clarity of purpose from team types 113 Feb 2020

Slide 103

Slide 103 text

Concepts ● Stream-aligned (business domain) ● Thinnest Viable Platform ● Evolving teams and interactions ● Combine with Wardley Mapping 114 teamtopologies.com/examples

Slide 104

Slide 104 text

● Product Mgt superpowers ● Effective comms during COVID-19 ● Responsive, autonomous teams Results 115 teamtopologies.com/examples

Slide 105

Slide 105 text

“the interaction modes defined by Team Topologies gave us real insight into how we could maintain effective practices, and also cross-team collaboration.“ -- Andy Norton, Software Development Manager, Footasylum 116

Slide 106

Slide 106 text

Thanks to: Paul Martin IT Director, Footasylum Andy Norton Software Development Manager, Footasylum 117

Slide 107

Slide 107 text

Dealing with legacy architectures

Slide 108

Slide 108 text

Use loosely-coupled, logically independent, asynchronous, message-driven services. 147

Slide 109

Slide 109 text

Use loosely-coupled, logically independent, asynchronous, message-driven services. 148 Smalltalk (1960s) Erlang (1980s)

Slide 110

Slide 110 text

“...start adopting product architectures that permit work to flow in small, decoupled batches. These loosely coupled architectures, with stable interfaces, enable us to work in parallel on many subsystems.” - Don Reinertsen 149 The Principles of Product Development Flow: Second Generation Lean Product Development (p. 127 - Principle B15)

Slide 111

Slide 111 text

150 Standard, modern version control Photo by Clay Banks on Unsplash

Slide 112

Slide 112 text

151 All changes via a deployment pipeline Photo by Markus Winkler on Unsplash

Slide 113

Slide 113 text

152 4 Team Types: clarity of purpose and behavior Photo by Dev Benjamin on Unsplash

Slide 114

Slide 114 text

153 Team Interaction Modes Photo by Van Tay Media on Unsplash

Slide 115

Slide 115 text

Legacy Adaptation Patterns

Slide 116

Slide 116 text

155 Split off services by domain (DDD) Photo by Jeremy Bezanger on Unsplash

Slide 117

Slide 117 text

156 API wrapper + outer services Photo by Brett Jordan on Unsplash

Slide 118

Slide 118 text

157 Eventual consistency Photo by NeONBRAND on Unsplash

Slide 119

Slide 119 text

158 Branch By Abstraction Photo by sainan wang on Unsplash

Slide 120

Slide 120 text

https://martinfowler.com/articles/patterns-legacy-displacement/ Patterns of Legacy Displacement

Slide 121

Slide 121 text

Case Study 160

Slide 122

Slide 122 text

● Founded in 1847 ● Insurance sector ● Norway and Baltics ● 4000 employees ● Cloud/DevOps transformation 2015-now 161

Slide 123

Slide 123 text

2015 162 Project-based Waterfall

Slide 124

Slide 124 text

Now: Stream-aligned 163

Slide 125

Slide 125 text

Supporting topologies 164 Design Platform, Analytics Platform, Web Application Platform, CRM platform, Infrastructure platform Mainframe core system Architecture, Information Security

Slide 126

Slide 126 text

Concepts ● Stream-aligned: build & run ● Supporting team types: clarity ● Platform teams have customers: Stream-aligned teams 165

Slide 127

Slide 127 text

Results ● Digital sales: 40% growth (5 yrs) ● Customer service: 2x digital ● Claims handling: 80%+ online 166 teamtopologies.com/examples

Slide 128

Slide 128 text

Thanks to: Christian Moe Chief Digital Officer Gjensidige Insurance 167

Slide 129

Slide 129 text

168 What is business agility? Being agile, not doing ‘Agile’ Valuable: product mindset Team Topologies examples

Slide 130

Slide 130 text

Respond rapidly to changing external and internal conditions

Slide 131

Slide 131 text

Situational awareness, clarity of business purpose, good technical practices, localised decisions

Slide 132

Slide 132 text

Strong focus on user needs and User Experience (UX), clear costs, viability, mission, ...

Slide 133

Slide 133 text

Real-world examples & Dealing with legacy

Slide 134

Slide 134 text

How does Team Topologies help with business and technical agility? 173

Slide 135

Slide 135 text

Team Topologies encourages decoupling of business concepts to help make the organization more responsive

Slide 136

Slide 136 text

Team Topologies patterns help to turn blocking compliance checks into self-service, flow-aligned, API-driven checks

Slide 137

Slide 137 text

Team Topologies is partly a sense-making approach to help organizations gain situational awareness and therefore agility

Slide 138

Slide 138 text

Team Topologies helps the organization to focus tightly on its core mission via streams and limiting team cognitive load

Slide 139

Slide 139 text

What’s next? 178

Slide 140

Slide 140 text

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

Slide 141

Slide 141 text

Infographics ● Getting Started ● In a Nutshell 181 teamtopologies.com/infographics

Slide 142

Slide 142 text

academy.teamtopologies.com

Slide 143

Slide 143 text

TeamTopologies.com @TeamTopologies Team Topologies Partner Program 🤝 partners@teamtopologies.com

Slide 144

Slide 144 text

TeamTopologies.com @TeamTopologies Sign up for news and tips: TeamTopologies.com

Slide 145

Slide 145 text

188 Manuel Pais FlowOnRails Twitter: @manupaisable LinkedIn: manuelpais Matthew Skelton Conflux Twitter: @matthewpskelton LinkedIn: matthewskelton Copyright © Conflux Digital Ltd and FlowOnRails 2018-2021. All rights reserved. teamtopologies.com