Top Culture Changes to Make DevOps a Reality - Part 5
November 02, 2016

DEVOPSdigest asked experts across the industry – including analysts, consultants, vendors and even users – what they think is the most important cultural change an organization can make to ensure DevOps success. The result is a broad range of answers that delves deep into what DevOps is really all about. Part 5 provides some final recommendations you may not have considered.

Start with Top Culture Changes to Make DevOps a Reality - Part 1

Start with Top Culture Changes to Make DevOps a Reality - Part 2

Start with Top Culture Changes to Make DevOps a Reality - Part 3

Start with Top Culture Changes to Make DevOps a Reality - Part 4

34. COMMON TOOLSET

It is important for the teams to use the same toolset for tracking development and operations tasks as well as for managing their environments so that everyone is looking at the same data at all times These practices can indeed help in breaking the silos between Dev and Ops.
Payal Chakravarty
Program Director, Product Management - IBM APM

DevOps processes and tools focus mostly on build-release-test-configure part of the DevOps world. I have learned that transparency of deployed solutions is a key ingredient that ties the operations and development teams together. When both teams are looking at production deployment through the same pane of glass that exposes performance and potential problems, the collaboration between the two worlds is significantly increased.
Ivo Mägi
Co-founder and Head of Product, Plumbr

35. AUTOMATION

Embrace automation. As your teams collaborate more around processes they need to become natural "automators" that automate the everyday so the rest of the team can focus on the innovation for tomorrow.
Ron Gidron
ARA Evangelist, Automic Software

Understanding and accepting the role of automation. While this may seem to be a technical issue, at its core there is always a significant cultural change that comes with automation. Compressing release cycles is made possible by automating repeatable tasks and managing exceptions as opposed to process. It is at the heart of DevOps. But it requires a cultural change that goes beyond the implementation of tools – it forces the collaboration between developers, testers and operations that will break down what are often very siloed organizations. In a way, automation is the change agent to build the culture of cooperation needed to make DevOps a reality.
Dave Murphy
SVP Delivery, SOASTA

For DevOps to become a reality, developers need to pay close attention to the operational challenges faced in deployment of applications. By embracing methodologies such as software-defined visibility, advanced automation techniques can be employed by developers to not only gain visibility into data-in-motion in their infrastructure but also avoid building IT silos. Nowhere is this more important than in the devsecops world, where security orchestration across multiple stacks can be accomplished by developers using such a paradigm.
Ananda Rajagopal
VP of Product Management, Gigamon

36. METRICS

Ask for metrics. DevOps emphasizes measurement of key performance indicators followed by continuous improvement. Getting the teams to focus on metrics at the beginning is important to enable this process.
Joan Wrabetz
CTO, Quali

37. CENTRALIZED CLOUD STRATEGY

The top culture change to make DevOps a reality is create a centralized cloud strategy for a cloud service platform that turns the CEO's digital transformation vision into reality. All the Digitally charged initiatives are dependent on a solid cloud strategy yet most company's have hybrid cloud services by happenstance. Top performers interviewed for iSpeak Cloud, built a cloud service platform based on the principles of DevOps as the CORE tenant of Digital Transformation. The governance team for the CSP was comprised of leadership across critical roles in the company not just IT to enable impacting budgets and business case before they were decided. Services were categorized to ensure streamlining manual processes such as security reviews, automating change, incident, and first level self healing. The platforms were built on open source with orchestration and integration to current tools for ITSM as a tenant. This approach automated onboarding and reviewing services created from shadow IT processes. It also provided a voice and input from the business to reduce the recurrence of Shadow IT by having input into the solution.
Jeanne Morain
Strategist and Author, iSpeak Cloud

Read Jeanne Morain's latest blog on DEVOPSdigest: Top 5 DevOps Challenges & Solutions

38. DEVOPSEC

Ensure that security testing is integral to DevOps. Often security testing is run by a separate group for compliance reasons. But, this doesn't mean that it should be performed outside of the DevOps process. In fact, incorporating security and compliance requirements into the DevOps processes can generate a big return in terms of security and compliance outcomes.
Joan Wrabetz
CTO, Quali

Security teams need to adapt and optimize their business processes for DevOps. They need to make it fast and easy for DevOps to develop code and run it safely. Today, most security teams still require DevOps teams to use security controls that are slow and manual. One great example of challenge is the use of encryption: it can take days and multiple security approvals for DevOps to get publicly trusted certificates for their code and services. Automating the process making keys and certificates available through an API service is a fundamental improvement that can make the lives of DevOps teams much better. Automating this slow, manual process will dramatically improve the speed of DevOps teams while, at the same time, improving security and policy compliance. This is DevOpsSec.
Kevin Bocek
VP of Security Strategy and Threat Intelligence, Venafi

39. TRANSFORM THE ORGANIZATION

Culture is germane to the success and ethos of DevOps, however, to paraphrase Frances Hesselbein, you don't change culture, you transform the organization. (Culture follows naturally). Challenge the norms, flatten hierarchy, and aggressively adopt people-centric technologies that drive transformation, and change behavior.
Richard Whitehead
Chief Evangelist, Moogsoft

40. FOCUS ON END USER EXPERIENCE

The most impactful culture change needed to make DevOps a success in any organization is a shift in focus from simply "running infrastructure" and ensuring "uptime," to true application performance and the end user experience. When an IT team is aligned behind these two factors, they naturally collaborate, think about performance metrics differently and find new ways to make things work well. There will also be a sense of urgency that makes it easier to introduce short sprints and other process improvements.
Gerardo Dada
VP, Product Marketing and Strategy, SolarWinds

41. FOCUS ON THE CUSTOMER

DevOps means breaking down silos to improve collaboration, bringing specialists together to create multi-skilled teams, and creating an environment in which it's safe to fail. However, all these changes are really in service of the biggest change needed for DevOps success – aligning everyone to the customers' needs. Ultimately, DevOps means bringing the whole business together in service of delivering value to the customer.
Lucas A. Welch
Director of Communications, Chef

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