The incidence of DevOps teams is on the rise according to reports, but the industry remains divided on whether a DevOps team should even exist. Some are wary of creating additional silos, or are of the opinion that DevOps is a methodology that everyone should subscribe to in an organisation; others point to DevOps teams as an effective way of transitioning to a new way of working.

Understand how sys admins, developers, testers, security pros and others blend their expertise into collaborative DevOps roles and responsibilities.

Please understand, dear Reader, that I write this with positive intention. I'm not here to impugn any person or organization. I want to talk about some decisions and their natural consequences. These consequences seem negative to me and after reading this post you may agree. When an established company faced a technology innovation, they often create a new team to adopt and exploit that innovation. During my career, I've seen this pattern play out with microcomputers, client/server architecture, open systems, web development, agile development, cloud architecture, NoSQL, and DevOps.