Gene Kim: Charting DevOps Milestones and Metrics
To advance your DevOps efforts and drive success, you need to understand precisely where you stand
February 22, 2016

Aruna Ravichandran
CA Technologies

For those of us deeply immersed in the rapidly advancing DevOps revolution, sometimes it’s hard to remember that we're still early on in this game.

As discussion of "unicorn" adopters has grown somewhat weary – given that these organizations tend to be those whose business models lend themselves to transformation – practitioners have made it abundantly clear that they seek more practical guidance as to where they should expect to find themselves on this journey.

Despite his status as one of the recognized "godfathers" of DevOps, or at the very least one of its most visible spokesman, noted entrepreneur and author Gene Kim (co-author of The Phoenix Project and other seminal works) remains intimately connected to the movement's real-world standing through his continued thought leadership work.

Based on this close connectivity to practitioners – those with both advanced and more nascent initiatives – there's perhaps no better person to ask which milestones, challenges and performance metrics represent the hallmarks of today's existing DevOps adopters.

In a recent interview, Gene shared some interesting feedback on what he's hearing out on the conference circuit and elsewhere in speaking to various stakeholders about their current DevOps strategies.


Filmed at CA World '15, the interview is definitely worth viewing in its entirety, as it touches on timely DevOps maturity topics, including:

Milestones

According to Kim, there is palpable progress being made related to the continued expansion and strategic import of DevOps adoption, namely:

■ DevOps is in fact spreading rapidly beyond the realm of unicorns –finding a home in many different types of organizations, from financial service providers to old-line product manufacturers, among others.

■ Those people spearheading and supporting DevOps transformation within their organizations are rapidly climbing the ladder, with many of the practitioners he meets being promoted and granted greater responsibility.

■ Organizations are expanding their initial (local) DevOps initiatives to take on more far-reaching (global) influence, across a broader swath of projects, with even greater impact on their overall business strategies.

Challenges

Based on some ongoing research, Kim said there are five primary challenges that most organizations are working to address today, related to:

■ Automated Testing: Practitioners are still attempting to increase the scope of automated testing to include more of their legacy assets.

■ Cultural Change: How successful organizations have been in driving transition of workflows, roles and responsibilities remains an issue.

■ Security Acceleration: Advancement of security and compliance processes remains an area where most DevOps practitioners cite the need for more work.

■ Operations 2.0: With far more IT operations work being carried out using self-service models, organizations are still working to ensure consistency.

■ Building Metrics:Organizations also remain highly focused on the creation and management of proper metrics to help assess their progress.

Metrics

In terms of leveraging metrics to deepen internal DevOps buy-in, and further drive home the overarching business case, today’s critical metrics include:

■ Lead time: Specifically, how quickly organizations can move from “code committed” through required testing cycles and into deployment.

■ Deployment rates: Obviously the endgame of DevOps is increasing responsiveness and getting apps in the hands of users more quickly.

■ Change success rates: Because DevOps isn’t only about getting releases out the door, it’s also about the overall quality of those resulting updates.

■ Mean-time-to-repair: This is another no brainer, as leveraging DevOps to find and fix emerging apps issues is at the core of the entire movement.

Worth noting, the research project that Kim is referencing, which surveyed over 20,000 organizations, also concludes that DevOps "high performers" continue to greatly outpace their peers in how they chart progress related to those metrics.

The very nature of DevOps is such that every element of the SDLC is treated like a work-in-progress. Yet, one of the critical elements of advancing your overall effort and driving success is understanding precisely where you stand.

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