Separate DevOps team

ARCHIVED BLIP

Please be aware that we have archived this blip and are no longer actively keeping the information updated. The current edition of the radar only features items that we feel are new or noteworthy.Understand more

HOLD?

In the last radar issue we advised against creating a separate DevOps team, as DevOps is about creating a culture of shared responsibility in delivery teams. We recommend embedding operations skills into delivery teams to reduce friction and deliver better outcomes. However where there is a need for significant investment in tooling and automation, we do see a role for a Delivery Engineering team. Rather than being a helpdesk, these teams build tooling and enable teams to deploy, monitor, and maintain their own production environments.

History for Separate DevOps team

Nov 2015

Hold?

In the last radar issue we advised against creating a separate DevOps team, as DevOps is about creating a culture of shared responsibility in delivery teams. We recommend embedding operations skills into delivery teams to reduce friction and deliver better outcomes. However where there is a need for significant investment in tooling and automation, we do see a role for a Delivery Engineering team. Rather than being a helpdesk, these teams build tooling and enable teams to deploy, monitor, and maintain their own production environments.

May 2015

Hold?

Jan 2015

Hold?

Jul 2014

Hold?

Some companies with good intentions create a separate DevOps team, which misconstrues the definition of DevOps. Rather than a role, DevOps is a cultural movement encouraging collaboration between operations specialists and developers. Rather than create yet another silo and suffer the consequences of Conway's Law, we advise you to embed these skills into teams, improving feedback loops and communication pathways by removing friction.