Author |
Topic |
|
Astralis
Senior Member
USA
1218 Posts |
Posted - 14 January 2005 : 03:44:01
|
After reading about this software issue at the FBI, who would you blame for the errors, the software company, or the FBI?
FBI Computer Overhaul Hits Another Snag
I blame both, but mostly the FBI. I believe when you change the structure of a project while in the middle of it, you not only increase the due date, but you also weaken then code by building over code that was supposed to do something else.
I'm not sure if the FBI is going to ask for their money back. It doesn't look like it. But, the software firm will no longer work with them.
BTW, is $2 million enough to test a computer system?! |
|
Astralis
Senior Member
USA
1218 Posts |
Posted - 16 January 2005 : 16:32:29
|
I guess there aren't many developers on Snitz as I presumed.
Anyhow, if you develop code, what is your opinion about this situation?
The FBI is now considering to scrap the entire $170M project. |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 16 January 2005 : 18:05:20
|
It's not easy to talk about this without proper info. In most software development projects requirements change as the project proceeds. Also usually blame is divided both by contractors and clients, maybe in different percentages, but certainly by both. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
Astralis
Senior Member
USA
1218 Posts |
Posted - 16 January 2005 : 18:43:39
|
I agree. I know someone whose project is running months behind due to a variety of issues, one of which is that the client made a number of changes and additional requests in mid-stream. The client is furious at the developer and she doesn't seem to understand that additions to a project add additional time.
What would you do if you ran into a problem like this? The problems with this FBI project are very similar to my friend's project. |
Edited by - Astralis on 16 January 2005 18:44:57 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 17 January 2005 : 14:00:05
|
I never accept changes to the initial specification, if those changes have impact on the overall acrchitecture of the system to develop, or if they challenge any assumptions with had made before, without telling customers that those changes will cost money and additional development time. If theaccept it, ok. If they don't, too bad...
If they accept it, then a new schedule and additional costs need to be defined. That's how I handle it. It's also easier, because, with projects of some size, there's always a contract, accompanied by a requirements document, to which the customer needs to agree as well. The client signs it after an initial analysis, so he cannoy say he didn't know what his money was paying for! |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
Topic |
|