Finding a Routine That Works for a Distributed Engineering Team
6 December, 2018
Challenge 1: Finding a daily stand up time that suits everybody. Challenge 2: Absence of a development process.
We were able to build a process together, stick to that process, and continuously refine it. Challenge 1: We met to pick a daily standup time that would work for all of us, despite our personal schedules from our lives in different time zones (with a maximum time difference of 9 hours between San Francisco and Warsaw). Challenge 2: We established a routine by introducing an agile scrum process with two-week cycles, including daily stand-ups, bi-weekly product demos, sprint plannings & grooming sessions as well as monthly retrospectives. The latter is the crucial component that ensured that we challenged and refined the process over time, resulting in a highly adapted and adopted routine that allowed everybody to strive.
There is constantly room for improvement, and most of the time it's the team that is able to identify and implement those. The most important thing, however, is that you enable and encourage the team to allow for such improvements to happen. The environment I build gives me the confidence, that due to this built-in, self-healing, improvement mechanism, any future situation that we navigate through can be mastered because of, and by the team.
Sameer Kalburgi, VP of Engineering at Fieldwire, debunks the hidden meaning behind the recurring requests for transparency and shares how he managed to enhance collaboration with other stakeholders by drawing his team’s boundaries clearly.
VP of Engineering at Fieldwire
Matt Pillar, VP of Engineering at OneSignal, shares how he improved the reliability of high scale systems by securing investment in infrastructure and on-call services.
VP Engineering at OneSignal
Matt Pillar, VP of Engineering at OneSignal, recalls how he helped merge two engineering teams at two different locations and how legal and cultural context made all the difference.
VP Engineering at OneSignal
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.
Engineering Manager at Asana
Ido Cohen, Head of Product at Permutive, shares how he approaches communication with different stakeholders who more often than not have different -- and conflicting -- goals.
Head of Product at Permutive
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.