The Valentine's Day DevOps Challenge: Who Do You Love?
February 14, 2017

Aruna Ravichandran
CA Technologies

Everybody loves DevOps. In fact, DevOps is the hottest date in IT. That's because DevOps promises to satisfy the deepest longings of digital business — including fast execution on innovative ideas, competitively differentiated customer experiences, and significantly improved operational efficiencies.

But who does DevOps love?


This is more than a cute Valentine's-themed question. It's a fundamental challenge for anyone leading a DevOps initiative. What passions and motivations are driving your DevOps teams? How do you know? And if those motivations aren't the right ones, how do you re-direct them?

Metrics, it turns out, may hold the answers.

The Danger of DevOps Narcissism

Many of us know what it's like to be in a relationship with a narcissist. Narcissists can actually be very attractive. They maintain the best possible outward appearance and exude confidence. They can also be quite charming and seductive.

But relationships with narcissists ultimately turn out to be quite toxic, because narcissists only love themselves. So they use our feelings for them to meet their own emotional and material needs—giving us little or nothing in return.

Left unchecked, DevOps can easily devolve into a similar state of narcissism. Technology professionals, after all, typically love technology. So as they catch DevOps fever, they start to view DevOps, agile and continuous delivery as objectives to be pursued for their own sakes.

There is nothing wrong with having a DevOps team that is super-enthusiastic about DevOps excellence. You want your team to be excited about DevOps best practices and DevOps-enabling tools.

But enterprises aren't investing millions in DevOps so that IT can congratulate itself. It's investing in DevOps to address an existential business challenge. DevOps narcissism is thus potentially quite toxic.

One way to detect creeping DevOps narcissism is through the metrics by which DevOps performance is measured. Narcissistic DevOps teams focus on narcissistic metrics (also known as "vanity" metrics). These metrics include lines of code produced and function points created. Leaderboards and gamification can also both indicate and promote DevOps narcissism — especially if they utilize vanity metrics to keep score.

Romancing the Business

The proper object of DevOps affection is, of course, the business. The whole point of DevOps is to accelerate time-to-benefit for business-driven digital deliverables produced by agile development — while also diligently addressing performance at scale, production economics, security, compliance, business continuity and other digital business requirements.

DevOps therefore can't just look inward. It must look outward to see how well it is communicating and collaborating with all relevant digital stakeholders in order to achieve the goals of the business.

What metrics best indicate alignment of DevOps efforts with the business? There are several—but I'll just highlight one here: NetPromoter. NetPromoter scores (NPS) are broadly used by organizations to quantify the customers' perceptions about the quality of their engagements. I won't weigh in here regarding the concerns CX professionals have about excessive reliance on NPS vs/ other CX metrics. I'll simply point out that, whatever its flaws, NPS is a far more business-directed metric than lines of code or function points. And, as such, it is a much-needed antidote to DevOps narcissism.

NPS is also practical to obtain and immune from corruption by DevOps staff — two key requirements for any management metric.

Other metrics (cycle times, FTE-to-customer ratios, MTTR, etc.) can also be very useful for DevOps leaders. And I'll write more about them in future blogs.

But on Valentine's Day, it's appropriate to ask a relationship question. Yes, everyone loves DevOps. But who does DevOps love? If it's not the business, then there's going to be some heartbreak. And that heartbreak is likely to come in the form of failed expectations and subpar business outcomes.

For more tips on measuring your DevOps success, check out the book DevOps for Digital Leaders, it's all about how one can reignite their business with a modern DevOps-enabled software factory.

Aruna Ravichandran is VP, Product & Solutions Marketing, DevOps, CA Technologies.

The Latest

March 23, 2017

Mature development organizations ensure automated security is woven into their DevOps practice, early, everywhere, and at scale, according to Sonatype's 2017 DevSecOps Community Survey ...

March 21, 2017

When it comes to food, we all know what's considered "good" and what's "bad". We can all understand this simple rule when eating. But for many, when it comes to software development, simple rules and advice from nutritional labels aren't always there for us ...

March 20, 2017

Monitoring and understanding what software is really doing, and maintaining good levels of software quality is increasingly important to software vendors today. Even a minor bug is capable of shutting down whole systems, and there is a real risk that development cycle pressure competes with quality assurance best practices ...

March 16, 2017

More than half (54 percent) of IT professionals surveyed indicate they have no access to self-service infrastructure, according to a new DevOps survey of 2,000 IT industry executives by Quali.This means that more than half of respondents take a ticket-based approach to infrastructure delivery, impacting productivity and increasing time to market ...

March 15, 2017

Driven by the adoption of cloud and modernization of application architectures, DevOps practices are fast gaining ground in companies that are interested in moving fast – with software eating everything - between "write code and throw it across the wall" to creating more pragmatic mechanisms that induce and maintain operational rigor. The intent behind DevOps (and DevSecOps) is quite noble and excellent in theory. Where it breaks down is in practice ...

March 13, 2017

There might be many people across organizations who claim that they’re using a DevOps approach, but often times, the “best practices” they’re using don’t align with DevOps methodologies. They can say what they do is “DevOps”, but what we’ve found is that many are actually not following basic agile methodology principles, and that’s not DevOps ...

March 09, 2017

The velocity and complexity of software delivery continues to increase as businesses adapt to new economic conditions. Optimizing and automating your deployment pipelines will dramatically reduce your lead times and enable you to deliver software faster and with better quality. Here are three more most common areas that generate the longest lead times ...

March 08, 2017

Every enterprise IT organization is unique in that it will have different bottlenecks and constraints in its deployment pipelines. With that being said, there are some common problem areas that typically produce the longest lead times in your software delivery process. Here are the most common areas that generate the longest lead times ...

March 06, 2017

The findings of an independent survey of IT leaders, application developers and database administrators, conducted by IDG Research for Datical, indicate that database administrators are unable to keep up with the pace and frequency of database changes caused by the accelerated pace of application releases, thus creating a bottleneck and delaying digital transformation initiatives. An overwhelming number of databases administrators (91 percent) and application development managers (90 percent) cited database updates as the cause for application release delays ...

March 02, 2017

A "Boost Caboose" is a secondary engine pulled on a trailer for the explicit purpose of increasing the output of the primary engine. In many ways, DevOps is its own form of Boost Caboose for application of agile methodologies within the modern software factory and SDLC/ADLC processes ...

Share this