We keep hearing that to 'do DevOps right' we need to tear down all the silos in order to get everyone collaborating as well as just cooperating. How do we continue to benefit from DevOps practices when the silos are there for the foreseeable future and may actually have some benefit, even if only perceived?
In a large enterprise, dedicated operations groups frequently serve multiple development groups, using the specialization of these groups to increase efficiency by having a smaller operations staff. These organizations use separation of duties to avoid real or apparent conflicts of interest and a higher level of security. Silos become firmly embedded because they work in these situations.
When silos are entrenched and can’t be torn down, or even when they’re just dictated above our pay grades, how can we use DevOps to increase collaboration and empathy? What other concepts of DevOps can we use to reduce the pain? What can operations teach development and learn from development to make systems more reliable and IT more successful?
In this session, I’ll present my version of the DevOps philosophy and how it can be applied in an enterprise environment without tearing down all the silos. I’ll tell success stories and failures as well as discussing continuing challenges to make improvements and change the culture in the trenches.
benzvan
thirion
mfonobong
marktimemedia
3n
gr2m
kimpetersen
honnibal
tmiket
tammyeverts
aleyda
iamctodd
