How to Build a Better DevOps Model

By Samuel Greengard Print this article Print
Build DevOps Model

Establishing a DevOps strategy and putting it into motion can prove extremely challenging. Success depends on factors such as technology, processes and culture.

Cracking the DevOps Code

The ability to push DevOps into the mainstream of the organization through a best-practice approach is key to success, Suleman says. He suggests that organizations establish a center of excellence; focus on pilot tests and projects that grab the attention of leadership; document successes and failures; learn from them; and then share that knowledge across the enterprise. "Once you have internal experts and consultants you can help other teams get on board and push the concept deeper into the organization," he explains.

Of course, there's a tactical side to the equation as well. This includes deploying communication and collaboration tools that allow key stakeholders to communicate and collaborate in real time, using automated testing tools to check for code quality and application security, establishing cloud and API libraries, and embracing a more integrated approach to configuration management.

In addition, organizations require greater application monitoring and automated dashboards to track the status of teams and to provide live feedback about project performance and governance. This may include continuous and predictive monitoring.

Finally, it's vitally important to dismantle the IT silos. DevOps means moving beyond traditional domains and departments that build, test and deploy code in discreet steps and within discreet groups. Code production and other tasks must take place continuously and become visible to all key stakeholders.

The good news is that today's technology and growing knowledge about DevOps makes all of this possible. "There's no need for everyone to sit in the same room," Suleman points out. "With tools and processes that enable communication and define the delivery process, it's possible to radically redefine the speed and manner in which development takes place.

"You no longer wind up with developers not knowing what the change was supposed to be and operations making the wrong change. You no longer wind up with teams going around in circles and eventually landing back at square one."

When organizations succeed with DevOps, processes and practices that previously consumed months may take weeks or days. Errors and mishaps that previously devoured staff time fade away. Agility, flexibility and performance all spike upward, and innovation flourishes.

"The most important thing to understand is that DevOps is not a six-month initiative," says Capgemini's Newberry. "It's not a close-ended project. It's a continuous improvement program that ties together your business and IT value chains.

"Even as technology evolves and customer solutions change, DevOps is able to help an organization deliver faster and better. It provides the framework to grow and change."

This article was originally published on 2017-09-04
Samuel Greengard writes about business and technology for Baseline, CIO Insight and other publications. His most recent book is The Internet of Things (MIT Press, 2015).
eWeek eWeek

Have the latest technology news and resources emailed to you everyday.