On GameSpot: Courtney Love to sue over Guitar Hero 5
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 1 of 3:
Next »
Don't Preclude Agile, Consider Legacy
I agree with most of these comments, but I must note that they primarily apply to waterfall projects which can be specified in advance. An agile project design may not fit the legislation and may be precluded or denigrated when that would be a superior approach.

A second issue that I have with government RFP's in general is that they try with generally poor results to specify what they want, which they frankly almost cannot do. Systems are too complex, and that complexity provides too much opportunity for cynical vendors to exploit.

Since there are almost no greenfield IT application development projects any more - virtually all application projects are replacing an existing application - I have a very specific recommendation: specify how the project results should be different from the current system. The existing system is its own specification for its functionality.
Posted by: donestes@...   Posted on: 06/11/09 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

Don't Preclude Agile, Consider Legacy  donestes@... | 06/11/09
RE: Senate IT oversight bill: Detailed analysis  Tom Raftery | 06/12/09
Thank you  mkrigsman@... ZDNet Moderator | 06/12/09

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

advertisement
advertisement

Enterprise Applications

  • Check out some of the easiest and most powerful ways to boost productivity while saving money on your application infrastructure. See ZDNet's comprehensive Enterprise Application resource center, now!
  • New Online Dashboard
  • Read about top issues IT decision-makers face every day, plus get cost effective solutions to real life IT problems. Oracle Topline