views:

109

answers:

7

I'm trying to find some publicly available "lessons learned" after a failed software development project. The bigger the project, the better. I'm interested mostly in opinions expressed by its participants: managers, programmers, designers, etc.

Information from analysts like F. Brooks, S. McConnell, and others is not as important, but thanks for your comments.

A: 

Microsoft Bob - It was a good idea. But no one wanted cartoons to represent the office environment.

Christian Sciberras
@Christian I'm interested in publicly disclosed information from project participants
Vincenzo
Why exactly did I get a -2? I'm not ranting against Microsoft, if that what it seems to be. Please look up Microsoft Bob on Wikipedia first... Oh, and Vincenzo, unfortunately, that project was way past my time.
Christian Sciberras
A: 

programming and/or project management books tend to have the best compilations of the material you are looking for.

My favorite is Steve McConnell's book "Software Project Survival Guide" (Amazon link) which has numerous examples of large failures and lessons learned.

Addys
A: 

Software Engineering Institude was my source for information on probablilty of success vs size of project. Not surprisingly the less likely it is to succeed.

You may also want to look at the book, "The Mythical Man Month" by Fred Brooks.

BillThor
A: 

That's the best I've found so far:

Vincenzo
A: 

Take a look at this and Ed Yourdon's book: http://en.wikipedia.org/wiki/Death_march_%28software_development%29

Also his web site - he may have projects like this listed there:http://www.yourdonreport.com/

Joe

related questions