Remote-first work is the "new normal" for companies around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely.
However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents.
Based on the ideas from Team Topologies, Manuel Pais and Matthew Skelton will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world.
Designing Team APIs and virtual communication channels that promote relevant team interactions while minimizing communication overhead will help modern organizations keep a fast flow of delivery once they're past the initial adaptation to teleworking.
Following well-defined interaction patterns and architecting for team-first software boundaries will also help reduce communication overhead, clarify expectations on teams, and increase visibility of on-going work and support.
5. Team Topologies
5
Organizing business and
technology teams for fast flow
Matthew Skelton & Manuel Pais
IT Revolution Press (Sep 2019)
Order via stores worldwide: teamtopologies.com/book
10. “For effective team-first ownership
of software, teams need to
continuously define, advertise, test,
and evolve their Team API”
Team Topologies, p.48
10
11. Team API
11
● Artifacts owned by the team
● Versioning & testing approach
● Wiki and documentation
● Practices and principles
● Roadmap & priorities
● Communication preferences (when/how)
12. Team API
12
● Artifacts owned by the team
● Versioning & testing approach
● Wiki and documentation
● Practices and principles
● Roadmap & priorities
● Communication preferences (when/how)
20. “an individual’s social network
(meaningful relationships)
is typically in the order of
100–200 individuals”
- Robin Dunbar
20
https://royalsocietypublishing.org/doi/full/10.1098/rsos.150292
29. Team-focused conventions
29
● team channel: team topology and name
● (temp) interaction channel: teams + purpose
● support channel: support + service name
● username: name + role + team + topology
38. Stream-aligned team 1
38
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)
39. Use awkwardness in team
interactions as a sensing
mechanism for evolution
39
45. “...three-tier support should be
replaced with Swarming”
– Jon Stevens-Hall, 2016
45
https://medium.com/@JonHall_/itsm-devops-and-why-the-three
-tier-structure-must-be-replaced-with-swarming-91e76ba22304
52. Team Topologies
52
Organizing business and
technology teams for fast flow
Matthew Skelton & Manuel Pais
IT Revolution Press
Order via stores worldwide: teamtopologies.com/book