The effects of COVID-19 have forced the accelerated adoption of fully remote teams, a trend that is likely to continue well beyond the impact of this pandemic. Employers around the world have started to embrace the model, with companies such as Atlassian, Facebook and Twitter announcing that employees can work from home permanently. Many employers are reporting increases in productivity by 44%1.
Software engineering using Agile has typically focused on co-located teams. While many modern Agile engineering teams already have some element of distributed operations, the pandemic has forced adoption of a fully distributed approach.
At this time, the approaches to improving productivity and team engagement for a remote workforce are fairly well understood. This article considers some of the practical observations (that build on common knowledge and lessons learned) as well potential approaches to tune remote Agile team performance. One of the key observations has been that the productivity gains or losses from remote operations are acutely amplified by the maturity of the Agile team, although there are techniques and tools to overcome many of these.
The rest of this article explores several observations related to how Agile team maturity and productivity are impacted by remote operations, especially for teams that are less mature. Many of the suggestions are related to reducing the productivity gap for less mature Agile teams.
Engineers learn a huge amount from their peers through informal and sometimes unintentional interactions. For example:
This can be difficult to replicate in a fully remote model. Less mature Agile teams with more narrowly focused expertise and lower relative levels of product knowledge will suffer more from the lack of informal learning.
Approaches to improve maturity in this area:
One of the biggest challenges with fully remote teams is that the lack of visibility and line of sight can lead to a lack of trust and accountability. This is amplified when the team members do not have a history of working together. This can lead to a situation when a lot of time is spent on generating reports, following up on activities and trying to micromanage daily activities at a much more granular level than the daily standup, which impacts team performance.
Team chat and instant messaging is a critical tool for remote teams. However, for less mature teams, team chat can cause implicit bottlenecks. Team chat channels can quickly become flooded with questions and requests, which in turn cause bottlenecks for the more experienced team members who are trying to respond. On the flip side, the requestors are unclear whether they are even going to get responses to some of their questions.
Mature teams typically have a strong sense of team identity, engagement and personal relationships that strengthen collaboration. This can be difficult to foster in a less mature team that is working remotely. While there is a lot of data on the importance of non-work interactions, getting team members to interact dynamically outside of work can be a challenge. The challenge is to make social time fun, dynamic and engaging for all participants instead of being treated as an extension of work.
Some ideas that have had generally good results:
Agile teams need to be aware of the performance penalties associated with remote operations. Increasing the team’s Agile maturity should be a priority, however there are also several ways to reduce the productivity decrease associated with remote operations for less mature teams. These approaches can be applied on top of all the typical strategies associated with increasing a remote team’s performance.
 - https://www.pwc.com/us/en/library/covid-19/us-remote-work-survey.html
Subscribe to keep up-to-date with recent industry developments including industry insights and innovative solution capabilities
Learn how telemetric data can help DevOps teams automate feedback, monitor applications in real-time, and ensure accelerated software delivery.
Unlock cost-friendly and unrestricted data quality checking