At this point in the DevOps movement if you ask nearly anyone what is the hardest part of DevOps, they will invariably say changing culture. It isn’t the technology, it isn’t even process, rather it is the people that are the impediment to change. Why is this? Why is change so hard? Despite the reports and numbers, why is it so difficult to change people and transform enterprises?
Author: Bart Driscoll
… once an object is created, its state must remain unchanged. In other words, the only way to make a change to an immutable piece of infrastructure (server, container, component, etc.), is to replace the old version with a new, updated version.
Hybrid clouds enable enterprises to exploit a public cloud for lower risk development and testing activities and then transition applications on-premises for “Staging” and for ultimately running in “Production”.
If you can’t deploy, you can’t do DevOps. find out why in this post.
what is stopping you? Here is a look at a few of the key impediments to scaling DevOps.
A few tips for reducing the amount of firefighting so you can focus on creating value.
A few nuggest collected during DOES2015.
Melvin Conway (Conway’s Law) stated it best when he said…
Organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.
So how do you protect yourself or prevent yourself from codifying the old? What are some of the common tooling pitfalls that impede adoption or derail transformation?
Repost from July 2015 on inside.emc.com. Coming out of EMC World and a recent IT Transformation Week, I […]
Is DevOps the NUMMI of Enterprise IT?
Coded Pipelines 