> Have you ever noticed that companies locate their research divisions away from the day-to-day operations divisions? It is to keep the timeframes separate.
No, it's turf building and budget protection. By segregating the developers from devops, devops can _hide_ their resources and keep them sequestered from developer requests. And putting the systems into a "requests go to managers, and only then to devops" makes the managers vital to allocating resources. It can protect their team from excess pecuniary demands, but far too often it's used to make the manager more important to the process than they should be, and grants them personal power over other groups' projects.
I've been documenting a tragic example of this for the past few weeks. I'm afraid the manager is in for a _big_ surprise when they find out that writing run books is their new highest priority, and their personal approval of run books is no longer expected.