My last DBA position was in the Operations part of a DevOps shop.
The company's implementation of DevOps was a colossal failure in several respects:
1. The ROI for the huge expansion of communication between departments was low,
2. The amount of energy expended on communicating was high (and mostly wasted), and
3. In general, the DevOps environment produced much frustration and hand wringing because real progress occurred at a snail's pace. We could talk much faster and farther then we could execute.
The shop claimed it was Agile, but only in name. Development was Agile, but nothing else. (But which version of Agile? That's a discussion in its own right.)
It had a CMS (Change Management System) in place that moved very slowly while the level of communication far outpaced it.
The email flood was unbelievable. With every new employee added, the explosion of emails increased exponentially because increased communication is a core tenant of the DevOps "model", and everyone communicated like they "were supposed to".
In summary, talking, writing, and hand wringing were substitutes and energy consumers for real progress. Communication was out of balance with other processes to meet objectives.
There are optimal levels of communication to accomplish real work. Communication for its own sake is not progress and ultimately, counter productive.
There may be other shops that have implemented DevOps successfully, but my last experience with it has left me very wary of it.
Like Agile, DevOps sounds good, but since it is poorly defined (like Agile), people make it up as they go (like Agile).
IMHO, both Agile and DevOps are good ways to avoid real planning which is hard work. Everyone is busy, busy, happy, happy, but doing what? Just busy.
In 30+ years in IT, I've seen many ideas come and go. Like a lot of things in I.T., I predict DevOps is a fad that will come and go, mostly go.