IT is not responsive (The Unicorn Project)
Axiomatically, IT is a solution to a "real world" problem. That's why application software is named as such.
Why is IT's endeavour to provide a solution seen as non-responsive? Why are projects "always" doomed to overextend on time and budget? Why can't there be a real Unicorn?
Unicorn Inhibitor #1. Manglement. Techies understand that an IT project's time is largely scoping, analysis and design, followed by the development of the solution (excluding implementation). Something like 70% of the first and 30% of the second in a project is, arguably, reasonable. Manglement, especially in $Corp, denies that premise - like politicians deny maths regarding backdooring encryption. They think a 5/95 split is way over-doing it on the 5!
Unicorn Inhibitor #2. Change Control! Yep, Change Control is there for a good reason. It's also a killer if the PHBs don't allow IT to "do it right" (as in #1). Every design change, because techies weren't allowed the time to design correctly, feeds an ever increasing CC snowball that even their own hell cannot melt. The larger the $Corp, the larger impact per design change. CC is the project PITA that auditing is to operations!
Only when techies are permitted to act appropriately is there a chance of seeing a Unicorn. A very, very, very slim chance!
(Aaaah! Forgive me for preaching to the converted!)