«« Next » « Previous
«« Next » « Previous

Link Details

If you vote you can be DZone's BFF! Login and vote now.
Link 89840 thumbnail

By silent1mezzo
via devjargon.com
Published: Jun 24 2008 / 13:37

A backwards look at why projects fail.
  • 13
  • 0
  • 1015
  • 575

Comments

Add your comment
User 275423 avatar

lifewithryan replied ago:

1 votes Vote down Vote up Reply

All pretty obvious, but a good read nonetheless. I am far too familiar with the old "lets use the latest and greatest cuz it cool" mentality...*ugh*

User 271246 avatar

nicklewisatx replied ago:

0 votes Vote down Vote up Reply

To say that advice like, "know what you are building", "use source control", "documentation is good", "communicate" is obvious is an understatement. As far as avoiding cutting edge stuff, I think that's way to big of a generalization. It depends. Personally, I think using outdated, stale technology that is uncool would be a bigger blunder (but only generally speaking).

User 237919 avatar

silent1mezzo replied ago:

0 votes Vote down Vote up Reply

I totally agree nick,

Using outdated technology can greatly hinder a project and using new stuff can definitely help. What I think they meant was that bringing in new technology DURING a project can make it fail (or cost a lot more than expected).

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.