Software development failures :: anatomy of abandoned projects /
Failed or abandoned software development projects cost the U.S. economy alone billions of dollars a year. In Software Development Failures, Kweku Ewusi-Mensah offers an empirically grounded study that suggests why these failures happen and how they can be avoided. Case studies analyzed include the w...
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Elektronisch E-Book |
| Sprache: | English |
| Veröffentlicht: |
Cambridge, Mass. :
MIT Press,
©2003.
|
| Schlagworte: | |
| Online-Zugang: | Volltext |
| Zusammenfassung: | Failed or abandoned software development projects cost the U.S. economy alone billions of dollars a year. In Software Development Failures, Kweku Ewusi-Mensah offers an empirically grounded study that suggests why these failures happen and how they can be avoided. Case studies analyzed include the well-known Confirm travel industry reservation program, FoxMeyer's Delta, the IRS's Tax System Modernization, the Denver International Airport's Baggage Handling System, and CODIS. It has been estimated that one-third of software development projects fail or are abandoned outright because of cost overruns, delays, and reduced functionality. Some consider this an acceptable risk -- that it is simply the cost of doing business. Ewusi-Mensah argues that understanding the factors involved in development failures will help developers and businesses bring down the rate of software failure and abandoned projects. Ewusi-Mensah explores the reasons software development projects are vulnerable to failure and why issues of management and organization are at the core of any failed project. He examines these projects not from a deterministically technical perspective but as part of a complex technical and social process; he proposes a framework of factors that contribute to the decision to abandon a project and enumerates the risks and uncertainties inherent in each phase of a project's life cycle. Exploring the multiplicity of factors that make software development risky, he presents empirical data that is reinforced by analyses of the reported cases. He emphasizes the role of the user in the development process and considers the effect of organizational politics on a project. Finally, he considers what lessons can be learned from past failures and how software development practices can be improved. |
| Beschreibung: | 1 online resource (xiv, 276 pages) |
| Bibliographie: | Includes bibliographical references (pages 255-263) and index. |
| ISBN: | 9780262256087 0262256088 0585480834 9780585480831 9780262050722 0262050722 |
Internformat
MARC
| LEADER | 00000cam a2200000 a 4500 | ||
|---|---|---|---|
| 001 | ZDB-4-EBA-ocm53907132 | ||
| 003 | OCoLC | ||
| 005 | 20241004212047.0 | ||
| 006 | m o d | ||
| 007 | cr cnu---unuuu | ||
| 008 | 031215s2003 mau ob 001 0 eng d | ||
| 040 | |a N$T |b eng |e pn |c N$T |d YDXCP |d OCLCQ |d N$T |d IDEBK |d OCLCQ |d TUU |d OCLCQ |d IEEEE |d ZCU |d OCLCF |d OCLCQ |d NTG |d WPG |d B24X7 |d OCLCO |d NLGGC |d OCLCQ |d PIFBR |d LIV |d ESU |d OCLCQ |d NJR |d WY@ |d OCLCQ |d LUE |d RCC |d STF |d VTS |d MERER |d AGLDB |d OCLCQ |d INT |d OCLCQ |d COO |d MITPR |d G3B |d LEAUB |d INARC |d OCLCO |d OCLCQ |d OCLCO |d SFB | ||
| 019 | |a 63110699 |a 961599510 |a 962564561 |a 1170437372 |a 1171351735 | ||
| 020 | |a 9780262256087 |q (electronic bk.) | ||
| 020 | |a 0262256088 |q (electronic bk.) | ||
| 020 | |a 0585480834 |q (electronic bk.) | ||
| 020 | |a 9780585480831 |q (electronic bk.) | ||
| 020 | |a 9780262050722 | ||
| 020 | |a 0262050722 | ||
| 035 | |a (OCoLC)53907132 |z (OCoLC)63110699 |z (OCoLC)961599510 |z (OCoLC)962564561 |z (OCoLC)1170437372 |z (OCoLC)1171351735 | ||
| 037 | |a 6322 |b MIT Press | ||
| 037 | |a 9780262256087 |b MIT Press | ||
| 050 | 4 | |a QA76.76.D47 |b E88 2003eb | |
| 072 | 7 | |a COM |x 051390 |2 bisacsh | |
| 072 | 7 | |a COM |x 051440 |2 bisacsh | |
| 072 | 7 | |a COM |x 051230 |2 bisacsh | |
| 082 | 7 | |a 005.1 |2 22 | |
| 049 | |a MAIN | ||
| 100 | 1 | |a Ewusi-Mensah, Kweku. | |
| 245 | 1 | 0 | |a Software development failures : |b anatomy of abandoned projects / |c Kweku Ewusi-Mensah. |
| 260 | |a Cambridge, Mass. : |b MIT Press, |c ©2003. | ||
| 300 | |a 1 online resource (xiv, 276 pages) | ||
| 336 | |a text |b txt |2 rdacontent | ||
| 337 | |a computer |b c |2 rdamedia | ||
| 338 | |a online resource |b cr |2 rdacarrier | ||
| 504 | |a Includes bibliographical references (pages 255-263) and index. | ||
| 505 | 0 | |a I. Conceptual issues. Software development project failures -- Software project characteristics -- Factors critical to abandoned software projects -- II. Empirical factors. Socioorganizational factors and abandoned projects -- Technical factors and abandoned projects -- Economic factors and abandoned projects -- User perspectives on software development failures -- III. Learning from failures. Postabandonmnet review: learning from abandoned projects -- Software development: a strategic paradigm -- Project failures and aftermath. | |
| 588 | 0 | |a Print version record. | |
| 520 | |a Failed or abandoned software development projects cost the U.S. economy alone billions of dollars a year. In Software Development Failures, Kweku Ewusi-Mensah offers an empirically grounded study that suggests why these failures happen and how they can be avoided. Case studies analyzed include the well-known Confirm travel industry reservation program, FoxMeyer's Delta, the IRS's Tax System Modernization, the Denver International Airport's Baggage Handling System, and CODIS. It has been estimated that one-third of software development projects fail or are abandoned outright because of cost overruns, delays, and reduced functionality. Some consider this an acceptable risk -- that it is simply the cost of doing business. Ewusi-Mensah argues that understanding the factors involved in development failures will help developers and businesses bring down the rate of software failure and abandoned projects. Ewusi-Mensah explores the reasons software development projects are vulnerable to failure and why issues of management and organization are at the core of any failed project. He examines these projects not from a deterministically technical perspective but as part of a complex technical and social process; he proposes a framework of factors that contribute to the decision to abandon a project and enumerates the risks and uncertainties inherent in each phase of a project's life cycle. Exploring the multiplicity of factors that make software development risky, he presents empirical data that is reinforced by analyses of the reported cases. He emphasizes the role of the user in the development process and considers the effect of organizational politics on a project. Finally, he considers what lessons can be learned from past failures and how software development practices can be improved. | ||
| 650 | 0 | |a Computer software |x Development. |0 http://id.loc.gov/authorities/subjects/sh85029535 | |
| 650 | 0 | |a Software failures. |0 http://id.loc.gov/authorities/subjects/sh97005329 | |
| 650 | 0 | |a Risk management. |0 http://id.loc.gov/authorities/subjects/sh85114200 | |
| 650 | 6 | |a Bogues (Informatique) | |
| 650 | 6 | |a Gestion du risque. | |
| 650 | 7 | |a risk management. |2 aat | |
| 650 | 7 | |a COMPUTERS |x Programming |x Open Source. |2 bisacsh | |
| 650 | 7 | |a COMPUTERS |x Software Development & Engineering |x Tools. |2 bisacsh | |
| 650 | 7 | |a COMPUTERS |x Software Development & Engineering |x General. |2 bisacsh | |
| 650 | 7 | |a Computer software |x Development |2 fast | |
| 650 | 7 | |a Risk management |2 fast | |
| 650 | 7 | |a Software failures |2 fast | |
| 650 | 1 | 7 | |a Software. |2 gtt |
| 650 | 1 | 7 | |a Projectmanagement. |2 gtt |
| 650 | 1 | 7 | |a Mislukkingen. |2 gtt |
| 653 | |a COMPUTER SCIENCE/General | ||
| 653 | |a BUSINESS/Business Technology | ||
| 655 | 0 | |a Electronic books. | |
| 655 | 7 | |a Casestudies (vorm) |0 (NL-LeOCL)08814223X |2 gtt | |
| 776 | 0 | 8 | |i Print version: |a Ewusi-Mensah, Kweku. |t Software development failures. |d Cambridge, Mass. : MIT Press, ©2003 |z 0262050722 |w (DLC) 2002045504 |
| 856 | 4 | 0 | |l FWS01 |p ZDB-4-EBA |q FWS_PDA_EBA |u https://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&AN=100057 |3 Volltext |
| 938 | |a Books 24x7 |b B247 |n bks00003152 | ||
| 938 | |a EBSCOhost |b EBSC |n 100057 | ||
| 938 | |a IEEE |b IEEE |n 6267255 | ||
| 938 | |a Internet Archive |b INAR |n softwaredevelopm0000ewus | ||
| 938 | |a YBP Library Services |b YANK |n 3410820 | ||
| 938 | |a YBP Library Services |b YANK |n 2335966 | ||
| 994 | |a 92 |b GEBAY | ||
| 912 | |a ZDB-4-EBA | ||
| 049 | |a DE-863 | ||
Datensatz im Suchindex
| DE-BY-FWS_katkey | ZDB-4-EBA-ocm53907132 |
|---|---|
| _version_ | 1816881612744294400 |
| adam_text | |
| any_adam_object | |
| author | Ewusi-Mensah, Kweku |
| author_facet | Ewusi-Mensah, Kweku |
| author_role | |
| author_sort | Ewusi-Mensah, Kweku |
| author_variant | k e m kem |
| building | Verbundindex |
| bvnumber | localFWS |
| callnumber-first | Q - Science |
| callnumber-label | QA76 |
| callnumber-raw | QA76.76.D47 E88 2003eb |
| callnumber-search | QA76.76.D47 E88 2003eb |
| callnumber-sort | QA 276.76 D47 E88 42003EB |
| callnumber-subject | QA - Mathematics |
| collection | ZDB-4-EBA |
| contents | I. Conceptual issues. Software development project failures -- Software project characteristics -- Factors critical to abandoned software projects -- II. Empirical factors. Socioorganizational factors and abandoned projects -- Technical factors and abandoned projects -- Economic factors and abandoned projects -- User perspectives on software development failures -- III. Learning from failures. Postabandonmnet review: learning from abandoned projects -- Software development: a strategic paradigm -- Project failures and aftermath. |
| ctrlnum | (OCoLC)53907132 |
| dewey-full | 005.1 |
| dewey-hundreds | 000 - Computer science, information, general works |
| dewey-ones | 005 - Computer programming, programs, data, security |
| dewey-raw | 005.1 |
| dewey-search | 005.1 |
| dewey-sort | 15.1 |
| dewey-tens | 000 - Computer science, information, general works |
| discipline | Informatik |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>05666cam a2200769 a 4500</leader><controlfield tag="001">ZDB-4-EBA-ocm53907132 </controlfield><controlfield tag="003">OCoLC</controlfield><controlfield tag="005">20241004212047.0</controlfield><controlfield tag="006">m o d </controlfield><controlfield tag="007">cr cnu---unuuu</controlfield><controlfield tag="008">031215s2003 mau ob 001 0 eng d</controlfield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">N$T</subfield><subfield code="b">eng</subfield><subfield code="e">pn</subfield><subfield code="c">N$T</subfield><subfield code="d">YDXCP</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">N$T</subfield><subfield code="d">IDEBK</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">TUU</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">IEEEE</subfield><subfield code="d">ZCU</subfield><subfield code="d">OCLCF</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">NTG</subfield><subfield code="d">WPG</subfield><subfield code="d">B24X7</subfield><subfield code="d">OCLCO</subfield><subfield code="d">NLGGC</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">PIFBR</subfield><subfield code="d">LIV</subfield><subfield code="d">ESU</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">NJR</subfield><subfield code="d">WY@</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">LUE</subfield><subfield code="d">RCC</subfield><subfield code="d">STF</subfield><subfield code="d">VTS</subfield><subfield code="d">MERER</subfield><subfield code="d">AGLDB</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">INT</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">COO</subfield><subfield code="d">MITPR</subfield><subfield code="d">G3B</subfield><subfield code="d">LEAUB</subfield><subfield code="d">INARC</subfield><subfield code="d">OCLCO</subfield><subfield code="d">OCLCQ</subfield><subfield code="d">OCLCO</subfield><subfield code="d">SFB</subfield></datafield><datafield tag="019" ind1=" " ind2=" "><subfield code="a">63110699</subfield><subfield code="a">961599510</subfield><subfield code="a">962564561</subfield><subfield code="a">1170437372</subfield><subfield code="a">1171351735</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780262256087</subfield><subfield code="q">(electronic bk.)</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">0262256088</subfield><subfield code="q">(electronic bk.)</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">0585480834</subfield><subfield code="q">(electronic bk.)</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780585480831</subfield><subfield code="q">(electronic bk.)</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780262050722</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">0262050722</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)53907132</subfield><subfield code="z">(OCoLC)63110699</subfield><subfield code="z">(OCoLC)961599510</subfield><subfield code="z">(OCoLC)962564561</subfield><subfield code="z">(OCoLC)1170437372</subfield><subfield code="z">(OCoLC)1171351735</subfield></datafield><datafield tag="037" ind1=" " ind2=" "><subfield code="a">6322</subfield><subfield code="b">MIT Press</subfield></datafield><datafield tag="037" ind1=" " ind2=" "><subfield code="a">9780262256087</subfield><subfield code="b">MIT Press</subfield></datafield><datafield tag="050" ind1=" " ind2="4"><subfield code="a">QA76.76.D47</subfield><subfield code="b">E88 2003eb</subfield></datafield><datafield tag="072" ind1=" " ind2="7"><subfield code="a">COM</subfield><subfield code="x">051390</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="072" ind1=" " ind2="7"><subfield code="a">COM</subfield><subfield code="x">051440</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="072" ind1=" " ind2="7"><subfield code="a">COM</subfield><subfield code="x">051230</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="082" ind1="7" ind2=" "><subfield code="a">005.1</subfield><subfield code="2">22</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">MAIN</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Ewusi-Mensah, Kweku.</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Software development failures :</subfield><subfield code="b">anatomy of abandoned projects /</subfield><subfield code="c">Kweku Ewusi-Mensah.</subfield></datafield><datafield tag="260" ind1=" " ind2=" "><subfield code="a">Cambridge, Mass. :</subfield><subfield code="b">MIT Press,</subfield><subfield code="c">©2003.</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 online resource (xiv, 276 pages)</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">computer</subfield><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">online resource</subfield><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="504" ind1=" " ind2=" "><subfield code="a">Includes bibliographical references (pages 255-263) and index.</subfield></datafield><datafield tag="505" ind1="0" ind2=" "><subfield code="a">I. Conceptual issues. Software development project failures -- Software project characteristics -- Factors critical to abandoned software projects -- II. Empirical factors. Socioorganizational factors and abandoned projects -- Technical factors and abandoned projects -- Economic factors and abandoned projects -- User perspectives on software development failures -- III. Learning from failures. Postabandonmnet review: learning from abandoned projects -- Software development: a strategic paradigm -- Project failures and aftermath.</subfield></datafield><datafield tag="588" ind1="0" ind2=" "><subfield code="a">Print version record.</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Failed or abandoned software development projects cost the U.S. economy alone billions of dollars a year. In Software Development Failures, Kweku Ewusi-Mensah offers an empirically grounded study that suggests why these failures happen and how they can be avoided. Case studies analyzed include the well-known Confirm travel industry reservation program, FoxMeyer's Delta, the IRS's Tax System Modernization, the Denver International Airport's Baggage Handling System, and CODIS. It has been estimated that one-third of software development projects fail or are abandoned outright because of cost overruns, delays, and reduced functionality. Some consider this an acceptable risk -- that it is simply the cost of doing business. Ewusi-Mensah argues that understanding the factors involved in development failures will help developers and businesses bring down the rate of software failure and abandoned projects. Ewusi-Mensah explores the reasons software development projects are vulnerable to failure and why issues of management and organization are at the core of any failed project. He examines these projects not from a deterministically technical perspective but as part of a complex technical and social process; he proposes a framework of factors that contribute to the decision to abandon a project and enumerates the risks and uncertainties inherent in each phase of a project's life cycle. Exploring the multiplicity of factors that make software development risky, he presents empirical data that is reinforced by analyses of the reported cases. He emphasizes the role of the user in the development process and considers the effect of organizational politics on a project. Finally, he considers what lessons can be learned from past failures and how software development practices can be improved.</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Computer software</subfield><subfield code="x">Development.</subfield><subfield code="0">http://id.loc.gov/authorities/subjects/sh85029535</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Software failures.</subfield><subfield code="0">http://id.loc.gov/authorities/subjects/sh97005329</subfield></datafield><datafield tag="650" ind1=" " ind2="0"><subfield code="a">Risk management.</subfield><subfield code="0">http://id.loc.gov/authorities/subjects/sh85114200</subfield></datafield><datafield tag="650" ind1=" " ind2="6"><subfield code="a">Bogues (Informatique)</subfield></datafield><datafield tag="650" ind1=" " ind2="6"><subfield code="a">Gestion du risque.</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">risk management.</subfield><subfield code="2">aat</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">COMPUTERS</subfield><subfield code="x">Programming</subfield><subfield code="x">Open Source.</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">COMPUTERS</subfield><subfield code="x">Software Development & Engineering</subfield><subfield code="x">Tools.</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">COMPUTERS</subfield><subfield code="x">Software Development & Engineering</subfield><subfield code="x">General.</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">Computer software</subfield><subfield code="x">Development</subfield><subfield code="2">fast</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">Risk management</subfield><subfield code="2">fast</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">Software failures</subfield><subfield code="2">fast</subfield></datafield><datafield tag="650" ind1="1" ind2="7"><subfield code="a">Software.</subfield><subfield code="2">gtt</subfield></datafield><datafield tag="650" ind1="1" ind2="7"><subfield code="a">Projectmanagement.</subfield><subfield code="2">gtt</subfield></datafield><datafield tag="650" ind1="1" ind2="7"><subfield code="a">Mislukkingen.</subfield><subfield code="2">gtt</subfield></datafield><datafield tag="653" ind1=" " ind2=" "><subfield code="a">COMPUTER SCIENCE/General</subfield></datafield><datafield tag="653" ind1=" " ind2=" "><subfield code="a">BUSINESS/Business Technology</subfield></datafield><datafield tag="655" ind1=" " ind2="0"><subfield code="a">Electronic books.</subfield></datafield><datafield tag="655" ind1=" " ind2="7"><subfield code="a">Casestudies (vorm)</subfield><subfield code="0">(NL-LeOCL)08814223X</subfield><subfield code="2">gtt</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Print version:</subfield><subfield code="a">Ewusi-Mensah, Kweku.</subfield><subfield code="t">Software development failures.</subfield><subfield code="d">Cambridge, Mass. : MIT Press, ©2003</subfield><subfield code="z">0262050722</subfield><subfield code="w">(DLC) 2002045504</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="l">FWS01</subfield><subfield code="p">ZDB-4-EBA</subfield><subfield code="q">FWS_PDA_EBA</subfield><subfield code="u">https://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&AN=100057</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="938" ind1=" " ind2=" "><subfield code="a">Books 24x7</subfield><subfield code="b">B247</subfield><subfield code="n">bks00003152</subfield></datafield><datafield tag="938" ind1=" " ind2=" "><subfield code="a">EBSCOhost</subfield><subfield code="b">EBSC</subfield><subfield code="n">100057</subfield></datafield><datafield tag="938" ind1=" " ind2=" "><subfield code="a">IEEE</subfield><subfield code="b">IEEE</subfield><subfield code="n">6267255</subfield></datafield><datafield tag="938" ind1=" " ind2=" "><subfield code="a">Internet Archive</subfield><subfield code="b">INAR</subfield><subfield code="n">softwaredevelopm0000ewus</subfield></datafield><datafield tag="938" ind1=" " ind2=" "><subfield code="a">YBP Library Services</subfield><subfield code="b">YANK</subfield><subfield code="n">3410820</subfield></datafield><datafield tag="938" ind1=" " ind2=" "><subfield code="a">YBP Library Services</subfield><subfield code="b">YANK</subfield><subfield code="n">2335966</subfield></datafield><datafield tag="994" ind1=" " ind2=" "><subfield code="a">92</subfield><subfield code="b">GEBAY</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-4-EBA</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-863</subfield></datafield></record></collection> |
| genre | Electronic books. Casestudies (vorm) (NL-LeOCL)08814223X gtt |
| genre_facet | Electronic books. Casestudies (vorm) |
| id | ZDB-4-EBA-ocm53907132 |
| illustrated | Not Illustrated |
| indexdate | 2024-11-27T13:15:29Z |
| institution | BVB |
| isbn | 9780262256087 0262256088 0585480834 9780585480831 9780262050722 0262050722 |
| language | English |
| oclc_num | 53907132 |
| open_access_boolean | |
| owner | MAIN DE-863 DE-BY-FWS |
| owner_facet | MAIN DE-863 DE-BY-FWS |
| physical | 1 online resource (xiv, 276 pages) |
| psigel | ZDB-4-EBA |
| publishDate | 2003 |
| publishDateSearch | 2003 |
| publishDateSort | 2003 |
| publisher | MIT Press, |
| record_format | marc |
| spelling | Ewusi-Mensah, Kweku. Software development failures : anatomy of abandoned projects / Kweku Ewusi-Mensah. Cambridge, Mass. : MIT Press, ©2003. 1 online resource (xiv, 276 pages) text txt rdacontent computer c rdamedia online resource cr rdacarrier Includes bibliographical references (pages 255-263) and index. I. Conceptual issues. Software development project failures -- Software project characteristics -- Factors critical to abandoned software projects -- II. Empirical factors. Socioorganizational factors and abandoned projects -- Technical factors and abandoned projects -- Economic factors and abandoned projects -- User perspectives on software development failures -- III. Learning from failures. Postabandonmnet review: learning from abandoned projects -- Software development: a strategic paradigm -- Project failures and aftermath. Print version record. Failed or abandoned software development projects cost the U.S. economy alone billions of dollars a year. In Software Development Failures, Kweku Ewusi-Mensah offers an empirically grounded study that suggests why these failures happen and how they can be avoided. Case studies analyzed include the well-known Confirm travel industry reservation program, FoxMeyer's Delta, the IRS's Tax System Modernization, the Denver International Airport's Baggage Handling System, and CODIS. It has been estimated that one-third of software development projects fail or are abandoned outright because of cost overruns, delays, and reduced functionality. Some consider this an acceptable risk -- that it is simply the cost of doing business. Ewusi-Mensah argues that understanding the factors involved in development failures will help developers and businesses bring down the rate of software failure and abandoned projects. Ewusi-Mensah explores the reasons software development projects are vulnerable to failure and why issues of management and organization are at the core of any failed project. He examines these projects not from a deterministically technical perspective but as part of a complex technical and social process; he proposes a framework of factors that contribute to the decision to abandon a project and enumerates the risks and uncertainties inherent in each phase of a project's life cycle. Exploring the multiplicity of factors that make software development risky, he presents empirical data that is reinforced by analyses of the reported cases. He emphasizes the role of the user in the development process and considers the effect of organizational politics on a project. Finally, he considers what lessons can be learned from past failures and how software development practices can be improved. Computer software Development. http://id.loc.gov/authorities/subjects/sh85029535 Software failures. http://id.loc.gov/authorities/subjects/sh97005329 Risk management. http://id.loc.gov/authorities/subjects/sh85114200 Bogues (Informatique) Gestion du risque. risk management. aat COMPUTERS Programming Open Source. bisacsh COMPUTERS Software Development & Engineering Tools. bisacsh COMPUTERS Software Development & Engineering General. bisacsh Computer software Development fast Risk management fast Software failures fast Software. gtt Projectmanagement. gtt Mislukkingen. gtt COMPUTER SCIENCE/General BUSINESS/Business Technology Electronic books. Casestudies (vorm) (NL-LeOCL)08814223X gtt Print version: Ewusi-Mensah, Kweku. Software development failures. Cambridge, Mass. : MIT Press, ©2003 0262050722 (DLC) 2002045504 FWS01 ZDB-4-EBA FWS_PDA_EBA https://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&AN=100057 Volltext |
| spellingShingle | Ewusi-Mensah, Kweku Software development failures : anatomy of abandoned projects / I. Conceptual issues. Software development project failures -- Software project characteristics -- Factors critical to abandoned software projects -- II. Empirical factors. Socioorganizational factors and abandoned projects -- Technical factors and abandoned projects -- Economic factors and abandoned projects -- User perspectives on software development failures -- III. Learning from failures. Postabandonmnet review: learning from abandoned projects -- Software development: a strategic paradigm -- Project failures and aftermath. Computer software Development. http://id.loc.gov/authorities/subjects/sh85029535 Software failures. http://id.loc.gov/authorities/subjects/sh97005329 Risk management. http://id.loc.gov/authorities/subjects/sh85114200 Bogues (Informatique) Gestion du risque. risk management. aat COMPUTERS Programming Open Source. bisacsh COMPUTERS Software Development & Engineering Tools. bisacsh COMPUTERS Software Development & Engineering General. bisacsh Computer software Development fast Risk management fast Software failures fast Software. gtt Projectmanagement. gtt Mislukkingen. gtt |
| subject_GND | http://id.loc.gov/authorities/subjects/sh85029535 http://id.loc.gov/authorities/subjects/sh97005329 http://id.loc.gov/authorities/subjects/sh85114200 (NL-LeOCL)08814223X |
| title | Software development failures : anatomy of abandoned projects / |
| title_auth | Software development failures : anatomy of abandoned projects / |
| title_exact_search | Software development failures : anatomy of abandoned projects / |
| title_full | Software development failures : anatomy of abandoned projects / Kweku Ewusi-Mensah. |
| title_fullStr | Software development failures : anatomy of abandoned projects / Kweku Ewusi-Mensah. |
| title_full_unstemmed | Software development failures : anatomy of abandoned projects / Kweku Ewusi-Mensah. |
| title_short | Software development failures : |
| title_sort | software development failures anatomy of abandoned projects |
| title_sub | anatomy of abandoned projects / |
| topic | Computer software Development. http://id.loc.gov/authorities/subjects/sh85029535 Software failures. http://id.loc.gov/authorities/subjects/sh97005329 Risk management. http://id.loc.gov/authorities/subjects/sh85114200 Bogues (Informatique) Gestion du risque. risk management. aat COMPUTERS Programming Open Source. bisacsh COMPUTERS Software Development & Engineering Tools. bisacsh COMPUTERS Software Development & Engineering General. bisacsh Computer software Development fast Risk management fast Software failures fast Software. gtt Projectmanagement. gtt Mislukkingen. gtt |
| topic_facet | Computer software Development. Software failures. Risk management. Bogues (Informatique) Gestion du risque. risk management. COMPUTERS Programming Open Source. COMPUTERS Software Development & Engineering Tools. COMPUTERS Software Development & Engineering General. Computer software Development Risk management Software failures Software. Projectmanagement. Mislukkingen. Electronic books. Casestudies (vorm) |
| url | https://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&AN=100057 |
| work_keys_str_mv | AT ewusimensahkweku softwaredevelopmentfailuresanatomyofabandonedprojects |