Posted by cadsmith on December 13, 2007
Catastrophe Disentanglement: Getting Software Projects Back on Track, Bennatan, 2006, 288pp, has courseware about rescuing software projects from failure using a ten-step process that takes two weeks to get back on track. Each chapter also has sections for what can go wrong (and what to do about it) and exercises. Alarms can be set to warn of project derailment so it can be halted, corrected and resumed. These use factors such as slipping schedule, budget, and software quality. An evaluation team is selcted, goals and software team are refined, the plan is revised based on risk analysis, an early-warning system is instituted, and the eventual results are reviewed. A successful case study is given for a software project for a wireless telephony control and maintenance center. Amazon.com has a table of contents. Author site. Discusses metrics used in development data collection including defects, testing, integration and product performance. Problems are classified as minor, serious or critical. The problem list alarm uses criteria such as growth of problem list, rate of additions, length of serious problem list, objective estimates of time needed to correct critical and serious problems, and whether the list itself is maintained correctly. Example of early-warning system (EWS) refers to software life cycle management (SLIM). A common problem cited in post-project reviews was the lack of an independent test organization.