Top Culture Changes to Make DevOps a Reality - Part 4
October 31, 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 4 covers development and testing.

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

25. START SMALL

The best way to introduce a DevOps culture to your organization is to start small and scale from there, repeatedly demonstrating success in larger and larger increments. The first step in a DevOps cultural shift is ensuring everyone understands that they control their own destiny. Give everyone the visibility they need to do their job right and share accountability evenly – each member of the team needs to know they have full ownership of their work and processes, and responsibility for company success. When this happens, developers and operations see each other as teammates working to deliver value to the customer and business, and it creates the foundation of self-service, prioritization and people required for getting DevOps right.
Eric Sigler
Head of DevOps, PagerDuty

26. SOFTWARE FACTORY

Currently, most organizations view software creation as a set of artisan engineering projects. To make DevOps a reality, organizations should consider software generation more of a factory exercise where small components are built, connected, and reused in multiple ways to create different products. Because the components become smaller, they warrant smaller but multidisciplinary teams that bring all the needed expertise to successfully produce the components (and eventually the larger products). In this type of environment, architects, developers, testers, and InfoSec individuals solve small problems rapidly and creatively ultimately to accelerate the business and make the organization more agile.
Amir Sharif
Co-Founder, Aporeto

27. CONTINUOUS IMPROVEMENT

The most important thing is to place a strong focus on Continuous Improvement. Changing the culture to one that continuously seeks out ways to improve the processes, tools, teams, and individuals will unlock benefits of DevOps such as Continuous Delivery and resilient systems.
Jason Hand
DevOps Evangelist, VictorOps

Companies need to foster a culture of continuous improvement, which penetrates itself into all facets of development and operations. This culture of improvement should be generated through multiple factors, such as persistent problem-solving, agility, and constant communication between teams. One top reviewer on IT Central Station suggested that a company can use APM to support such a culture, using the different monitoring points as gauges for constant improvement. A consistently positive end-user-experience can be one of the threads in this fabric of continuous improvement, becoming the yardstick by which to measure application performance
Russell Rothstein
Founder and CEO, IT Central Station

Check out Release Automation reviews on IT Central Station

28. TRAINING

Allow time for training. This requires a dedicated training budget that people know how to access. People should be able to choose training they find most interesting, rather than being restricted to specific manager chosen topics – even if it isn't directly applicable to what their job is today.
Tim Zonca
VP of Product Marketing, Puppet Labs

Read Tim Zonca's blog on DEVOPSdigest: Culture is Key to DevOps

29. ELIMINATE TICKET CULTURE

The most important cultural change an organization can make in pursuit of DevOps is to rid the organization of the ticket culture. Service/help desk solutions can be valuable however, too often they are used in a way that encourages an "us vs them" mentality. Some solutions are to augment the ticket system with instant messaging for chatops, use a shared automation solution for dev, QA and Ops and have Ops personnel on the dev/scrum team.
Brian Dawson
DevOps Dude & Jenkins Marketing Mgr, Product Marketing, CloudBees

30. OPERATIONAL ACCEPTANCE TESTING

In order to make DevOps a genuine reality organizations need to consider the whole development and testing process – in the round – and not just focus on what we would describe as "Check-Box Testing." They need to look beyond the confines of functional testing if they are to ensure applications will work effectively when deployed into the real world. In order to achieve this, they need to consider external factors that will impact the user experience such as the networks, private and public, over which the great majority of applications are expected to be delivered over these days. Therefore, all organizations need to broaden their DevOps horizons to incorporate the new discipline of Operational Acceptance Testing which is used to conduct operational readiness of a product, service, or system before it is introduced into the live production environment.
Peter White
Operations Director, iTrinegy

31. CONTINOUS TESTING

Continuous Testing is a fundamental element of DevOps. You cannot do Continuous Integration and Continuous Delivery without continuous testing. Without continuous testing, the net result is that testing process can't keep up with your development speed. You might accelerate your release cycle only to find out more problems in production. Not good. Both Continuous Integration (CI) and Continuous Delivery (CD) are almost meaningless without continuous testing.
Paola Moretto
Founder and CEO, Nouvola

32. RELEASE FAST, CATCH PROBLEMS IN PRODUCTION

Perfect quality should never be a blocker. Successful DevOps teams move quickly and build their software in such a way that the it can be released to production fast and at any time. This requires team focus to shift to catching problems quickly after release with monitoring, canary environments, traffic shaping and roll-back tools rather than trying to prevent them from being released.
Dana Oshiro
General Partner & GM, Heavybit

33. GO BEYOND CONTINUOUS RELEASE AND DEPLOY

In order for DevOps teams to meet their application service level objectives, they need to go beyond continuous release and deploy. Keeping these applications up and running requires real-time analytics of the data throughout the entire application infrastructure — including performance data, logs, configuration and topology, which will automatically show the impact of a software release on the operations in the continuous delivery and integration mode.
JF Huard, Ph.D.
Founder and CTO, Perspica

Check out Top Culture Changes to Make DevOps a Reality - Part 5, offering some final thoughts.

The Latest

May 25, 2017

DevOps brings Development and Operations together with the sheer objective of ensuring quality and enabling faster time to market. However, what happens to QA in this scenario? How does the Testing team fit in? Let's ponder on this further and understand the role of QA and Testing in the DevOps world ...

May 23, 2017

When organizations adopt containers and microservice style architectures in production, systems become incredibly complex. For operations it's a shock because it means coming to grips with many new container tech nuances - plus letting go of the old monitoring rule book ...

May 22, 2017

Managing application performance today requires analytics. IT Operations Analytics (ITOA) is often used to augment or built into Application Performance Management solutions to process the massive amounts of metrics coming out of today's IT environment. But today ITOA stands at a crossroads as revolutionary technologies and capabilities are emerging to push it into new realms. So where is ITOA going next? With this question in mind, DEVOPSdigest partner site APMdigest asked experts across the industry for their opinions on the next steps for ITOA ...

May 18, 2017

In Part 3 of my Q&A with industry analysts, I ask: What trends will have the biggest impact on the software industry and DevOps in particular this year and beyond? How can enterprises set themselves up to succeed with so many rapid changes occurring in development and delivery? ...

May 16, 2017

See how to turbo-charge the impact of APIs, according to a global study conducted by CA Technologies ...

May 15, 2017

APIs are vital components for business success and thriving in the application economy, according to a global study conducted by CA Technologies ...

May 11, 2017

In Part 2, I'll dive into some findings from CollabNet's outreach to industry analysts. I asked them about the greatest challenges facing enterprises venturing into the world of DevOps and to touch on what lies ahead for the future of the DevOps movement ...

May 09, 2017

DevOps teams bring significant benefits to their organizations. Unfortunately, DevOps teams, like many business programs, tend to believe innovation must come with a detriment to security. Security measures are often seen as obstacles that impact the agility that DevOps teams rely on ...

May 08, 2017

With increased competition, enterprises now require greater agility than ever before, and traditional approaches simply can’t provide the speed enterprises demand. To remain competitive with these new players, companies need to improve their operational agility both in the data center and the WAN ...

May 04, 2017

There is no "right" culture for DevOps, but characteristics such as open communication, high cooperation, collaboration, respect, and trust are essential. If your organization does not have these characteristics, they must be developed. Culture is learned, not inherited. It must be genuinely nurtured by everyone from executive management on down the line. Here are some hacks to help develop a positive DevOps culture ...

Share this