I didn't see this DevOps challenge coming. My DevOps team seems to often be in agreement, with little discussion...
most of the time. Could this be due to groupthink?
Initially, when we think of DevOps and groupthink, it seems like an oxymoron. After all, DevOps is based on a culture of collaboration; DevOps teams bring together specialists from disciplines with different views on what is most important, and this should form the basis for preventing groupthink.
Accordingly, one would think that the tendency of these groups would be to have many lively, productive or, perhaps, even heated discussions, as each team member lobbies for what is most important to the area they represent.
However, since all closely knit teams are susceptible to groupthink, it can certainly happen in DevOps teams. This is definitely a new DevOps challenge.
Groupthink, a term coined by Irving Janus in 1972, is a cultural attitude that implicitly rewards members whose desire for unanimity overrides their motivation to realistically appraise alternative courses of action.
Just like all teams, DevOps team members may have biases and fixed mindsets based on their respective areas of expertise, team members from opposite disciplines may become polarized, and informal leaders may emerge, all of which sets the stage for groupthink. The DevOps challenge here is that team members' mindsets may impede critical thinking, group interaction may amplify individual biases and group discussions may dissolve into deliberation failures.
DevOps team members from different functional specialties may often defer to the expert in a particular realm to solve individual problems. Since DevOps teams are formed to implement continuous integration and deployment, these teams also recognize that they have to solve issues quickly and decisively, and, therefore, may defer to the team member with the most authoritative voice.
You can recognize this groupthink DevOps challenge by looking at your team members' interactions. Specifically, if your team has an illusion of invulnerability; is consistently in agreement, with little discussion; and if there is collective rationalization and self-censorship during meetings and team discussions, it is very likely that your team may be influenced by groupthink.
Where is DevOps 2.0 going to take you?
Taking the pain out of making DevOps work
Struggling with DevOps? Change the culture
Dig Deeper on Agile DevOps
Related Q&A from Gerie Owen
There are numerous DevOps tools, so as a tester, is it necessary to know all of them? Gerie Owen explains why tools might come secondary to the goal ... Continue Reading
As a junior tester, I think learning scripting languages could make me more valuable to my team and enhance my career. But how do I pick the ... Continue Reading
DevOps teams use chaos engineering, but at what cost? Learn how this testing method secures applications in ways that traditional testing can't. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.