Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Advice for Breaking Down Dev and Ops Silos In The Real World

DZone's Guide to

Advice for Breaking Down Dev and Ops Silos In The Real World

· DevOps Zone
Free Resource

Best practices for getting to continuous deployment faster and with dramatic results in reduced outage minutes, development costs, and QA testing cycles. Brought to you by Rainforest QA.

Today Paul Mueller from HP shared some insights from a customer and friend of his who leads the Systems Management at a major health insurance provider.  In his cleverly titled post, "IT is like salad dressing, sometimes you need to shake it up," he gave three points of advice that led to a 90 percent reduction in production incidents:

  • "Operations has a voice in requirements - it’s important that the supportability of the application be part of its non-functional requirements. The Operations teams are best positioned to form those requirements."
  • "App development and QA should be part of operations escalations - this helps to build a shared understanding of real-world use cases for fault isolation and diagnostics."


  • "Establish common tooling between the two - in his case he focused on common synthetic transaction and load generators, diagnostics and configuration management tools. This not only prevented his development and operations teams doubling up on tools that essentially did the same thing, but facilitated a common bond between Dev and Ops and that helped bridge what was previously a gap."

As with most problems, Mueller says that a DevOps culture cannot be achieved with just tools. 

Source: http://www.enterprisecioforum.com/en/blogs/paulm/it-salad-dressing-sometimes-you-need-shake-it

Discover how to optimize your DevOps workflows with our on-demand QA solution, brought to you in partnership with Rainforest QA.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}