SW Development Failures Book Title Request

As per our phone call of today, here is the book I mentioned on the conference call.

http://www.amazon.com/exec/obidos/tg/detail/-/0262050722/qid=1079978986/sr=1-1/ref=sr_1_1/102-1124386-7954550?v=glance&s=books#product-details

This is not the greatest book in terms of writing. See reviews. I found the abandonment-factor categories and the complex technical and social issues around the code of silence about failed projects most helpful. Page 66 has the abandonment categorization broken down into

Socioorganizational, Sociotechnical and Economic.

Essentially:

Unrealistic Project Goals and Objectives

Changing Requirements

Lack of Executive Support and Commitment

Insufficient User Commitment and Involvement

Inappropriate project-team composition

Project management and control problems

Inadequate Technical Know-How

Problematic Technology Base/Infrastructure

Rapidly Changing Requirements

Cost Overruns & Schedule Delays

The book would have been dynamite if he had taken the 55 Facts and Fallacies of Software Engineering by Bob Glass and used the above categorization.

http://www.amazon.com/exec/obidos/tg/detail/-/0321117425/qid=1079986459/sr=1-1/ref=sr_1_1/102-1124386-7954550?v=glance&s=books

If somebody has the time or inclination, they could do the mapping and include the BCM contribution to the solution. I am over committed to BCM/EPR right now.

<Dan/>

bcm message