DevOps: May Help, May Not: Page 2 of 2

As the percentage of defects that reach production increases, the combined DevOps respondents and those with none are closer, but those with some DevOps teams are doing better. The biggest disparity is those that responded they are not sure how many defects made it into production. The responses are similar when respondents were asked how often software updates are made and the time it takes to resolve high severity issues.

It's not a slam-dunk that DevOps has a measurable impact on reducing or responding to software defects, but 58 percent of respondents say that team communications was one of the three biggest benefits to the new role. Smoother change management, 57 percent, and faster mean time to resolution, 49.8 percent, were No. 2 and No. 3. There is no doubt that improved communications among teams has an organizational benefit that can't always be measured.

Jonathan Lindo, co-founder, VP products and technologies, says "one of the goals of DevOps is getting your developers to think more about the business requirements and how the application will be run in the field, and less about building cool stuff. For operations staff, it's about giving them more information about how the applications will be running in the data center and cloud. Then you can facilitate communications between the two groups, removing the hand-off where one group tosses an application or problem--along with the responsibility for it--over the fence. The DevOps team takes and keeps ownership and responsibility."