17 Ways to Define DevOps - Part 3
What Does DevOps Mean to You?
November 19, 2015

DEVOPSdigest asked experts from across the industry to define what DevOps means to them. The goal is to show just how many varied ideas are connected with the concept of DevOps, and in the process learn a little more what DevOps is all about. The third installment shows the impact of DevOps on both Dev and Ops team members.

Start with 17 Ways to Define DevOps - Part 1

Start with 17 Ways to Define DevOps - Part 2

8. EMPOWERING DEVELOPERS

DevOps takes away the friction between software developers and a traditional ops team by entrusting developers with responsibility for the products they build. It's not about giving developers more work to do — it's about giving them the power to get the whole job done rather than a small portion of it.
Ryan Park
Principal Infrastructure Engineer, Runscope

DevOps is a philosophy that places value on developers owning responsibility for service operations to enable a high velocity of infrastructure change without sacrificing service quality. It's less an organizational structure and more of a cultural transformation. By embedding operational discipline in the development process, technology-driven companies deliver better products faster. It's the only way for teams to deliver modern apps at scale.
Dan Turchin
VP of Product, Big Panda

9. EMPOWERING OPERATIONS

I see DevOps as official recognition that the classic model makes operations people frustrated with software developers, and vice versa. People whose natural instinct is to fix things rather than point fingers will not be shy about looking over the shoulder of the person in the other chair, and collaborating to remove obstacles. DevOps makes that part of an actual job description, rather than an unrecognized reality.
Thomas Stocking
Director of Sales Engineering, GroundWork

10. CROSS-FUNCTIONALITY

We can talk about agility, automation and collaboration til the cows come home, but DevOps is about people being generalists vs. specialists. Having a broad understanding of how to build and support applications, networks, databases and storage will become invaluable in cloud environments where nearly every service is built using APIs vs. bespoke code. When something breaks or goes wrong you shouldn't need experts to troubleshoot different areas of your environment, you need generalists who can leverage the insight that their APM, NPM and ITOA toolsets can provide.
Steve Burton
Chairman, VP of Product Marketing, Moogsoft

No matter what exact definition and flavor of DevOps an organization is following, I think a key element of DevOps is to have developers who act and think like ops people, and vice versa. Developers who are on-call and held accountable for ensuring that their code doesn't just do well in the lab environment, but is easy to operate and doesn't break under real-world circumstances will produce better applications.
Sven Dummer
Senior Director of Product Marketing, Loggly

11. BREAKING DOWN SILOS

DevOps is an amalgam of strategy, culture, methodology, architecture and technology that enables dev teams to break down silos and cumbersome frameworks in teams, systems and tech so that they can ship whatever they want whenever they want with higher quality and lower cost.
Steven Anderson
CEO, Clutch

DevOps means mitigating any and all constraints in order to roll out high-quality, high-performance software, faster, regardless of platform. Traditionally, mobile/distributed teams work in very different silos from mainframe teams. Each with their own distinct culture. Unfortunately, the characteristics of mainframe systems and culture can cause an overall software development effort to encounter slowdowns, or even come to a screeching halt. Fortunately, mainframe ISVs are making tremendous strides in modernizing and evolving these systems for non-mainframe experts, enabling a faster, more agile platform that can keep up with the pace of DevOps while nurturing innovation.
Christopher O'Malley
President and CEO, Compuware

Devops is about driving application transformation. Making things and people work not only as "islands" but a cool ecosystem of software development and infrastructure that is fueled by a passionate team attitude.
Stacy Gorkoff
VP, Strategic Marketing, INETCO

To achieve DevOps success, organizations must shift from silo-based management of their application infrastructures to a collaborative approach that offers end-to-end, correlated visibility to all stakeholders. This will enable faster and more accurate problem resolution, improved end-user satisfaction , rapid optimization and enhanced planning to scale the business for the future.
Arun Aravamudhan
Senior Product Architect, eG Innovations

Read 17 Ways to Define DevOps - Part 4, outlining the many approaches and tools associated with DevOps.

The Latest

April 27, 2017

In a movement that has gained momentum as quickly as DevOps has, it's always good to stop from time to time and evaluate where we are, where we have come from, and where we are going. We asked four industry experts some questions about the progress of ALM and DevOps ...

April 26, 2017

It's easy to ignore downtime. But ignoring downtime is a surefire way to upset your customers and your colleagues. More and more, teams need to think about shipping stellar experiences. Proper incident response is a great place to start ...

April 24, 2017

The expectation of regular software updates – it's what developers are tasked with, and what users expect and demand. Increased functionality, better performance, and fewer bugs – often in a week or less. Automation of critical processes such as QA can help meet the gargantuan task of constant updates, but it can also send your software into a death spiral of user abandonment unless deployed correctly ...

April 20, 2017

One could argue that testing is the most important phase of an IT project. It's also time-consuming and expensive. It's essential to strike a balance between an IT testing program that ensures a quality product and the cost-to-value ratio of your project. But when you're dealing with replatforming projects, how much testing is enough testing? ...

April 18, 2017

Whether through formal methods such as classroom or virtual training, job shadowing, and mentoring; or through informal methods such as team discussions or presentations, teaching needs to be a frequent element of team integration. It is a given that IT and business teams have difficulty understanding each other without a common taxonomy. Even teams within IT often fail to understand each other ...

April 17, 2017

Although DBAs fortunately have the rare ability to bridge the gap between development and operations, they have been detrimentally overlooked in many companies that deploy DevOps practices. A DBA's ability to interrogate code and construct a resilient, well–performing database environment uniquely defines the capabilities needed for DevOps – leaving me perplexed about why DBAs were not one of the first operations team members asked to join the DevOps movement ...

April 12, 2017

DEVOPSdigest asked experts across the industry — including analysts, consultants and vendors — for their opinions on the best way for a development or DevOps team to become more Agile. Part 5, the final installment in this series, provides tips on empowering people ...

April 10, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 4 covers DevOps technologies ...

April 07, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 3 provides some tips for getting started and gaining feedback ...

April 05, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 2 covers processes including automation, continuous delivery and testing ..

Share this