The Devops movement addresses the dysfunction that results from organizations composed of functional silos: Devops proposes instead strategies to create better collaboration between functional silos, or doing away with the functional silos altogether and creating cross-functional teams (or some combination of these approaches).
The fundamental problem is this: Bad behavior arises when you abstract people away from the consequences of their actions. Functional silos abstract people away from the consequences of their actions.
The essence of Devops, I believe, is to design a system in which people are held responsible for the consequences of their actions – and indeed, one in which the right thing to do is also the easiest thing to do.
(There’s No Such Thing as a “Devops Team” http://continuousdelivery.com/2012/10/theres-no-such-thing-as-a-devops-team/)