3 ms·
> NYC government could have created a small crack-team of internal IT people who could build the system for less than a 5th of the current cost. So you're arg
by tjic 17y ago
> NYC government could have created a small crack-team of internal IT people who could build the system for less than a 5th of the current cost.
So you're arguing that the NYC government is incompetent at running a project done by contractors, but it would be better at both FORMING and RUNNING its own team of contractors?
Sounds like nonsense to me.
- dkarl 17y agoInternal IT people would be able to "cheat" by talking to actual users and stakeholders, doing stealth requirements gathering, examining the current system and how it's used, doing rogue user testing, etc. Basically doing all the things that everyone agrees are required for success on this kind of project, but which in the real world end up being dropped or neutered by bureaucracy. E.g., your "expert user" is the manager of the users and doesn't know anything about how they do their jobs, and you aren't allowed to talk to the actual users. An internal person would be more likely to have the personal contacts and trust required to work around crap like that.
- Devilboy 17y agoYea the internal IT people know what the ACTUAL requirements are and how the current system REALLY works. The bureaucrats writing the requirements and other documents usually don't understand the nuances of how the systems work in real life and will fail to capture the details and idiosyncrasies accurately.
- siculars 17y agoAn internal crack IT team is the only way to make something meaningful happen. Consultants should only be brought in when there is no in house capacity/capability. The best way to make applications happen is to have the programmer intimately know the requirements by being on site and intermixed with the end users.