This document discusses remote team interactions using Team Topologies concepts. It emphasizes that understanding dependencies between teams is vital for remote work. It also discusses setting boundaries between teams, defining purposeful interactions, and growing feedback to improve remote collaboration. Effective remote interactions require tools, ground rules, and defining each team's purpose and communication preferences through a "Team API".
6. Team Topologies
6
Organizing business and
technology teams for fast flow
Matthew Skelton & Manuel Pais
IT Revolution Press (Sep 2019)
Order via stores worldwide: teamtopologies.com/book
11. “For effective team-first ownership
of software, teams need to
continuously define, advertise, test,
and evolve their Team API”
Team Topologies, p.48
11
12. Team API
12
● Artifacts owned by the team
● Versioning & testing approach
● Wiki and documentation
● Practices and principles
● Roadmap & priorities
● Communication preferences (when/how)
13. Team API
13
● Artifacts owned by the team
● Versioning & testing approach
● Wiki and documentation
● Practices and principles
● Roadmap & priorities
● Communication preferences (when/how)
25. “an individual’s social network
(meaningful relationships)
is typically in the order of
100–200 individuals”
- Robin Dunbar
25
https://royalsocietypublishing.org/doi/full/10.1098/rsos.150292
35. Team-focused conventions
35
● team channel: team topology and name
● (temp) interaction channel: teams + purpose
● support channel: support + service name
● username: name + role + team + topology
44. Stream-aligned team 1
44
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
3 weeks
(from Apr 13
to Apr 30,
2h per day)
Face Recognition
Complicated
subsystem team
Collaboration Define response
errors and
workflow for poor
contrast photos
2 months
(from Mar 30
to May 29,
1 day per week)
45. Use awkwardness in team
interactions as a sensing
mechanism for evolution
45
57. “...three-tier support should be
replaced with Swarming”
– Jon Stevens-Hall, 2016
57
https://medium.com/@JonHall_/itsm-devops-and-why-the-three
-tier-structure-must-be-replaced-with-swarming-91e76ba22304
65. Team Topologies
65
Organizing business and
technology teams for fast flow
Matthew Skelton & Manuel Pais
IT Revolution Press
Order via stores worldwide: teamtopologies.com/book