The adoption of DevOps, where I work, seems to experience its ups, then significant downs. And how DevOps is perceived is also mysterious.
For example, on Monday I was involved in a meeting with some people in upper management, to discuss a division of people who are requesting a Git repo for themselves to share their code. These people are not developers. Instead, they're data analysts, so they are sophisticated users. Basically, the meeting was how do we reign them in. I understand the need to provide governance. And some of this group had caused a server to fill up. I asked what happened later and learned that the disk space on the server got low. The reports that they run weren't cleaning up temporary files correctly, so it filled up the disk. The worse thing is this group of people were given administrative privileges on the server, then they installed some SAS add-ons. I don't understand what happened next, it wasn't explained to me, but some in the meeting were very concerned about this. No one in IT knows the software involved (SAS, R and I think Python), so there's a concern how to we support them. How do we review their code, etc. Since the server involved was on-prem it became a big issue, especially once the server's disk space filled up and the users demanded help from IT. This lead to a discussion of where to put Git. We used an old version TFS, so we use TFVC, but I did point out that TFS can also support Git. The discussion went to do we have them go to Azure DevOps or GitHub? Then the most senior person in the meeting expressed concern about the cost.
It was here that alarms went off for me. Our TFS server is so old that it is no longer supported. I'd like for us to move to Azure DevOps and we have the money to move IT there. But I foresee other users, like this group, requiring moving their "shadow IT" to a git server somewhere. If the only consideration is, how much is this going to cost, then we're likely to try to stop the users. I foresee those sophisticated users will find a way of getting done what they need to get done, without IT's help. After all, they have a job to do too. The horse has left the barn, trying to stop the horse after the fact isn't going to work.
As far as how DevOps is perceived at where I work, it's because people see only one person doing anything with CI/CD, rather than something all developers could do, to an extent. This may be because our TFS is so old that it doesn't support YAML. Right now, our CI is handled using PowerShell scripts, all of which were written by a PowerShell guru, who left about 2 years ago. I have some experience at YAML development, and I can tell you I prefer writing YAML over authoring PowerShell. Anyway, when I look across the organizations who are using CI/CD I see all developers involved, to some degree, in helping to author CI/CD pipelines. Where I work the perception is it is only done by one person for the whole organization. In this case that happens to be me. It surprises me the huge disconnect between what I see most companies and agencies doing verses what I see where I work. They're nothing alike.