Please enable JavaScript.
Coggle requires JavaScript to display documents.
Team Topologies - Coggle Diagram
Team Topologies
Fracture planes
domain
tech
change cadence
biz context
risk
regulatory
location
users
evaluating topologies
cognitive load
comms overhead
clarity of boundaries
handoff delays
empowerment and skills
team types
stream
single feature / product
should be default
e.g. Mendeley
platform
common shared services
e.g. auth
sub-system
specialist services
e.g. complex domain services
Enabling
specialist knowledge
e.g. security
interaction modes
collaboration
work together closely with other teams
X as a Service
provide services to other teams
facilitation
skills
coaching
Remit
clear
we know what we're doing and why
logical
it makes sense
collaboration
at most 15 people in a remit
Component vs Feature
Component team
FE
BE
Feature team
FE/BE
evolving teams
boundaries emerging
be flexible