Untangling (And Understanding) DevOps - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
DevOps
Commentary
2/10/2017
07:00 AM
John Edwards
John Edwards
Commentary
Connect Directly
Twitter
RSS
50%
50%

Untangling (And Understanding) DevOps

Everybody's talking about DevOps, but how many really understand how to build or deploy an effective strategy?

When Michael Strange, a vice president in the Los Angeles office of technology consulting firm Pariveda Solutions, looks at DevOps he sees a set of practices with significant power and potential buried under a mountain of confusion and misunderstanding.

"DevOps is a series of processes and tools that comes with this high-level moniker that our industry tends to love," says Strange, who will lead the session DevOps: A Practical Framework for Technology, Process and Organizational Change, at Interop ITX on May 18. "We love titles like 'DevOps' and 'Big Data' that are simply massive and overwhelming when you look at the topic as a whole."

Strange believes that DevOps is best viewed as the natural extension of a long series of activities and principles, such as Agile, that have been designed to inspire productivity, efficiency, teamwork and innovation. "One of the fundamental premises of the integration of developers and operational awareness is that developers and their companies should, and could, benefit from greater involvement throughout the entire development chain," he says.

Michal Strange, Pariveda
Michal Strange, Pariveda

Getting started

Although DevOps' intrinsic value is rarely questioned, many enterprises still don't quite understand how to build or deploy an effective DevOps strategy. "When you talk about DevOps, there are so many different components of what that could possibly be, and so many different goals and drivers of what could cause a company to want to explore these topics, that it is very possible to have confusion from the very beginning," Strange says.

As Strange sees it, the biggest adoption roadblock is a failure to zero-in on a goal or collection of goals. "This is not surprising," he notes. "That’s true in the cloud and true in lots of things."

DevOps goals can be as simple and fundamental as improving quality or cutting costs. Yet some enterprises also seek more elusive targets, such as ownership, accountability, or role definition. "It could be the elimination of key-person dependence or, in the case of a technology company like Google, a desire to foster innovation," Strange says. "There's a whole series of possible goals, and the way to ready your organization for DevOps completely changes based on those goals."

A team journey

After the DevOps goals have been established, the enterprise needs to engage in a period of introspection. "Understanding exactly where you are organizationally in terms of maturity, and what your target maturity is, is super-important to letting out any kind of a realistic plan," Strange says.

Constantly encouraging honest, straightforward discussions among all stakeholders is essential for long-term DevOps success. "You need to leave space for people to have debates," Strange says.  "Pick a couple of topics that very few people disagree with and start there." Strange also recommends implementing Agile, committing to continuous deployment and creating a cloud-based development environment. "Move in this direction, and then work with your own people to decide what matches your culture," he suggests.

A big mistake many enterprises make, Strange says, is approaching DevOps as a project. "DevOps is not a project that you start and end," he says. "It’s a decision to implement a series of processes, roles, tools and methods that are going to be continuously refined."

Strange compares DevOps to Kaizen, the Japanese business philosophy of continuous improvement. "That's more a philosophy linked to numerous processes, but it’s a similar kind of a thing," he notes. "You have to continue to explore processes and, for the most part, explore improvements iteratively."

 

John Edwards is a veteran business technology journalist. His work has appeared in The New York Times, The Washington Post, and numerous business and technology publications, including Computerworld, CFO Magazine, IBM Data Management Magazine, RFID Journal, and Electronic ... View Full Bio
We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
News
IBM Puts Red Hat OpenShift to Work on Sports Data at US Open
Joao-Pierre S. Ruth, Senior Writer,  8/30/2019
Slideshows
IT Careers: 10 Places to Look for Great Developers
Cynthia Harvey, Freelance Journalist, InformationWeek,  9/4/2019
Commentary
Cloud 2.0: A New Era for Public Cloud
Crystal Bedell, Technology Writer,  9/1/2019
White Papers
Register for InformationWeek Newsletters
State of the Cloud
State of the Cloud
Cloud has drastically changed how IT organizations consume and deploy services in the digital age. This research report will delve into public, private and hybrid cloud adoption trends, with a special focus on infrastructure as a service and its role in the enterprise. Find out the challenges organizations are experiencing, and the technologies and strategies they are using to manage and mitigate those challenges today.
Video
Current Issue
Data Science and AI in the Fast Lane
This IT Trend Report will help you gain insight into how quickly and dramatically data science is influencing how enterprises are managed and where they will derive business success. Read the report today!
Slideshows
Flash Poll