<aside> <img src="/icons/bookmark-outline_red.svg" alt="/icons/bookmark-outline_red.svg" width="40px" /> OUTLINE
</aside>
"The future of work is global. Companies that want to stay competitive need to be able to hire the best people from anywhere in the world." - Sundar Pichai
In today's global digital landscape, distributed teams have become the norm, offering comprehensive benefits like round-the-clock productivity and access to the global talent pool. According to Gartner, by 2022, 90 percent of agile development teams will include remote work as part of business continuity planning. By embracing diversity and inclusion, you can tap into the full potential of the global workforce.
Managing these teams effectively requires more than traditional project management approaches. That's where distributed scrum comes in. This chapter explores the world of distributed scrum, delving into its principles, practices, and the unique challenges it addresses.
Today, most online-leading businesses have distributed teams. Distributed teams can work on projects around the clock, and strong talent can be found in less competitive markets. Not to mention, talent is easily retained by not requiring an unwanted relocation. The best tech companies have geographically distributed, self-organizing, cross-functional agile teams.
Distributed scrum is a project management framework that enables teams to collaborate on projects regardless of their geographical location. It is an extension of traditional Scrum, a popular agile methodology software development teams use. The critical difference between the two is that distributed scrum allows team members to work remotely, while traditional scrum requires all team members to be in the exact same physical location.
In distributed scrum, team members use video conferencing tools and collaboration platforms to communicate and share information. This increases flexibility and productivity, as team members can work from anywhere globally. It also presents some unique challenges, such as time zone differences and cultural barriers, which must be addressed to ensure effective collaboration.
“In order to compete in the global economy, businesses need to be able to attract and retain top talent from all over the world." - Satya Nadella
As more companies have teams with at least some remote workers, scrum offers a framework to collaborate effectively. It’s essential, however, to adjust the general agile and scrum practices and use the right tools for a distributed team to be successful. Because of constraints on ad hoc collaboration and informal communication, remote teams need to be even more disciplined about their scrum rituals.
Teamsize]: When working remotely, it’s often best to have smaller teams, especially since a video conference with 5 to 6 people is much easier to manage than 10. The traditional scrum roles are just as crucial with a distributed team but need to make adjustments for the specific challenges of remote work. Remote workers, however, may feel isolated, have less team unity, and miss social interaction with work colleagues. Developing a sense of camaraderie among work-from-home teams may also be more challenging.Informalities]: Since quick water cooler chats disappear with remote work, it’s essential to allow for these informal communication channels to exist. If you use Slack, you can create specific channels with different intents. The scrum master should keep open communication channels to each part of the team and facilitate communication with the group. Without informal hallway chats and impromptu in-person meetings, remote teams must communicate more and sometimes overcommunicate.Time Zones]: Video conferencing calls must be adapted to cover different time zones. If a team is distributed in different time zones or geographies, it’s important to schedule regular video conferencing. You can also hold asynchronous stand-ups where team members use Slack to check in or comment on their work board to share updates. This provides a quick forum for a distributed team that helps with focus, collaboration, communication, and problem-solving.Ownership]: It’s essential for remote team members to take ownership of work and expand that to the entire team. You can provide visibility by online documenting expectations and agreeing on how to hold each member accountable.Culture]: Team members may have different work styles, communication norms, and expectations. It's essential to be aware of these differences and find ways to bridge the gap. This can include establishing clear communication channels, setting expectations for work, and encouraging open dialogue between team members. A remote scrum team should follow the core scrum behaviors of clear communication, transparency, and a dedication to continuous improvement. A remote team’s success depends on mutual trust, communication, and collaboration.The benefits of distributed teams aren't without some heavy trade-offs to close the distance gap between local and remote offices. All the teams must adapt coherently, learn how to share work between offices, communicate effectively, and grow a consistent culture across geographies.
[Structure]: Good software architecture dictates modular design. Structure your development teams accordingly. Every office should be self-sufficient in developing a single piece of technology, which minimizes the collaboration required with units in other time zones and makes them generally autonomous. When a project does need teams in different locations to pitch in, they can focus on their integration points and APIs.
[Golden Hours]: These are the hours when the local and remote teams are simultaneously in their respective offices. This is an excellent time for stand-ups when all units are in the office.