Making Remote teams successful with Agile.

Remote
Meetings
Internal Communication
Collaboration
Productivity
Team processes
Agile / Scrum

6 December, 2017

Nowadays, it is very common to have remote teams working in different time zones. But how can you ensure remote teams are successful and how do you ensure high-quality collaboration?

Problem

At Blackhawk Network, I was given the role of managing the company's native app team. The team was comprised of four engineers in California, and five engineers working in Bangalore, India. This meant the team had to deal with significant time zone differences. The team had a product manager who was in India, who worked with a tech lead here in California on a daily basis. Information between the teams was exchanged between these two team members. However, the tech lead in California was not involved in discussions with remote teams. The features of our products would often have gaps, and there was always at least a 24-hour turnaround time for these issues, which caused delays in feature delivery.

Actions taken

To resolve this issue, I first put together some metrics regarding the team's output, issue resolution time, and feature delivery times. I then got the whole team together in two separate sessions and explained the issue we were having. Next, I recommended that the team should operate as one scrum team of nine engineers, and I asked the team to pick a time that would work for both the Indian and Californian teams, so they could hold their scrum meetings. The teams discussed this among themselves and came to an agreement to do two-week sprints. They also agreed that:

  • They would hold daily stand-ups. These would be during the early morning for the Californian team, and during the late evening for the remote Indian team.
  • Groomings would be held once a week, and the two teams would alternate between morning and evening schedules.
  • Sprint planning and a retrospective would be held once for every sprint. They would be held in the evening for the Californian team, which would be early morning for the Indian team.
  • The Sprint Review would be held once for every sprint. It would be held during the day, which would be late in the evening for the remote Indian team. The product manager was involved in all of these meetings and helped to articulate the vision to the entire team. Sprint Reviews and demos at the end of each sprint helped all of the stakeholders to visualize the progress we had made, and we were able to release an update to our native apps after every sprint. We kept the daily stand ups to 10 minutes and timeboxed the other meetings for efficiency. The teams were able to plan their schedule more efficiently, and were less bothered by the difficulties of working with time zone differences.

Lessons learned

Having the whole team work together as a single scrum team helped to eliminate a lot of the communication gap my team had. The project manager took on the role of scrum master for the remote team, to remove any roadblocks. Having the product manager in all of the meetings helped the team to understand the feature more accurately. They could ask questions in grooming meetings, make better estimations and infuse a commitment-driven approach to the team. In addition, having daily standups helped to reduce the 24-hour turnaround time, as there was frequent communication.


Related stories

Leveraging Diverse Peer Groups for Tighter Feedback
24 May

With both the need for a more supportive team setting and shorter feedback cycles, Marc LeBrun, VP Engineering at Flow Kana, addresses two problems with a single solution.

Team reaction
Cross-functional collaboration
Collaboration
Marc LeBrun

Marc LeBrun

VP Engineering at Flow Kana

Leveraging the Team to Salvage a Frustrated High-Performer
24 May

Marc LeBrun, VP Engineering at Flow Kana, shows the value in establishing a collaborative relationship with a withdrawn but highly-capable employee. We can then use that bridge to draw the person back into the team and elevate everyone’s performance.

High Performers
Internal Communication
One-on-one
Marc LeBrun

Marc LeBrun

VP Engineering at Flow Kana

Going Low-Tech to Uplevel Agile Practices
24 May

Marc LeBrun, VP Engineering at Flow Kana, describes how he empowered teams to make decisions and uplevel their process by adopting a low-tech approach to agile practices.

Team reaction
Leadership
Impact
Agile / Scrum
Marc LeBrun

Marc LeBrun

VP Engineering at Flow Kana

Remote Work in Times of the Coronavirus Pandemic
21 May

Steve Hoeg, Director of Engineering at Faire, provides a detailed list of instructions that will make your remote work in times of coronavirus pandemics more efficient and productive.

Remote
Steve Hoeg

Steve Hoeg

Director of Engineering at Faire

Aligning an Ineffective Team to Realize Product Potential
21 May

Kowsheek Mahmood, Principal and CTO at ArchetypeTech, explains how he adapted an ineffective team by determining and implementing team-evaluation processes to better align the team on product delivery.

Team reaction
Managing Expectations
Underperformance
Firing
Internal Communication
Productivity
Reorganization
Kowsheek Mahmood

Kowsheek Mahmood

Principal & CTO at ArchetypeTech

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.