I’ve been thinking about the roles we play as professionals and leaders. A big part of our job is to make decisions on courses of action to address problems or opportunities facing our teams or our organization. Those decisions are often met with resistance, doubt, disagreement, or even outright hostility. In those situations, we’re faced with a choice: cave to the pressure and fall back to the relative safety of our status quo, or press on in the face of opposition. Continue reading
Yeah, I know. This “Keep Calm” thing has been done to death. I’m only adding to the craziness by associating it with the DevOps movement (although I know I’m not even close to being the first). In this context, CALMS is an acronym coined by John Willis and Damon Edwards and later added to by Jez Humble. CALMS represents five key aspects of DevOps and stands for Culture, Automation, Lean, Measurement, and Sharing.
If you haven’t read the 2015 State of DevOps Report (or the 2014 version, for that matter), you’re doing yourself a disservice. I’m putting this report on my DevOps “must read” list, right along with The Phoenix Project and Continuous Delivery books. The report is one of the few things I’ve found about DevOps that consistently gets people’s attention — even if they’re not familiar with DevOps. The results and the research are that remarkable.
I wrote about the top 5 insights I had from the 2015 State of DevOps Report on Excella’s blog. Check it out and let me know what you think.
‘Tis the season. You know the tune.
On the twelfth day of DevOps, our business gave to me…
12 GitHub repos,
10 deploys a day,
9 Chefs a-knifing,
7 wastes of lean,
6 devs a-pairing,
5 golden images,
4 Jenkins servers,
3 DevOps ways,
And 1 team to help our business win.
Wishing you and yours the very best DevOps has to offer.
Over the last year or two, I have often heard a word used in the DevOps community not usually uttered in IT circles. In fact, outside of the psychology and counseling communities, I don’t hear the word much at all. That word is “empathy”. And the more I learn about DevOps, the more I believe empathy may be the single best tool there is for building bridges and collaboration across boundaries — job #1 when considering a move to DevOps. Using empathy is better than any process, organizational redesign, or automation initiative. Empathy has tremendous power to improve any relationship that matters to you — personal and professional. Whether you’re Dev working with Ops, Ops working with Dev, IT with “the business”, or a parent with your child, everything seems to work better with a healthy dose of empathy thrown into the mix.
You’ve started down the road of a DevOps transformation, but you’re struggling on the journey. You might not be improving the performance of your teams and organization like you had hoped. You’re probably wondering why and, more importantly, how to get back on track. DevOps transformations are hard. If they were easy, everybody would have already gone through them.
Here are a few tips you can use to get things moving more quickly in the right direction.