The 2017 State of DevOps Reportis out. As in previous years, it provides a lot of information about the state of DevOps within the industry and some of the important factors that differentiate high-performing organizations from their non-high-performing peers. I noted a few highlights from this year’s report: the impact of leadership, the continued misconception about the perceived tradeoff between throughput and stability, and autonomy with teams and architectures.
A few years ago, I went through some executive coaching individually and as a group. In one of the individual sessions, the coach and I were talking about my team and the meetings I had with them. The coach asked me how I wanted someone on my team to feel after meeting with me. I had to think about it because I had never been asked that question before. And yet, it was an incredibly important answer to have. After a minute or two, I came up with the following answer. Continue reading →
I’ve heard a lot of questions about DevOps, audit, compliance, and how they all fit together. I’ve fielded more questions from more people recently. In my mind, that means more people are applying DevOps patterns and practices to their work and the work they’re doing is real (as opposed to sandbox, pilot, or “let’s try this stuff out” projects). Why else would they be interested in audit and compliance?
Here are some resources that might be helpful if you’re “doing the DevOps” and interested in making audit and compliance efforts go more smoothly. Continue reading →
I delivered a talk entitled “Decoding Culture: Beyond the Fluff and Back to Business” to an engaged group at the inaugural DevOpsDays Baltimore event on March 7, 2017. At the end of the talk, I promised to provide info on the resources I referenced. Continue reading →
Lots of organizations struggle with legacy systems. Or more to the point, they struggle to maintain and make changes to them in a way that provides the pace and value the organization wants. So given the scale of this issue in the Federal Government, ACT-IAC took a crack at providing a “best practice” approach for modernizing legacy systems in the white paper I just referenced.
I read the paper a couple of times. I definitely had some strong thoughts and feels as I read it. I couldn’t keep them bottled up so I suggested some changes to how the Government should think about legacy systems modernization on Excella’s blog. I could’ve written a lot more (like on the role of DevOps, which shouldn’t be in the “DevOps/Sustainment” phase — see page 20 in the white paper), but the post was already getting lengthy. Let’s consider this a good start for discussion and iterate from there.
I started my career as a developer. My success was determined largely by how much I could produce and how fast I could produce it. I was an “individual contributor.” As I grew in my career and gained experience and perspective, I realized a couple of things. First, what I could produce was insignificant compared to what a high-performing team could produce. Second, what I most enjoyed was not producing stuff myself — it was creating opportunities for others to be happy and successful. (That’s now my personal mission statement.)
I decided I had to become a better leader because, regardless of what title I had, that was my real job. Becoming a better leader was the only way I was going to be successful — as defined by the success of the people, teams, and organizations I led.
I’m not that interested in the charismatic leaders or leaders who succeed by “force of personality.” I’m more interested in leaders who put systems in place and create environments for the people and organizations they lead to be successful. I can’t “be” anybody else — but I can learn the principles, values, and systems they used for their success and adopt what I think will work for me.
I’ve discovered some “go to” resources in my quest to become a better leader. These resources achieved that “go to” status based on how useful they are to me — measured primarily by how often I reference them and how much they’ve shaped how I think, speak, and act. Continue reading →
“Performance more often comes down to a cultural challenge, rather than simply a technical one.”
— Lara Hogan, Engineering Director, Etsy
Culture has a huge impact on the performance of an organization — for better or worse. In fact, some say culture is the only sustainable competitive advantage an organization can have. Despite culture’s importance, it has also been “fuzzy” and notoriously hard to quantify. The problem has been that we’ve had no good way of describing, assessing, or measuring culture. That changed when Dr. Ron Westrum, a sociologist, came up with his “Three Cultures Model”.
The 2016 State of DevOps Report is out and carries with it some fantastic information — just like the 2014 and 2015 versions. I love the statistics and the research — and the support it provides in making the case for DevOps. This year’s version even more so because it covers the topics of employee engagement and ROI.
At Excella, I lead our Services organization — really the “what” and “how” of our business. One responsibility in my organization is establishing partnerships to complement what we do. A partnership can deliver value to us, our clients, and our partner if established for the right reasons and managed correctly. For example, we are currently a partner with both Microsoft and AWS and they’ve both been win (clients) – win (partner) – win (us) relationships.
Occasionally I’m asked to look at new partnerships — either by an Excella employee or by a potential partner. These opportunities led me to think about the criteria for exploring a new partnership. Continue reading →