We've just launched plato for individuals

🔥

login


Google Sign inLinkedIn Sign in

Don't have an account? 

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

Migrating a Legacy Service: A Lesson in Eng/Ops Collaboration
18 November

Jackson Dowell, Engineering Manager at Asana, discusses how he approached legacy service migration by stabilizing the existing stack and getting Engineering and Operations to work together to address the underlying problems.

Collaboration
Jackson Dowell

Jackson Dowell

Engineering Manager at Asana

When Systems Thinking Unlocks a Way Forward
18 November

Jackson Dowell, Engineering Manager at Asana, explains how he moved his project forward by coming up with a clear model of the system and problem that provided guidance to the team and helped communicate their efforts outward.

Managing Expectations
Dev Processes
Internal Communication
Jackson Dowell

Jackson Dowell

Engineering Manager at Asana

An Egalitarian Approach to a Disportionate Workload
16 November

Nimrod Perez, CTO and VP of Engineering at Wobi LTD., explains how he solved a long-troubling problem of disproportionate workload by his simple and egalitarian approach.

Team processes
Ethics
Ownership
Nimrod Perez

Nimrod Perez

CTO and VP of Engineering at Wobi LTD.

How Skip-Level Conversations Can Help You Create Strong Relationships with Your Engineers
31 October

Toby Delamore, Product Manager at Xero, explains how skip-level conversations and maintaining an attentive relationship with engineers enabled him to keep a finger on the pulse of the team.

Internal Communication
Feedback
Meetings
Collaboration
Toby Delamore

Toby Delamore

Product Manager at Xero

Growing the Culture of a New Product Team
31 October

Toby Delamore, Product Manager at Xero, explains why culture needs to be grown organically by a team and what is the role of a product leader in guiding that process.

Company Culture
Team processes
Toby Delamore

Toby Delamore

Product Manager at Xero

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.