A relevant comment about IT developers in general:
I’ve seen a lot of IT projects over the years. One thing I learned is that developers rarely have any real understanding of their users or the business environment for their project. And that this is true even if they are actual users.
It’s not the same thing, but it could perhaps be compared with the fact than an experienced EVE player can never simulate being a new player again. They know too much, so things which are very difficult for the new player are obvious and simple for an experienced player with a 500K SP character.
In this case (EVE requirements management), it sounds like the Developers themselves aren’t the problem: the company is probably missing the kind of people who can manage the project(s) properly.
:
:
An IT scenario (real, but I have to be vague due to confidentiality requirements):
I’ve literally seen the developers “destroy” a very successful project (100-odd dedicated developers plus IT Operations staff) by subverting their project management and business people, convincing them to make the project “developer friendly”. They started looking too far into the future, preparing to build an IT “work of art”, and forgot to give the investors the functions they wanted and needed to generate income and profit.
Endgame: the project was moved to a different development company and a different IT Service company, badly damaging the companies that originally developed and operated the system.
The system is still very successful, the developers have nice CVs (they weren’t even very good at development, put it’s a high-status project) … but the both companies they worked for and the IT services company took very serious beatings.
The problem: the developers were good enough to keep the project alive and moving forward, but … they got their own people to approve “modernizing” the existing system instead of implementing key functions the system owners / investors wanted.
The developer-side issue is perspective: engineers want to built cool stuff with the latest technology. In IT it means they always want to re-engineer rather than deliver new functions, so they’re naturally not very interested in the user perspective. Even, as in this particular case, when they’re all users. It’s also unusual for developers to understand the investor perspective, but that’s easier to understand and accept.
In this particular case, the management-side issue was that the organization wouldn’t hire the right kind of project management and business leadership to “keep the developers honest”. This rarely works even with much smaller projects, but it’s very dangerous with more than 15-odd developers (two + teams).
Whose fault? Not the developers: they always do this if they’re allowed to. It was definitely a management mistake: they let the “lunatics take over the asylum” instead of running it properly. The couldn’t see it either, even afterwards. You could look at it as a “Dunning-Kruger” problem with a group, with normal levels of denial afterwards