When organizations start moving to DevOps, one of the first things they focus on is automation. It makes sense: Automated deployment tools are easy to explain, and implementing them usually shows value right away. But speed isn’t the only (or even the best) reason to move to DevOps and an automated release pipeline.

For many organizations, traditional testing groups are separated from the IT security group. But having traditional testers perform some security testing efforts is a great way of achieving a balanced approach to shifting left while being mindful of staffing and budgetary challenges. It also has some great advantages.

When managing a remote team, usual practices apply, but there are some additional considerations you should think about. You need to be sure not to make any blunders that would affect the productivity and happiness of your staff. Here are eight common mistakes managers of remote teams make that you should try to avoid.