Software runaways
著者
書誌事項
Software runaways
Prentice Hall PTR, c1998
大学図書館所蔵 全2件
  青森
  岩手
  宮城
  秋田
  山形
  福島
  茨城
  栃木
  群馬
  埼玉
  千葉
  東京
  神奈川
  新潟
  富山
  石川
  福井
  山梨
  長野
  岐阜
  静岡
  愛知
  三重
  滋賀
  京都
  大阪
  兵庫
  奈良
  和歌山
  鳥取
  島根
  岡山
  広島
  山口
  徳島
  香川
  愛媛
  高知
  福岡
  佐賀
  長崎
  熊本
  大分
  宮崎
  鹿児島
  沖縄
  韓国
  中国
  タイ
  イギリス
  ドイツ
  スイス
  フランス
  ベルギー
  オランダ
  スウェーデン
  ノルウェー
  アメリカ
注記
Includes index
内容説明・目次
内容説明
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.
目次
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.
「Nielsen BookData」 より