In-Depth

How IT Can Facilitate a DevOps Culture

A successful move to DevOps requires several key changes, according to Live! 360 conference keynoters Don Jones and Brian Randell.

DevOps represents a fundamental shift in the way many organizations are developing and delivering applications to their user and customer base.

While DevOps isn't new, more organizations are building it into the way they deliver IT and experts expect that trend to continue next year.

Yet many IT professionals are still grappling with how to shift their distinct IT operations and development organizations into one that embraces DevOps, where the two collaborate and build more automation into their systems to make it easier to deploy apps more dynamically.

A successful move to adopting a streamlined and efficient DevOps depends on several factors, according to Don Jones, curriculum director for IT Pro content for Pluralsight and Brian Randell, a partner with MCW Technologies, specializing in software development.

The two described from both the IT pro and developer points of view on how to move to a DevOps culture in the keynote address at Live! 360, which took place in Orlando, Fla. The conference is produced by 1105 Media, which is also the parent company of this site.

Jones and Randell outlined the following considerations:

  • Collaboration: All team members should have the same goal to successfully deliver to the customer.
  • Integration: DevOps should be a fluid exchange of ideas.
  • Automation: By automating repetitive tasks, it becomes easier to iterate quickly, and ensure a smooth delivery path to eliminate bottlenecks.
  • Cooperation: Successful DevOps also requires a measure of cooperation

The DevOps movement essentially stems from the agile development movement. "Agile is working," Randell said. "Three quarters of [development] teams are doing some kind of agile. It comes down to the focus on delivering to the users. It's not a one size fits all situation."

Development teams are now the first line of defense for effective and smooth-running apps, Randell added. The move to DevOps has changed the app testing process. Testing now becomes embedded into the development teams as part of the process. By iterating frequently and delivering rapidly, apps are tested and debugged on a more continual basis.

"It really does turn DevOps into a machine," Jones said, noting even Microsoft no longer has a QA department which has led to the delivery of new code to fix bugs faster. "This ensures a smooth flight path from the developer to the customer," Jones said.

DevOps becomes a continuous cycle of integration, testing, deployment and feedback. Automation plays a big part of this, according to Jones. "The real purpose of automation is consistency, but there are other benefits as well," he said. "The idea of reducing manual effort is a side effect."

While the automation, continuous iteration and delivery means code will be delivered with bugs, it can always be fixed, he added. "You are going to ship bugs," he said. "You just have to learn to fail with style."

Randell agreed. "A key success point is to stop assigning blame," he said. "You have to create a culture of empathy and continuous code delivery." It's a process of constant improvement that ensures customers get the features they want and need.

A full recording of the presentation is now available for download. Next year's Live! 360 conference will be held Dec. 5-9, 2016.

About the Author

Lafe Low is the editorial liaison for ECG Events.

Featured

comments powered by Disqus

Office 365 Watch

Sign up for our newsletter.

I agree to this site's Privacy Policy.