Collaborate to Innovate? Fostering a New Kind of Relationship Between Dev and Ops
November 27, 2017

Amir Rozenberg
Perfecto

It has been argued that Dev and Ops teams should work more closely together for some time. For many, the benefits of a closer relationship are clear, and the debate has moved on from "if" to "how," but for lots of companies there are several types of walls to tear down.

The first is the organizational one: some large companies still have a clear distinction in their IT set up; "build the product" (Dev) and "maintain the product" (Ops). But the downsides of this divide are vast. Each department houses specific mindset, responsibilities and performance goals: Developers will be focused on creating new functionality and Operations on maintaining stability.

In some cases there is also a physical separation: Development and Operations teams are located at different floors, different buildings, or even with different companies, thanks to outsourcing. And this separation can result in a "them and us" attitude where ideas aren't shared well enough and collaboration is (albeit subconsciously) discouraged.

How to Collaborate

For most organizations, it's clear that these barriers need to be broken down — and many aspire to create DevOps teams where the two functions work seamlessly together. But it's when we come to the "how" to break down these barriers that debate ensues. For us, a fundamental shift in priorities is needed. Yesterday's model — where one team focuses on delivering software and one team focuses on overall app health in production — is fundamentally wrong and doesn't work in today's world of agility and digitalization. When thinking about fostering collaboration between Dev and Ops, savvy firms must instead think about one team, with shared objectives and shared tools.

But more than this, the focus must shift away from the intricacies of how a team works to rest firmly on delivering against customer expectations. The focus should be on providing useful, delightful and flawless customer experiences — helping enterprises to grow market share, and build and sustain a happy, loyal customer base. And that means organizations needs to design teams around that objective — allowing them to take ownership and designing the right tech stack to deliver and proactively monitor that outcome.

Ensuring Team Independency

The very first "Agile Value" is "Individuals and interactions over processes and tools". So, for us, one of the key elements in driving agility and collaboration in development teams is the notion of team independency. Reduce the team dependencies and they will produce more, and faster.

One implication of this, though, is that teams need to own more of the process themselves. With speed and collaboration must come independence and empowerment.

The status quo for most organizations is not agile-friendly: "production monitoring" (generating awareness of the application health in the production phase) is a task owned typically by a central operations team. The team is usually not enabled on the specific app, and certainly not on new features coming in the next build. They are usually using a separate tool for "Application Performance Management"

This impacts on the ability to work quickly. In real terms — if there is an incident in production (responsiveness degradation or even outage), that the operations teams can't resolve themselves, they typically call on the development team.

Using a separate tool and process, the developer then needs to familiarize him or herself with how that tool is setup. This means that the time to understand the root cause for the incident and the time to resolve it is naturally impacted. All of this while the brands' "front door" is closed due to an outage, impacting customers, the brand and the business.

So, we know that collaboration is critical and a customer-first strategy must be prioritized in order to succeed.

For us, this goes one stage further, as both DevOps and non-IT roles see the need for better integrated toolsets that provide various teams with a composite view of how their systems are performing. But we also recognize that affecting this change isn't always easy or straightforward. And that a starting point is having these conversations, where we come together to discuss our experiences and issues, and work together to solve issues — collaboratively.

Amir Rozenberg is Director of Product Management at Perfecto

The Latest

October 22, 2018

Embracing DevOps at enterprise scale requires a seismic shift in the way an organization plans, builds, tests, releases, and manages applications. Here are four ways to ensure your enterprise DevOps transformation is a success ...

October 18, 2018

Are applications teams prepared to manage the chaos arising from an ever-growing landscape of heterogeneous deployment types? A recent survey of application and operations professionals sought to better understand how the industry is shifting and what the future of DevOps might look like. Here is what the survey uncovered ...

October 16, 2018

More than half of organizations have a dedicated DevOps team to help them better implement agile strategies, accelerate release cycles and ensure continuous development. However, databases have a habit of holding DevOps back ...

October 15, 2018

Test Environment Management can save organizations close to $10,000 for each release, yet only four percent of large enterprises have fully integrated TEM processes into organizational DNA, according to the 2018 Test Environment Management Survey released by EMA and Plutora ...

October 11, 2018

Agile is indeed expanding across the enterprise and there was a significant jump from last year to this year in the percentage of respondents who indicated that all or almost all of their teams were agile, according to the State of Agile 2018 report from CollabNet ...

October 09, 2018

Adopting a modern application architecture is critical to business success and a significant driver of profit growth in today’s digital economy, according to the results of a global survey of IT and business executives released by CA Technologies and conducted by Frost & Sullivan ...

October 04, 2018

How do you integrate tools to enable shift-left performance? The following tools will simplify maintenance, can be managed in a centralized way, and provide an easy-to-use UI to comprehend results ...

October 03, 2018

Focusing at the API layer of an application can help enable a scalable testing practice that can be efficiently executed as part of an accelerated delivery process, and is a practice that can be adopted and enabled at the earliest possible stages of development — truly shifting left functional testing. But what about performance testing? How do we enable the shift left of nonfunctional testing? Here, we explore what this means and how to enable it in your organization ...

October 01, 2018

As businesses look to capitalize on the benefits offered by the cloud, we've seen the rise of the DevOps practice which, in common with the cloud, offers businesses the advantages of greater agility, speed, quality and efficiency. However, achieving this agility requires end-to-end visibility based on continuous monitoring of the developed applications as part of the software development life cycle ...

September 27, 2018

Imagine that you are tasked with architecting a mission-critical cloud application. Or migrating an on-premise app to the cloud. You may ask yourself, "how do the cloud savvy companies like Airbnb, Adobe, SalesForce, etc. build and manage their modern applications?" ...

Share this