We know that team-based software delivery can be very effective but how can we promote and enable team-based approaches for organisations that are fully remote or hybrid? What should teams think about and what patterns can teams adopt to be effective when most people are not in the office?
Based on the ideas from Team Topologies book and the new Remote Team Interactions Workbook, co-author Manuel Pais will present some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world.
2. Team Topologies
2
Organizing business and
technology teams for fast flow
Matthew Skelton & Manuel Pais
IT Revolution Press, 2019
teamtopologies.com/book
3. “innovative tools and concepts for
structuring the next generation
digital operating model”
Charles T. Betz,
Principal Analyst, Forrester Research
3
4. Remote Team Interactions
Workbook
4
Using Team Topologies
Patterns for Remote Working
Matthew Skelton & Manuel Pais
IT Revolution Press, 2022
teamtopologies.com/workbook
5. “extends the original book with
valuable exercises to setup your
teams effectively for a Remote First
world”
Stefan van Oirschot,
Chief Digital Advisor at Red Hat
5
16. Team API
19
● Artifacts owned by the team
● Versioning & testing approach
● Wiki and documentation
● Practices and principles
● Roadmap & priorities
● Communication preferences (when/how)
18. “For effective team-first ownership of
software, teams need to continuously
define, advertise, test, and evolve
their Team API”
Team Topologies, p.48
21
34. “an individual’s social network
(meaningful relationships)
is typically in the order of
100–200 individuals”
- Robin Dunbar
37
https://royalsocietypublishing.org/doi/full/10.1098/rsos.150292
44. Team-focused conventions
48
● team channel: team topology and name
● (temp) interaction channel: teams + purpose
● support channel: support + service name
● username: name + role + team + topology
55. Stream-aligned team
59
Example: 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
2 months
(from Mar 30
to May 29,
1 day per week)
Monitoring &
Telemetry
Platform team
Collaboration Store and visualize
data on product
features usage
3 weeks
(from Apr 13
to Apr 30,
2h per day)
56. Use awkwardness in team
interactions as a sensing
mechanism for evolution
60