论文信息 - 12.3 Project Failure Prevention: 10 Principles for Project Control

12.3 Project Failure Prevention: 10 Principles for Project Control

It is now well-known and well-documented that far too many projects fail totally or partially, both in engineering generally (Morris 1998) and software engineering (Neill and Laplante 2003). I think everybody has some opinions about this. I do too, and in this paper I offer some of my opinions, and I hope to lend some originality to the discussion. As an international consultant for decades, involved in a wide range of projects, and involved in saving many ‘almost failed’ projects, my basic premises in this paper are as follows: We specify our requirements unclearly; We do not focus enough on ensuring that the system design meets the requirements.

Tom Gilb

[1] Craig Larman,et al. Agile and Iterative Development: A Manager's Guide , 2003 .

[2] Victor R. Basili,et al. Iterative and incremental developments. a brief history , 2003, Computer.

[3] Tom Gilb. 1.6.1 Software Project Management: Adding Stakeholder Metrics to Agile Projects , 2004 .

[4] A. Terry Bahill,et al. Requirements development, verification, and validation exhibited in famous failures , 2005, Syst. Eng..

[5] Colin J. Neill,et al. Requirements Engineering: The State of the Practice , 2003, IEEE Softw..

[6] Tom Gilb,et al. Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, And Software Engineering Using Planguage , 2005 .