Remote development has drastically changed the way teams build software. The freedom to work from wherever and possibly whenever has increased flexibility, but these benefits have not come without growing pains. The people managing this new type of team have worked tirelessly to adapt existing practices to this new, unfamiliar environment.

The good news is you don’t have to go through it alone. Authors Carleton DiLeo and Jennifer Reyes draw from two decades of combined experience building and managing highly-effective remote teams. You’ll see how to set up, manage, and maintain your team. These ideas have been tested, boiled down, and refined over the years into an easy-to-understand series of steps.

If you want to build a new remote team or transition from in-person, Effective Remote Teams has you covered. Read on to start enjoying the benefits of remote development today.

You will:

• Build an ecosystem to promote collaboration and automation
• Create an onboarding process to get new team members quickly integrated
• Manage an ideal work week
• Use the “strike team” method to structure your team
• Make changes to your team and process without affecting velocity
• Keep your team happy and productive long-term

Carleton DiLeo is a software developer with 20 years of experience working in everything from VR to web development. He went 100 percent remote in 2016 and has been responsible for building remote teams from the ground up as well as helping existing teams improve their remote setup. He is currently a remote Principal Software Engineer building robust, scalable systems.

Jennifer Reyes is a software engineer who spends most of her time building robust backend solutions across several web application frameworks. She spent 13 years working with Ruby on Rails before diving into PHP’s Laravel and Python’s Django. With over 12 years of remote work experience, she understands and advocates for clear communication, a good work-life balance, and transparency for every team. She’s currently a remote Staff Engineer. When she’s not writing code, you can find her exploring new coffee shops and collecting journals.