Software runaways
Author(s)
Bibliographic Information
Software runaways
Prentice Hall PTR, c1998
Available at / 2 libraries
-
No Libraries matched.
- Remove all filters.
Note
Includes index
Description and Table of Contents
Description
A case study book dealing with software failed projects, e.g. The Denver Airport problem. It categorizes these projects into the following areas: 1)Project objectives were not fully specified. 2)Projects were poorly planned. 3)Enabling project technology was not fully understood. 4)Absence of management methodology. 5)Insufficient expertise. 6)Lack of understanding of the risks involved. These cases will show how failure might have been avoided, how they might have been completed, on time and within budget. This book should be seen as a companion volume to Yourdon's DEATH MARCH book and Jones ASSESSMENT & CONTROL OF SOFTWARE PROJECTS, both of which will be extensively referenced in the book.
Table of Contents
1. Introduction.
What Is a Software Runaway? The Cries of Software Crisis. "Crunch Mode" and the "Death March" Project. Some Relevant Research Findings.
2. Software Runaway War Stories.
Project Objectives Not Fully Specified. Bad Planning and Estimating. Technology New to the Organization. Inadequate/No Project Management Methodology. Insufficient Senior Staff on the Team. Poor Performance by Suppliers of Hardware/Software. Other' Performance (Efficiency) Problems.
3. Software Runaway Remedies.
Risk Management. Issue Management. Remedies Attempted During Runaways. Remedies Envisioned for the Future.
4. Conclusions.
Index.
by "Nielsen BookData"
