Remote-first Team Interactions for Business and Technology Teams @ DevOps Notts, Jul 2020
0 likes287 views
The document discusses the importance of remote-first team interactions in the context of DevOps, emphasizing the need for clear communication and well-defined team boundaries. It introduces concepts such as 'team API' and 'team dependencies' to facilitate effective collaboration and mitigate issues in remote work settings. Resources and tools for remote teams, including templates and workshops, are also provided to enhance organizational processes.
![31
Private car salesCommercial car sales
Car leasing
[example]From Team Topologies,
chapter 3 (page 53)](https://image.slidesharecdn.com/remote-firstteaminteractionsforbusinessandtechnologyteamsdevopsnottsjul2020-200728203434/85/Remote-first-Team-Interactions-for-Business-and-Technology-Teams-DevOps-Notts-Jul-2020-25-320.jpg)
Remote-first Team Interactions for Business and Technology Teams @ DevOps Notts, Jul 2020
- 1. TeamTopologies.com @TeamTopologies Manuel Pais co-author of Team Topologies DevOps Notts meetups, 28 Jul 2020 Remote-First Team Interactions with Team Topologies
- 2. 2 Manuel Pais Independent IT organizational consultant and trainer Ex-dev, ex-build manager, ex-tester, ex-QA lead LinkedIn instructor on Accelerating Continuous Delivery Twitter: @manupaisable LinkedIn: manuelpais
- 4. Remote Work tools + psychological safety + ground rules and practices 5
- 5. 6 Poor remote interactions can kill the “<LATEST> transformation”.
- 6. Team Topologies 8 Organizing business and technology teams for fast flow Matthew Skelton & Manuel Pais IT Revolution Press (Sep 2019) Order via stores worldwide: teamtopologies.com/book
- 7. 9 Team Dependencies Setting Team Boundaries Purposeful Interactions Growing Feedback
- 9. 11 In a remote-first context, it’s vital to understand who is working on what
- 10. Team API 12
- 11. “For effective team-first ownership of software, teams need to continuously define, advertise, test, and evolve their Team API” Team Topologies, p.48 13
- 12. Team API 14 ● Artifacts owned by the team ● Versioning & testing approach ● Wiki and documentation ● Practices and principles ● Roadmap & priorities ● Communication preferences (when/how)
- 13. Team API 15 ● Artifacts owned by the team ● Versioning & testing approach ● Wiki and documentation ● Practices and principles ● Roadmap & priorities ● Communication preferences (when/how)
- 18. 20 Eliminate blocking dependencies. Mitigate slow dependencies. Keep healthy dependencies.
- 21. “an individual’s social network (meaningful relationships) is typically in the order of 100–200 individuals” - Robin Dunbar 27 https://royalsocietypublishing.org/doi/full/10.1098/rsos.150292
- 22. 28
- 23. 29
- 24. 30 Trust dynamics can change when crossing a Dunbar boundary. Expect different rules & non-linear effects.
- 25. 31 Private car salesCommercial car sales Car leasing [example]From Team Topologies, chapter 3 (page 53)
- 26. 32
- 27. 33
- 28. 34 Private car sales Commercial car sales Car leasing
- 29. 35 # enabling-test-automation ... # platform-team … # stream-team-1 # stream-team-2 # stream-team-3 ... # st1-platform-monitoring # st2-enabling-test-automation ... Mary (Platform Team Engineer) # support-environments # support-logging … # marketing # sales ...
- 30. 36
- 31. Team-focused conventions 37 ● team channel: team topology and name ● (temp) interaction channel: teams + purpose ● support channel: support + service name ● username: name + role + team + topology
- 32. 38 Team-focused conventions increase discoverability and reduce cognitive load on communications.
- 35. 41 We cannot and should not expect to talk to everyone else (person or team)
- 36. 42 Well-defined interactions are key to effective teams
- 37. 43 Team Interaction Modes Collaboration: 2 teams working together X-as-a-Service: 1 provides, 1 consumes Facilitating: 1 team helps another
- 38. 44
- 40. Stream-aligned team 1 46 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)
- 41. Use awkwardness in team interactions as a sensing mechanism for evolution 47
- 42. Clarify Communication Purpose & Channels 53
- 47. 58
- 49. 60
- 50. Team Topologies 61 Organizing business and technology teams for fast flow Matthew Skelton & Manuel Pais IT Revolution Press Order via stores worldwide: teamtopologies.com/book
- 51. Workbook coming soon... Team Topologies for Remote Teams 62 for Remote Teams Sign up for news: teamtopologies.com/newsletter Icon by Pixel perfect from www.flaticon.com
- 54. Free Resources 65 Remote-first interactions teamtopologies.com/remote-first Free tools & templates github.com/teamtopologies
- 55. Thank you! 66 Matthew Skelton, Conflux @matthewpskelton Manuel Pais, Independent @manupaisable teamtopologies.com