I was fortunate enough to have been close to this process a few times in my working career (I am an engineer, not a computer expert) and saw this play out a half dozen times, once up close and personal.
Three years before I retired, I suggested to my supervisor a way to avoid random versions of what should be a single set of weekly updates of critical constantly changing information related to a large site, where construction was ongoing 365 days a year, and affected a hundred or so other engineers on site and countless others off site. This was my sole task, gathering changes and revisions and preparing the updates.
So eventually a program was ordered from the IT department to address that single problem.
Before the bureaucracy was done there were so many "enhancements" added to the original task that when I retired, the program was still not working to satisfy anyone, and as far as I know, to this day, 9 years later, it is still not working.
Most Informative-Why Large IT Projects Fail
I can't recommend too strongly the value of reading this series of reports and commentary, if all of the links and sublinks are followed. An education in itself.