《Catastrophe Disentanglement》是Addison-Wesley出版的圖書，作者是Bennatan, E.M.
基本介紹
- ISBN：9780321336620
- 作者：Bennatan, E.M.
- 出版社：Addison-Wesley
- 出版時間：2006年4月
- 頁數：288
- 定價：$ 45.19
- 裝幀：Pap
內容簡介
"There are many books available on software risks and software failures. There are very few books that provide step-by-step information on getting troubled software projects back on track. This book provides detailed guidelines for software project recovery. Some of the steps the author recommends may be unpleasant, but all are important." -Capers Jones, chief scientist emerit...(展開全部) "There are many books available on software risks and software failures. There are very few books that provide step-by-step information on getting troubled software projects back on track. This book provides detailed guidelines for software project recovery. Some of the steps the author recommends may be unpleasant, but all are important." -Capers Jones, chief scientist emeritus at Software Productivity Research LLC "This is a well-conceived, well-written, interesting book about an important topic. The author is right in saying that no one else has covered this particular facet of project failure." -Robert L. Glass, publisher of the Software Practitioner A 10-STEP PROCESS TO IDENTIFY SEVERELY TROUBLED PROJECTS AND AVOID COSTLY FAILURE It's a software development nightmare: a project that's rapidly spiraling out of control...or already a disaster. Conventional project management techniques won't save these projects: there are no standard rescue processes to follow. You need something radically different: Catastrophe Disentanglement. Drawing on in-depth data from hundreds of development organizations, E.M. Bennatan presents a proven, 10-step program for rescuing any project that's worth saving. You'll find specific guidance for addressing massive budget overruns, schedule slippage, poor quality-or all three at once. Using practical examples drawn from decades of hands-on experience as a software development leader and consultant, Bennatan shows how to * Evaluate where your project really stands * Align your project's developers, managers, and customers * Defi ne t
