“You need to understand what is the primary goal of the business and ensure those goals are measureable and support the business,” he said.
Being able to understand what you are working toward will help organizations understand if they are on the path of success or failure, Levy continued.
In addition, business goals are really what will drive DevOps adoption, because in the end the business is all about IT, according to CloudBees’ Labourey, “We need to stop thinking about IT as some kind of remote team within the organization responsible for implementing whatever the business desires.”
“What we are seeing today is that IT is business, business is IT. A lot of the innovation and differentiation that exists within products today comes from software, which comes from IT.”
Lastly, before moving toward DevOps, organizations need to grasp the notion that it is going to take time. Even if the IT department is on board and wants to make the move, it isn’t going to happen in a snap, nor should it happen all at once, according to Labourey.
“It is really something that needs to happen through small proof-of-concept initially because every company is going to be different,” he said. “You have to build your own practice, your own religion, and that is going to take time.”
Proven practices for a DevOps implementation
Keeping it simple: Don’t try to transform the entire organization, according to Serena’s Levy. Instead, start with a pilot program. “If the DevOps principles are not natural to your team—such as creating a culture, automating and measuring all things—then you need a place to practice,” he said. “Pilot programs allow you to start small and it is less expensive, but it represents real work.”
According to CA’s Ravichandran, organizations have actually built “centers of excellence” to foster one common business imperative, and to use that to fine-tune how they are going to make this culture transformation at a larger level in the company.
Understanding that failure is a part of the process: Organizations should not go into DevOps thinking that they will see results right away, because that is not going to happen, according to CloudBees’ Labourey. “You don’t need to build a castle to define whether an idea is a good one or a bad one,” he said. “You are going to do maybe daily, weekly reviews to see how things are going and whether things need to be adapted.”