4 Steps to a People-First Strategy for Optimal DevOps
February 03, 2017

John Gentry
Virtual Instruments

IT teams are often tasked with managing the impossible: supporting the current needs of their organizations while continually developing applications and systems that reliably move business forward — oh, and let's not forget squeezing as much out of their budgets as they can, year after year with only nominal increases. Add to this the rapid pace of technology development and ever-increasing complexity caused by virtualization, hyperconvergence, BYOD and software-defined trends, and you get a perspective of the impossibilities that today's modern IT teams face.

This "new normal" can be thrilling, frightening or both, depending on your perspective. How enterprise IT manages compounding complexities, now and forever forward, affects overall business agility and innovation. With this inconvenient truth in mind, it's no wonder that DevOps and continuous delivery models are a primary focus. The performance and reliability of IT infrastructures delivering today's business-critical workloads is only as good as the accuracy and reliability of the systems monitoring and managing them.

While DevOps and continuous delivery models can (in theory) accelerate technology projects and help them run more smoothly and predictably, the required cultural realignment can prevent companies from reaping the full benefits. Developing and executing an effective strategy means shifting how teams collaborate and interoperate — and we all know how everyone loves change. Here are four steps that enterprise IT leaders are undertaking to facilitate the cultural adaptation and collaboration required to maintain IT and business agility:

1. Get buy-in, train, and enable data-informed collaboration

It seems so simple, but getting everyone on the same page must be the first, and sometimes the hardest, step. It is so important that it's worth repeating: Get. Everyone. On. The. Same. Page. The entire premise of DevOps and continuous delivery rests on the premise of bringing multiple teams together. Only then can you enable innovation, adaptation and transformation.

To make sure collaboration goes smoothly and delivers effective outcomes, focus on the basics. Start with development and operational functions, job descriptions, and similarities and differences. Determine the training and technologies needed to help with the cultural shift. Deploying analytics solutions that enable cross-domain collaboration is critical for aligning teams and helping them perform. These solutions help employees see DevOps transformation as an opportunity for growth, fueled by intelligence that they can consume, act upon and learn from.

2. Start simply, monitor comprehensively and decide confidently

There are several factors to consider when identifying which projects are good candidates to feed into the DevOps process, including overall scope, estimated costs and projected ROI. Start with projects that have a clearly defined and reasonable scope, as well as existing benchmarks. Determine success metrics for expected improvements, enable and monitor data-driven collaboration, and meet your targets.

This effort requires tight collaboration throughout development and operational organizations. Every team has relevant insights, which help form an accurate view of what it takes to deliver a successful project. It's crucial to have the right monitoring solution in place, one that provides a complete understanding of workload interdependencies, effects and how to optimize for overall performance.

3. Enable authoritative understanding and confident collaboration across silos

End users demand flawless experiences, and the ultimate charter for any DevOps team is to meet and exceed end-user demands. While DevOps teams must understand how new feature and functionality releases affect end users, they must also understand how these same releases affect the underlying IT infrastructures delivering them.

Effective DevOps models require close collaboration across multiple silos. To be effective, every collaborator must have an authoritative understanding of what's happening, and the confidence to act. End-to-end performance monitoring with algorithmically driven decision support provides teams with this accuracy and confidence.

4. Remember, DevOps has no "end state"

It's important to continually assess the training and cultural divides you are bridging. DevOps is a new way of life and it's just beginning. Everything is dynamic. Applications aren't static, and neither is the infrastructure that supports and delivers them. There must forever be a vigilant focus on understanding how organically evolving workloads affect the infrastructure. After new releases are put into production, everything must be constantly monitored and tuned for optimal performance.

Without an accurate, real-time understanding of end-to-end performance, every release cycle presents risks that can harm the DevOps process. It's critical to constantly gather and analyze performance data in order to determine how continually evolving workloads affect IT infrastructure performance. DevOps teams then need to use this data to proactively tune and manage infrastructures before emergent issues become actual performance problems.

John Gentry is CEO of Virtual Instruments.

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