Communicating: “Communication has to be simple and streamlined. No administrative or bureaucratic barriers,” said Yarko. “Less long meetings, more openness to asking questions and solving problems on the spot. We believe that solving problems quickly and early is key to making the transition smoother.”

Not replacing your teams: According to Serena’s Fish, some organizations go down the route of hiring an entire DevOps team, intending to have it replace existing teams. But all that does is create another silo within the organization. “It is an interesting approach, but unfortunately it just leads to the same levels of heartache that organizations have been trying to move away from—the whole notion of isolation and silos that we want to break down,” he said. “So certainly don’t put a team in place to purely perform DevOps. It just creates another silo.”

Not being afraid of the term “DevOps”: According to Serena’s Levy, people were afraid that agile was going to ruin the entire software engineering industry, but it didn’t. So they shouldn’t be afraid that DevOps is going to be the same thing. It is all about creating cross-functional teams and delivering better software; DevOps is just a term, he explained.

DevOps in some ways is not a totally new way of thinking; it just uses a lot of stuff that has been around in other industries,” he said. “If you get heartburn with ‘DevOps,’ then don’t use the word. Call it anything you like. The point is being able to remove the constraint of IT out so the businesses can move as fast as possible.”

Automating as much as possible: Automate everything that can be automated, because anything you can’t automate is manual, and manual means it is going to take a longer time, according to Dynatrace’s Grabner.

“Manual means that it is also prone to error because if somebody needs to perform something manually, humans make mistakes,” he said. “Also, if the person who is performing the manual tasks is sick and somebody else needs to do it, then that person isn’t going to have the same experience and make mistakes. Therefore, tools need to have a very big focus on automation.”

What does DevOps mean for your company
DevOps can be confusing for companies because there is still no set definition on what the methodology actually means. SD Times caught up with some experts to describe what DevOps means to their company and how they try to explain it to customers.

CA’s Ravichandran: Our definition of DevOps is being able to enable customers by providing a tool set that helps them automate the entire software delivery life cycle while enabling customers to have a continuous feedback mechanism, which goes bi-directionally between the Dev and the Ops side. If you think about DevOps, people have multiple different definitions, and DevOps in my mind is more of a phenomenon; it is more of a culture transformation, which includes people, processes and technology.

CloudBees’ Labourey: Everyone is going to tell you it is hard to define, it is not a specific or solid. It is almost more of a philosophy then a set of tools. Tools are important, but really DevOps is going to be anything that helps accelerate the delivery flow from development to testing, staging and production. Anything that can help make that happen is going to be covered by DevOps, and obviously it is going to have some very specific aspects to it in terms of tooling, in terms of methodologies, in terms of collaboration among teams of different DNA, and all of that is covered under the DevOps umbrella.