How to Facilitate a Knowledge Transfer Remotely

At the end of a recent project, I was scheduled to visit our clients for a week to hold a knowledge transfer for their development team. Due to the coronavirus pandemic, we were forced to change plans, and we opted to run the knowledge transfer remotely. I’d spent the previous weeks creating and refining an […]

Remote-First Communication for Project Teams

“If anyone is remote, you’re all remote.” At Atomic Object, we value co-located teams. But not every team member can always be co-located. Larger project teams may have members from multiple offices. Some projects might involve working closely with other vendors. I experience this “remoteness” when I support the infrastructure needs of teams in our […]

Tools & Practices for Remote Teams, Part 2 – Communicate, Communicate, Communicate!

This is part two of a two-part series on tools and practices for maintaining a healthy and effective remote team. In part one, I discussed infrastructure and tools for remote teams. In this second part, I’ll be focusing on day-to-day practices and attitudes. As with part one, this advice is not only for remote teams […]

Working with Remote Software Teams

Atomic works in close partnership with our clients, adopting their goals and becoming part of their internal team. This requires regular communication with the client’s product manager during every stage of the project — something we’ve very intentional about, especially when the client is too far from our office to have weekly in-person meetings. To […]

A Comparison of Remote Pairing Tools – Skype vs. Wemux vs. Chrome Remote Desktop

Since starting at Atomic, I’ve had to use remote pairing on several occasions to work with developers who were not co-located with me. I wanted to give an overview of some of the different tools I’ve used for remote pairing and what I like/don’t like about them. Skype Skype is hardly a sophisticated remote pairing […]