Skip to main content

Your Dad's DevOps is Dead

Agile.  Test Driven Development.  DevOps.  All of these terms represent phases that the application development community, as a whole, have gone through for various reasons.  Whatever the reason, however, they all miss the mark.  Yes, I just said that.

Several years ago, I conducted a webinar entitled Agile is Dead.  The title wasn't only incendiary to those who attended; I even heard from the agile project management solution's product team who decried my title as an attempt to force them into irrelevancy.

"Never mind that," I told them.  "Listen to what the content is all about."  What was the content then, and why am I bringing it up now?

Back then, I argued that Test Driven Development was a fallacy because the one thing that was immutable was the release date.  Forcing developers to spend time developing test cases to be solved and that leaves developers less time to write the code that satisfies the test cases that they developed.  It was a relevant point then, but it's even more relevant now.

Remember:  there are a bevy of companies that do the same thing as your company.  Many of them are smaller, more nimble (by definition) companies.  And so giving your customers any excuse to go to them is a bad idea since, after all, your customers simply want to accomplish their own goals, e.g. by a new knick-knack that they feel they need.

Don't believe me?  Ask Amazon, which calculated in 2012 that it would lose $1.6B (that's billion) in revenue because of a 1 second delay in their shopping cart processing code.  1 second would cost them 10 digits of revenue.  And that's not just theoretical either - the news is littered with similar examples where a poor customer experience resulted in a huge impact on revenue.

Going back to my original point:  DevOps is dead.  In fact, I'd argue that it was never alive in the sense that it was the driving force behind business decisions.  Instead, it was the result of the recognition that the consumer landscape has irrevocably changed and, if companies aren't more mindful of the perceived value of the end result, their customers will leave.

Consider for a moment that statement.  A poor customer experience will result in a drop in revenue.

In March 2017, a study was conducted by Customer Gauge to determine the impact of Net Promoter Score (NPS) on revenue.  What they determined was that a 10 point increase in NPS corresponded to a 3.2% increase in revenue.  And while they didn't look at the converse of that conclusion (i.e. how much revenue is lost due to a 10 point drop in NPS), it's reasonable to conclude that there will be a drop of similar magnitude.

What does this all mean?  It means that you should stop focusing on whether development and operations can come together, hold hands, and sing kumbaya.  Instead, there should be a recognition that all parts of your company need to work together to ensure an exemplary customer experience.  There is no development or operations.  There is only the brand of your company and the effect that each individual has on that brand's value.

Popular posts from this blog

"Ni jiang yi yang de hua ma?"

Last week, I wrote about the necessity of having a clear message . Because this topic is so important I decided to follow-up with another entry on this general subject. This week we will approach it from another angle. (For the curious, the title says " Do you speak the same language? " in pinyin, which is a transliterated Mandarin Chinese.) Recently, a good friend of mine (who is Chinese, ironically) and I were playing pool. He had to bank the 8-ball in the pocket to win the game, and since it was an informal game and bank shots are my area of expertise, he asked me for advice. I told him, "you just need to strike the cue ball with medium speed so that it hits the 8-ball right in the middle." He didn't believe me so we marked the positions of the balls, and then he took his shot only to watch the 8-ball sail past the pocket. "A-ha!" he exclaimed. "I told you it wasn't that easy." But when we reset the positions and I made an attemp

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While that

Is No/Low-Code the Key to IT Nirvana?

 Unless you've had your head in the sand for the past year or so, you've seen the phrases low-code  and no-code  bandied about quite frequently everywhere you look.  You've probably wondered if this is something new that's here to stay or just a "flash in the pan."  Although the terms have been in the fore of the IT trade publications recently, Low Code Development Platforms (LCDP) (and the corresponding No Code Development Platforms) have been in existence since 2011.  Their roots can be traced to the 90's with 4th generation programming languages and GUI-assisted programming paradigms, e.g. IBM VisualAge for Basic, which was discontinued in 1998. For those of you who aren't familiar with either, the premise is that these platforms allow someone to quickly build applications using a WYSIWYG interface and a "click and configure" paradigm to Isn't this the source code to Roblox? rapidly build full applications with little or no coding requ