Here at Admios, though we’re definitely used to working remotely with our customers, it’s not unusual for us to travel overseas to work side-by-side with them. Be it for key releases, peer-programming through packed sprints, or project ramp-ups to get acquainted with the team and the details of the product, it’s a great opportunity for us to get to know their team and figure out how to best work with them and tackle the tasks at hand.
With our most recent client, my Admios team and I worked onsite with them for the first month of our project. Due to their ramp-up process and the extensive nature of their product, we agreed on an extended visit so we could thoroughly sync up with them and get an idea of where they were at and how they would be moving forward.
After just one week onsite, I could see how important it was for us to be there. We had the chance to meet with leads and members of other teams, discuss the capabilities of their Senior Developers and get a good sense of their stack’s functionality. Based on a microservice infrastructure based on Consul and core services that tied them all together, their back-end turned out to be quite complex.
By my third week, we were working through our first sprint with the team and nearing the end of our ramp-up. Doing some peer-programming early on was a great way to discuss the team workflow and things that could be improved from a fresh point of view. It was also a big help given that our next task is to restructure their front-end project with a more nimble stack. We’re now well versed in the company’s structure and needs so we can hit the ground running.
Though we’re now back to working remotely with their team, our one month onsite was a great way to familiarize ourselves with them and put faces to the names of our new teammates.
Getting a chance to peer-program with them in the first few weeks was key in giving us a solid base idea of how to best help them while utilizing their team. We’ll definitely visit them again in the future so we can keep up with local developments and continue to improve our approach as remote developers.