Beyond Agile with Team Topologies discusses an approach to organizational design called "team-first thinking" based on the concepts in Team Topologies. It describes how teams should be the fundamental unit of delivery and how their size, lifespan, interactions and cognition must be considered. The document provides an example of how a fitness company called PureGym applied these principles to transition from project teams to long-lived stream-aligned teams in order to better support rapid business needs. Key takeaways are that Team Topologies can help organizations increase team efficiency, evolve away from monolithic structures, and achieve better business agility through its focus on team purpose, interaction modes and service boundaries.
2
Richard Allen
Head ofconsulting at Conjurer Solutions
Founder of leavewizard.com
Founder of devsouthcoast.com
Experience:
• More than 20 years developing software
Team Topologies Experience:
• Involved with one of the first implementations at
PureGym
• Further developed the Team-Shape-Templates
• Crafted the infographics
• Developed and delivered guided discovery workshops
4
Individuals and interactionsover processes and
tools
Working software over comprehensive
documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Agile Manifesto 2001
16
“We must shiftour thinking from treating teams as collections of
interchangeable individuals that will succeed as long as they
follow the “right” process and use the “right” tools, to
treating people and technology as a single human/computer
carbon/silicon socio-technical ecosystem”
Team Topologies, Matthew Skelton and Manuel Pais
17.
17
Aim to achievebusiness agility via:
• Rapid flows of change and fast feedback
• High situational awareness
• Loosely coupled, autonomous teams
• Loosely-coupled, autonomous services & applications (architecture)
• High domain context at multiple levels
• Healthy, evolvable codebase
• Engaged Teams
• People incentivised for long-term product health, not “features”
20
Team Lifespan: Smalllong-lived teams
TEAM =
• Stable (not static) group of 5 to 9 people
• Work towards a shared goal as a unit
• Smallest entity of delivery within an
organization
22
Team Size: Dunbar’sNumber
Trust dynamics can
change when crossing a
Dunbar boundary.
Expect different rules &
non-linear effects
23.
23
Team Interactions: Conway’sLaw
“Organizations which design systems…are
constrained to produce designs which are copies
of the communication structures of these
organizations”
- Mel Conway
31
Team Cognition: FracturePlanes
Business Domain Bounded Context
Regulatory Compliance
Change Cadence
Team Location
Risk
Performance Isolation
Technology
User Personas
44
Differences from thebook
Complicated
Subsystem
team
Stream-aligned
Stream-aligned
Platform team
Enabling
team
https://github.com/TeamTopologies/Team-Shape-Templates
51
•Launched 2009
•260+ gymsin the UK
•> 1.1 million members
•Largest operator in the UK
•Second largest operator in
Europe
•2015-2020 Huge growth in
members
53
Steady Growth withShort-lived Project Teams
Project D
Project E Small Changes
Project F
Projects BAU
Project G
Project H
Bugs
GSD
Handover
54.
54
Trigger: Rapid TeamGrowth to 40+
Bugs & Small Change
Project G
Project H
Project I
Project J
Project K
Projects BAU
GSD
Handover
55.
55
The Monolith
Site
Project G
ProjectH
Project I
Project J
BAU
Vendor API
Reseller API
Mobile App
Mobile Team
Customer API
Membership Management System
Single repository
57
Breaking the Monolith
Gyms
Site
ClassListings Members Area
Payments Help Centre Class Booking
Join Process
PT Profiles
Gift Cards
Landing Pages
Project G
Project H
Project I
Project J
BAU
Group
Training
Time Tables
Blog Live Chat Kiosks …
58.
58
Other
Payments Retention
Acquisition Team
GymTeam
Re-defining Teams
Join Process
Landing Pages
…
Time Tables
Gyms
…
Reconcilliation
Join Payments
…
Members Areaa
CRM
…
…
Streams
Enabling
Mobile?
Platform
Membership Management Gateway (MMG)
Developer Experience SRE
60
Mobile?
Using Facilitation andDeveloping X as a Service
Gym
Retention
Acquisition
Membership Management Gateway
SRE
Payments
Dev
Ex
*
*
*
*
*
*
Flow of change
62
Simple Team APIs
TeamType: Acquisition
Owns a prospects journey before they have joined.
Responsibilities:
Join Process Steps 1 to 3
Gym Pages and Reviews
Banner management
Resellers
Team Presence:
Tech Lead: Joe Bloggs
Product Owner: Jeremy Clarkson
Business Analyst: Don Johnson
Jira Board: https://ajiraboard.com
Jira Label: team-acquisition
Members:
Joe Bloggs
Frankie Boyle
Clare Balding
64
“Team Topologies helpedus to evaluate the
relationships between our teams and
business strategy, to increase team efficiency,
and evolve away from a monolith”
John Kilmister
Principal Software Architect, PureGym
65.
65
Key Concepts
‘Fracture Planes’for splitting code
Cognitive Load for boundaries
Interaction Modes for clarity
Team Types for purpose
72
•Healthy organizational culture
•Goodengineering practices
•Healthy funding and financial practices
•Avoid CapEx/OpEx split in IT
•Project driven deadlines
•Large-batch budgeting
•Clarity of business vision
Team Topologies may not be enough