6 Steps To Survive A DevOps Transformation
This certainly gets at the heart of what DevOps is and where it comes from. Looking at all these larger business philosophies, you see how many of them predate DevOps by so much, and yet how applicable they still are to it. Many people's interpretaiton of DevOps is that it changes the work environment to be how people actually already want to work, and it just eliminates needless red tape and processes that are in the way. You can see that here. These tips also highlight the potential downside of DevOps. I've heard it tons of times before that ra culture shift that comes from the bottom up is required - or at least, it requires real stakeholders across the organization that will show people the benefits. If it simply comes as an order from the top, it'll never stick. People may follow the processes to the letter, but it won't make an impact unless they're on board with the spirit.
A lot of these synergize with each other. The measurable goals and the quick wins, for example, go hand in hand. You can set your metrics for what you want to measure and then pick a quick achievable for it that you can get done in the next release cycle or so. "Talk to other teams" may seem like a no-brainer, but Charlie's right; it's more art than science. Giving them the support and resources and making them feel like they're not stranded on an island goes a long way towards stimulating that cross-team communication. All in all, I'd say that these tips are applicable to more than just DevOps, and are good overrall - but that doesn't mean they aren't great for DevOps as well.