Most Organizations Are Not Fully Embracing DevOps (betanews.com)

An anonymous reader shares a report: Although many businesses have begun moving to DevOps-style processes, eight out of 10 respondents to a new survey say they still have separate teams for managing infrastructure/operations and development. The study by managed cloud specialist 2nd Watch of more than 1,000 IT professionals indicates that a majority of companies have yet to fully commit to the DevOps process. 78 percent of respondents say that separate teams are still managing infrastructure/operations and application development. Some organizations surveyed are using infrastructure-as-code tools, automation or even CI/CD pipelines, but those techniques alone do not define DevOps.

Comments

Marketing and operations not embracing MarkOps

[Anonymous Coward]

Equivalent of saying marketing and business operations need to embrace each other as one. Yes there should be synergy and commonality, however they are different fundamental areas of expertise. Dev Ops should favor cooperation and collaboration not one person to do it all.

Re:Marketing and operations not embracing MarkOps

[Idimmu Xul]

im gonna throw it out there and say devops was just a philosophy of applying development paradigms, e.g. source control to infrastructure, producing the code as infrastructure movement and paving the way for easier continuous integration with the ability to auto-build complete systems from scratch on demand

devops was never about merging the systems and development teams, ever

And this is a "problem" because ...

[xmas2003]

... a developer should be modifying production code?

Re:And this is a "problem" because ...

[supremebob]

Well, not the developer per se, but the DevOps guy should have a process to promote it automagically from development to qa to production.

If they do their job right, it shouldn't take more effort than pressing the "promote" button in their build and deploy tool of choice. For course, it never actually WORKS that way, but that's how the vendors tell me it should work.

Re:And this is a "problem" because ...

[Xest]

I'm not really sure what the summary/article is on about. It says:

"Although many businesses have begun moving to DevOps-style processes, eight out of 10 respondents to a new survey say they still have separate teams for managing infrastructure/operations and development."

But DevOps processes doesn't preclude dev and ops being separate teams, it just means that they should work together and use the countless bits of DevOps tooling out there to help support things like CI. It just about smoothing the path from dev to ops and automating it as much as possible.

If the suggestion is that to to DevOps "properly" which seems to be the implication of the summary then it does indeed suggest that what they're saying is that there should be crossover between developers and ops.

I work for a well regulated financial services organisation and that frankly just wouldn't fly. It's all fun and games if you're running shit that doesn't matter but for us, good luck explaining to the FCA that the reason you leaked a whole bunch of sensitive personal financial data was because Bob the dev configured the hardware firewall himself via Octopus incorrectly, or Jim the ops guy just did a small update that involved temporarily storing an admin password in a plaintext string internally in some application which got subsequently output in a memory dump on error on the public internet.

There are ample good reasons why DevOps does not and should not inherently mean merging the two departments, and frankly those suggesting otherwise should get the fuck out the industry in case someone accidentally employs them to work on something that matter and we end up with yet another complete fuckup of a software project.

It's sufficient to simply build bridges between and increase efficiency of the work dev and ops do together. Anything more than that is frankly nothing more than utter retardation. Let professionals do what they're professionals at - you wouldn't get the fucking cleaner to do their own payroll, so why the fuck would you get ops to do their own dev or vice versa?

Re:And this is a "problem" because ...

[jrumney]

For many companies it needs to be harder, not easier to push into production. The emphasis should not be on the "one button" to promote from development to production, it should be on the well defined process that leads to that button.

Re:I'm the architect on our DevOps team...

[Dynedain]

If you're on 4 scrum teams, then that's entirely stupid and undermines scrum. The teams shouldn't organized to be project-based, the teams should be organized to form a tight well-functioning, and most importantly, PRODUCTIVE group.

One of the biggest values of scrum and sprints is to reduce the amount of work in-flight at once so that each thing can be completed in a shorter timeline. If everyone is on everything, then you're wasting everyone's time on context switching.