Let us take a typical enterprise: they started with IT department with pay roll in the 70s.
The brought in PC’s for client/server programs to create small apps for their customer relationship management.
Eventually, I relented and had our professional IT manager, who setup a process for procurement of phones. We are sent conflicting signals throughout schooling.
Even if the procurement time increased to a week, it was always guaranteed. On one hand, we are supposed to follow rules: school rules, arithmetic rules, L’Hospital’s Rule, whatever.
The problem is that these technologies are moving really fast.
If you standardize and build all the ecosystem — the assets, the processes, the training, the hiring — then, what happens if the technology becomes outdated?
They tried to write lot of apps, but eventually wisely moved to SAP.
In the 2000’s, they rewrote parts of SAP in Java on the web. All in all, their focus was to take the requirements and use the right COTS application.When I co-founded Savera, a telecom interconnect billing company, I had the chance to put my theory to action. After a few employees, I let others handle the ordering.Soon, we ended up with many different models of phones.Within Java Script, on average, there is one new framework every quarter.Even if you choose the right one, it will be outdated soon. You choose, you still end up with a dozen, but all the ones are outside your governance.It created the entire software development outsourcing, where offshore development companies came with standard tools, processes, and methodologies to deliver software with expected quality, cheap price, and predictable timelines. This problem shows up in many ways: [Consider the fireplace in a house. Ironically, it ended up with a different utility value, as a place for people to gather and an informal place to sit.