I work for a part of a state government agency that does highly technical, scientific work. The agency pays for licenses for every employee, from managers down to entry-level, to use a sophisticated Relational Database Management System (RDBMS) that includes developer tools, with which most of the agency's various record-keeping software apps have been developed over the past 25 years. The majority of those apps have been developed by "citizen developers," IT's term for non-IT personnel.
A few years ago, a crucial app used by my group was corrupted and became unusable. As a "computer guy" (I had some experience with Access and MySQL), I was assigned to learn the software and attempt to repair the app and make it usable "in my spare time."
Since the software had gone through several updates over the years and the version in which the original app was created would no longer run on updated computers, I decided to recreate the app in the current version, which I did. The new version worked better than the original, and everyone from the Manager on down started asking for new features. Another six months went by, and the scope of the project ballooned and I dutifully expanded the capabilities of the app as requested.
When we were about to go live (app had been tested, training materials created, etc), the IT department got wind of it and refused to let us upload the app to the server. Their reasoning?
IT Department: You're not a developer. Only IT develops apps.
We lobbied for two years while every function of the app had to continue to be done on paper, which for a highly technical workplace that collects a lot of data, was a nightmare. Eventually, after much lobbying by my manager, IT relented and decided that we could use the original version of the app (which would not run on the current version of the software) if it were repaired, but using the "new" version was still forbidden.
In a meeting where I, my manager, a high-level administrator, and a representative from IT were all present, I outlined the scope of the app, what it was used for, and why it was critical for productivity. The IT rep (an extremely arrogant person who had been blocking all progress on our project from day 1) outlined the process for getting the app up and running: My group would outline the requirements, it would go through an approval process with management, then IT would prioritize it along with their other projects, and then they would build it from scratch without any input from technical staff.
Me: "We have a fully built, operational, tested app. We don't need you to build it from scratch."
IT Rep: "You're not a developer. Only IT develops apps."
When we asked about the timeline for the development of the app, he replied, straight-faced:
IT Rep: "We might be able to start on it in about two years."
My manager was skeptical of my reports about interactions with this person, but the meeting opened his eyes. He had a private meeting with the agency director and suddenly we were cleared to upload the app to the server.
That was 14 years ago and the app has been through several upgrades and with many added features, and has probably saved taxpayers hundreds of thousands of dollars in lost productivity.