3 ms·
I've worked on projects like this at two separate companies, both of which had people on opposite sides of the world and across the US. It was easiest at the sm
by lovehashbrowns 6y ago
I've worked on projects like this at two separate companies, both of which had people on opposite sides of the world and across the US. It was easiest at the smaller start-up because communicating via Slack/Hipchat made this work fairly smoothly, aside from the occasional situations where we had to go on a video chat at 7a or 10p.
For the start-up I worked at, everyone around the world was working on the same APIs. Issues and priorities were just bubbled up via chat.
The larger company I work for now is more difficult because more people = more questions that need to be resolved via video chats. We have a PM that talks with the people on the other side of the world and also a "team liaison" on the east coast that hops in their planning meetings, and communicates with us if there are any issues we need to be aware of. The project we're working on is being completed by three separate teams, all in different parts of the world.
The smaller team I am on has people all over the US and Canada. That itself hasn't been much of an issue. Prior to COVID, we would have the occasional fly-in to San Francisco so we could do team stuff in person, go out for happy hour, etc.
The most complaints I've seen where lack of communication within team members which contributes to siloing, but that is more of an issue with how many services our team has assigned to it and less to do with having team members working remotely (although it does contribute).