Project recovery: case studies and techniques for overcoming project failure
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Elektronisch E-Book |
| Sprache: | English |
| Veröffentlicht: |
Hoboken, New Jersey
Wiley
2014
|
| Schlagworte: | |
| Online-Zugang: | TUM01 Volltext |
| Beschreibung: | Includes index Best practices for picking up the pieces when projects fail There are plenty of books available offering best practices that help you keep your projects on track, but offer guidance on what to do when the worst has already happened. Some studies show that more than half of all large-scale project fail either fail completely, or at least miss targeted budget and scheduling goals. These failures cost organizations time, money, and labor. Project Recovery offers wise guidance and real-world best practices for saving failed projects and recovering as much value as possible from the wreckage. Sinc Project Recovery: Case Studies and Techniques for Overcoming Project Failure; Copyright; Contents; Preface; Chapter 1: Understanding Success and Failure; 1.0 Introduction; 1.1 Success: Historical Perspective; 1.2 Early Modifications to Triple Constraints; 1.3 Primary and Secondary Constraints; 1.4 Prioritization of Constraints; 1.5 From Triple Constraints to Competing Constraints; 1.6 Future Definitions of Project Success; 1.7 Different Definitions of Project Success; 1.8 Understanding Project Failure; 1.9 Degrees of Project Failure; 1.10 Other Categories of Project Failure 1.11 Summary of Lessons LearnedChapter 2: Causes of Project Failure; 2.0 Introduction; 2.1 Facts About Project Failure; 2.2 Causes of Project Failure; 2.3 Schedule Failure; 2.4 Failures Due to Unknown Technology; 2.5 Project Size and Success/Failure Risk; 2.6 Failure Due to Improper Critical Failure Factors; 2.7 Failure to Establish Tracking Metrics; 2.8 Failing to Recognize Early Warning Signs; 2.9 Improper Selection of Critical Team Members; 2.10 Uncertain Rewards; 2.11 Estimating Failures; 2.12 Staffing Failures; 2.13 Planning Failures; 2.14 Risk Management Failures 2.15 Management Mistakes2.16 Lacking Sufficient Tools; 2.17 Failure of Success; 2.18 Motivation to Fail; 2.19 Tradeoff Failures; 2.20 Summary of Lessons Learned; Chapter 3: Business Case Failure; 3.0 Introduction; 3.1 Changing Stakeholders; 3.2 Revalidation of Assumptions; 3.3 Managing Innovation; 3.4 Examples of Changing Business Cases; 3.5 Prologue to the Iridium Case Study; 3.6 Rise, Fall and Resurrection of Iridium; Naming the Project "Iridium"; Obtaining Executive Support; Launching the Venture; Iridium System; Terrestial and Space-Based Network Project Initiation: Developing Business Case"Hidden" Business Case; Risk Management; Collective Belief; Iridium's Infancy Years; Debt Financing; M-Star Project; A New CEO; Project Management at Motorola (Iridium); Satellite Launches; Initial Public Offering (IPO); Signing Up Customers; Iridium's Rapid Ascent; Iridium's Rapid Descent; Iridium "Flu"; Definition of Failure (October 1999); 3.7 Summary of Lessons Learned; Chapter 4: Sponsorship/Governance Failures; 4.0 Introduction; 4.1 Defining Project Governance; 4.2 Project Versus Corporate Governance 4.3 Roles, Responsibilities and Decision-Making Authority4.4 Governance Frameworks; 4.5 Governance Failures; 4.6 Why Projects are Hard to Kill; 4.7 Collective Belief; 4.8 Exit Champion; 4.9 When to Give Up; 4.10 Prologue to the Denver International Airport Case Study; 4.11 Denver International Airport; Background; Airports and Airline Deregulation; Does Denver Need a New Airport?; Enplaned Passenger Market; Land Selection; Front Range Airport; Airport Design; Project Management; Baggage-Handling System; Early Risk Analysis; March 1991; April 1991; May 1991; August 1991; November 1991 |
| Beschreibung: | 1 Online-Ressource (xii, 323 pages) |
| ISBN: | 1118809122 1118809173 1118841611 9781118809129 9781118809174 9781118841617 |
Internformat
MARC
| LEADER | 00000nmm a2200000zc 4500 | ||
|---|---|---|---|
| 001 | BV041990474 | ||
| 003 | DE-604 | ||
| 005 | 20140724 | ||
| 007 | cr|uuu---uuuuu | ||
| 008 | 140723s2014 |||| o||u| ||||||eng d | ||
| 020 | |a 1118809122 |c electronic bk. |9 1-118-80912-2 | ||
| 020 | |a 1118809173 |c electronic bk. |9 1-118-80917-3 | ||
| 020 | |a 1118841611 |c electronic bk. |9 1-118-84161-1 | ||
| 020 | |a 9781118809129 |c electronic bk. |9 978-1-118-80912-9 | ||
| 020 | |a 9781118809174 |c electronic bk. |9 978-1-118-80917-4 | ||
| 020 | |a 9781118841617 |c electronic bk. |9 978-1-118-84161-7 | ||
| 035 | |a (OCoLC)857754214 | ||
| 035 | |a (DE-599)BVBBV041990474 | ||
| 040 | |a DE-604 |b ger |e aacr | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-91 | ||
| 082 | 0 | |a 658.4/04 |2 23 | |
| 100 | 1 | |a Kerzner, Harold |d 1940- |e Verfasser |0 (DE-588)124166229 |4 aut | |
| 245 | 1 | 0 | |a Project recovery |b case studies and techniques for overcoming project failure |c Harold Kerzner |
| 264 | 1 | |a Hoboken, New Jersey |b Wiley |c 2014 | |
| 300 | |a 1 Online-Ressource (xii, 323 pages) | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b c |2 rdamedia | ||
| 338 | |b cr |2 rdacarrier | ||
| 500 | |a Includes index | ||
| 500 | |a Best practices for picking up the pieces when projects fail There are plenty of books available offering best practices that help you keep your projects on track, but offer guidance on what to do when the worst has already happened. Some studies show that more than half of all large-scale project fail either fail completely, or at least miss targeted budget and scheduling goals. These failures cost organizations time, money, and labor. Project Recovery offers wise guidance and real-world best practices for saving failed projects and recovering as much value as possible from the wreckage. Sinc | ||
| 500 | |a Project Recovery: Case Studies and Techniques for Overcoming Project Failure; Copyright; Contents; Preface; Chapter 1: Understanding Success and Failure; 1.0 Introduction; 1.1 Success: Historical Perspective; 1.2 Early Modifications to Triple Constraints; 1.3 Primary and Secondary Constraints; 1.4 Prioritization of Constraints; 1.5 From Triple Constraints to Competing Constraints; 1.6 Future Definitions of Project Success; 1.7 Different Definitions of Project Success; 1.8 Understanding Project Failure; 1.9 Degrees of Project Failure; 1.10 Other Categories of Project Failure | ||
| 500 | |a 1.11 Summary of Lessons LearnedChapter 2: Causes of Project Failure; 2.0 Introduction; 2.1 Facts About Project Failure; 2.2 Causes of Project Failure; 2.3 Schedule Failure; 2.4 Failures Due to Unknown Technology; 2.5 Project Size and Success/Failure Risk; 2.6 Failure Due to Improper Critical Failure Factors; 2.7 Failure to Establish Tracking Metrics; 2.8 Failing to Recognize Early Warning Signs; 2.9 Improper Selection of Critical Team Members; 2.10 Uncertain Rewards; 2.11 Estimating Failures; 2.12 Staffing Failures; 2.13 Planning Failures; 2.14 Risk Management Failures | ||
| 500 | |a 2.15 Management Mistakes2.16 Lacking Sufficient Tools; 2.17 Failure of Success; 2.18 Motivation to Fail; 2.19 Tradeoff Failures; 2.20 Summary of Lessons Learned; Chapter 3: Business Case Failure; 3.0 Introduction; 3.1 Changing Stakeholders; 3.2 Revalidation of Assumptions; 3.3 Managing Innovation; 3.4 Examples of Changing Business Cases; 3.5 Prologue to the Iridium Case Study; 3.6 Rise, Fall and Resurrection of Iridium; Naming the Project "Iridium"; Obtaining Executive Support; Launching the Venture; Iridium System; Terrestial and Space-Based Network | ||
| 500 | |a Project Initiation: Developing Business Case"Hidden" Business Case; Risk Management; Collective Belief; Iridium's Infancy Years; Debt Financing; M-Star Project; A New CEO; Project Management at Motorola (Iridium); Satellite Launches; Initial Public Offering (IPO); Signing Up Customers; Iridium's Rapid Ascent; Iridium's Rapid Descent; Iridium "Flu"; Definition of Failure (October 1999); 3.7 Summary of Lessons Learned; Chapter 4: Sponsorship/Governance Failures; 4.0 Introduction; 4.1 Defining Project Governance; 4.2 Project Versus Corporate Governance | ||
| 500 | |a 4.3 Roles, Responsibilities and Decision-Making Authority4.4 Governance Frameworks; 4.5 Governance Failures; 4.6 Why Projects are Hard to Kill; 4.7 Collective Belief; 4.8 Exit Champion; 4.9 When to Give Up; 4.10 Prologue to the Denver International Airport Case Study; 4.11 Denver International Airport; Background; Airports and Airline Deregulation; Does Denver Need a New Airport?; Enplaned Passenger Market; Land Selection; Front Range Airport; Airport Design; Project Management; Baggage-Handling System; Early Risk Analysis; March 1991; April 1991; May 1991; August 1991; November 1991 | ||
| 650 | 7 | |a BUSINESS & ECONOMICS / Industrial Management |2 bisacsh | |
| 650 | 7 | |a BUSINESS & ECONOMICS / Management |2 bisacsh | |
| 650 | 7 | |a BUSINESS & ECONOMICS / Management Science |2 bisacsh | |
| 650 | 7 | |a BUSINESS & ECONOMICS / Organizational Behavior |2 bisacsh | |
| 650 | 4 | |a Wirtschaft | |
| 650 | 4 | |a Project management | |
| 650 | 0 | 7 | |a Projektmanagement |0 (DE-588)4047441-0 |2 gnd |9 rswk-swf |
| 653 | |a Electronic books | ||
| 689 | 0 | 0 | |a Projektmanagement |0 (DE-588)4047441-0 |D s |
| 689 | 0 | |8 1\p |5 DE-604 | |
| 776 | 0 | 8 | |i Erscheint auch als |n Druck-Ausgabe, Hardcover |z 1-118-80919-X |
| 776 | 0 | 8 | |i Erscheint auch als |n Druck-Ausgabe, Hardcover |z 978-1-118-80919-8 |
| 856 | 4 | 0 | |u http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=698897 |x Aggregator |3 Volltext |
| 912 | |a ZDB-4-NLEBK | ||
| 999 | |a oai:aleph.bib-bvb.de:BVB01-027432722 | ||
| 883 | 1 | |8 1\p |a cgwrk |d 20201028 |q DE-101 |u https://d-nb.info/provenance/plan#cgwrk | |
| 966 | e | |u http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=698897 |l TUM01 |p ZDB-4-NLEBK |q TUM_PDA_EBSCO_BAE_gekauft |x Aggregator |3 Volltext | |
Datensatz im Suchindex
| _version_ | 1804152394973446144 |
|---|---|
| any_adam_object | |
| author | Kerzner, Harold 1940- |
| author_GND | (DE-588)124166229 |
| author_facet | Kerzner, Harold 1940- |
| author_role | aut |
| author_sort | Kerzner, Harold 1940- |
| author_variant | h k hk |
| building | Verbundindex |
| bvnumber | BV041990474 |
| collection | ZDB-4-NLEBK |
| ctrlnum | (OCoLC)857754214 (DE-599)BVBBV041990474 |
| dewey-full | 658.4/04 |
| dewey-hundreds | 600 - Technology (Applied sciences) |
| dewey-ones | 658 - General management |
| dewey-raw | 658.4/04 |
| dewey-search | 658.4/04 |
| dewey-sort | 3658.4 14 |
| dewey-tens | 650 - Management and auxiliary services |
| discipline | Wirtschaftswissenschaften |
| format | Electronic eBook |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>05828nmm a2200601zc 4500</leader><controlfield tag="001">BV041990474</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20140724 </controlfield><controlfield tag="007">cr|uuu---uuuuu</controlfield><controlfield tag="008">140723s2014 |||| o||u| ||||||eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">1118809122</subfield><subfield code="c">electronic bk.</subfield><subfield code="9">1-118-80912-2</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">1118809173</subfield><subfield code="c">electronic bk.</subfield><subfield code="9">1-118-80917-3</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">1118841611</subfield><subfield code="c">electronic bk.</subfield><subfield code="9">1-118-84161-1</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781118809129</subfield><subfield code="c">electronic bk.</subfield><subfield code="9">978-1-118-80912-9</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781118809174</subfield><subfield code="c">electronic bk.</subfield><subfield code="9">978-1-118-80917-4</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9781118841617</subfield><subfield code="c">electronic bk.</subfield><subfield code="9">978-1-118-84161-7</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)857754214</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV041990474</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">aacr</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-91</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">658.4/04</subfield><subfield code="2">23</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Kerzner, Harold</subfield><subfield code="d">1940-</subfield><subfield code="e">Verfasser</subfield><subfield code="0">(DE-588)124166229</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Project recovery</subfield><subfield code="b">case studies and techniques for overcoming project failure</subfield><subfield code="c">Harold Kerzner</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Hoboken, New Jersey</subfield><subfield code="b">Wiley</subfield><subfield code="c">2014</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">1 Online-Ressource (xii, 323 pages)</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Includes index</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Best practices for picking up the pieces when projects fail There are plenty of books available offering best practices that help you keep your projects on track, but offer guidance on what to do when the worst has already happened. Some studies show that more than half of all large-scale project fail either fail completely, or at least miss targeted budget and scheduling goals. These failures cost organizations time, money, and labor. Project Recovery offers wise guidance and real-world best practices for saving failed projects and recovering as much value as possible from the wreckage. Sinc</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Project Recovery: Case Studies and Techniques for Overcoming Project Failure; Copyright; Contents; Preface; Chapter 1: Understanding Success and Failure; 1.0 Introduction; 1.1 Success: Historical Perspective; 1.2 Early Modifications to Triple Constraints; 1.3 Primary and Secondary Constraints; 1.4 Prioritization of Constraints; 1.5 From Triple Constraints to Competing Constraints; 1.6 Future Definitions of Project Success; 1.7 Different Definitions of Project Success; 1.8 Understanding Project Failure; 1.9 Degrees of Project Failure; 1.10 Other Categories of Project Failure</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">1.11 Summary of Lessons LearnedChapter 2: Causes of Project Failure; 2.0 Introduction; 2.1 Facts About Project Failure; 2.2 Causes of Project Failure; 2.3 Schedule Failure; 2.4 Failures Due to Unknown Technology; 2.5 Project Size and Success/Failure Risk; 2.6 Failure Due to Improper Critical Failure Factors; 2.7 Failure to Establish Tracking Metrics; 2.8 Failing to Recognize Early Warning Signs; 2.9 Improper Selection of Critical Team Members; 2.10 Uncertain Rewards; 2.11 Estimating Failures; 2.12 Staffing Failures; 2.13 Planning Failures; 2.14 Risk Management Failures</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">2.15 Management Mistakes2.16 Lacking Sufficient Tools; 2.17 Failure of Success; 2.18 Motivation to Fail; 2.19 Tradeoff Failures; 2.20 Summary of Lessons Learned; Chapter 3: Business Case Failure; 3.0 Introduction; 3.1 Changing Stakeholders; 3.2 Revalidation of Assumptions; 3.3 Managing Innovation; 3.4 Examples of Changing Business Cases; 3.5 Prologue to the Iridium Case Study; 3.6 Rise, Fall and Resurrection of Iridium; Naming the Project "Iridium"; Obtaining Executive Support; Launching the Venture; Iridium System; Terrestial and Space-Based Network</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Project Initiation: Developing Business Case"Hidden" Business Case; Risk Management; Collective Belief; Iridium's Infancy Years; Debt Financing; M-Star Project; A New CEO; Project Management at Motorola (Iridium); Satellite Launches; Initial Public Offering (IPO); Signing Up Customers; Iridium's Rapid Ascent; Iridium's Rapid Descent; Iridium "Flu"; Definition of Failure (October 1999); 3.7 Summary of Lessons Learned; Chapter 4: Sponsorship/Governance Failures; 4.0 Introduction; 4.1 Defining Project Governance; 4.2 Project Versus Corporate Governance</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">4.3 Roles, Responsibilities and Decision-Making Authority4.4 Governance Frameworks; 4.5 Governance Failures; 4.6 Why Projects are Hard to Kill; 4.7 Collective Belief; 4.8 Exit Champion; 4.9 When to Give Up; 4.10 Prologue to the Denver International Airport Case Study; 4.11 Denver International Airport; Background; Airports and Airline Deregulation; Does Denver Need a New Airport?; Enplaned Passenger Market; Land Selection; Front Range Airport; Airport Design; Project Management; Baggage-Handling System; Early Risk Analysis; March 1991; April 1991; May 1991; August 1991; November 1991</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">BUSINESS & ECONOMICS / Industrial Management</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">BUSINESS & ECONOMICS / Management</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">BUSINESS & ECONOMICS / Management Science</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="7"><subfield code="a">BUSINESS & ECONOMICS / Organizational Behavior</subfield><subfield code="2">bisacsh</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Wirtschaft</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Project management</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Projektmanagement</subfield><subfield code="0">(DE-588)4047441-0</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="653" ind1=" " ind2=" "><subfield code="a">Electronic books</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Projektmanagement</subfield><subfield code="0">(DE-588)4047441-0</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="8">1\p</subfield><subfield code="5">DE-604</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Druck-Ausgabe, Hardcover</subfield><subfield code="z">1-118-80919-X</subfield></datafield><datafield tag="776" ind1="0" ind2="8"><subfield code="i">Erscheint auch als</subfield><subfield code="n">Druck-Ausgabe, Hardcover</subfield><subfield code="z">978-1-118-80919-8</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=698897</subfield><subfield code="x">Aggregator</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">ZDB-4-NLEBK</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-027432722</subfield></datafield><datafield tag="883" ind1="1" ind2=" "><subfield code="8">1\p</subfield><subfield code="a">cgwrk</subfield><subfield code="d">20201028</subfield><subfield code="q">DE-101</subfield><subfield code="u">https://d-nb.info/provenance/plan#cgwrk</subfield></datafield><datafield tag="966" ind1="e" ind2=" "><subfield code="u">http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=698897</subfield><subfield code="l">TUM01</subfield><subfield code="p">ZDB-4-NLEBK</subfield><subfield code="q">TUM_PDA_EBSCO_BAE_gekauft</subfield><subfield code="x">Aggregator</subfield><subfield code="3">Volltext</subfield></datafield></record></collection> |
| id | DE-604.BV041990474 |
| illustrated | Not Illustrated |
| indexdate | 2024-07-10T01:10:01Z |
| institution | BVB |
| isbn | 1118809122 1118809173 1118841611 9781118809129 9781118809174 9781118841617 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-027432722 |
| oclc_num | 857754214 |
| open_access_boolean | |
| owner | DE-91 DE-BY-TUM |
| owner_facet | DE-91 DE-BY-TUM |
| physical | 1 Online-Ressource (xii, 323 pages) |
| psigel | ZDB-4-NLEBK ZDB-4-NLEBK TUM_PDA_EBSCO_BAE_gekauft |
| publishDate | 2014 |
| publishDateSearch | 2014 |
| publishDateSort | 2014 |
| publisher | Wiley |
| record_format | marc |
| spelling | Kerzner, Harold 1940- Verfasser (DE-588)124166229 aut Project recovery case studies and techniques for overcoming project failure Harold Kerzner Hoboken, New Jersey Wiley 2014 1 Online-Ressource (xii, 323 pages) txt rdacontent c rdamedia cr rdacarrier Includes index Best practices for picking up the pieces when projects fail There are plenty of books available offering best practices that help you keep your projects on track, but offer guidance on what to do when the worst has already happened. Some studies show that more than half of all large-scale project fail either fail completely, or at least miss targeted budget and scheduling goals. These failures cost organizations time, money, and labor. Project Recovery offers wise guidance and real-world best practices for saving failed projects and recovering as much value as possible from the wreckage. Sinc Project Recovery: Case Studies and Techniques for Overcoming Project Failure; Copyright; Contents; Preface; Chapter 1: Understanding Success and Failure; 1.0 Introduction; 1.1 Success: Historical Perspective; 1.2 Early Modifications to Triple Constraints; 1.3 Primary and Secondary Constraints; 1.4 Prioritization of Constraints; 1.5 From Triple Constraints to Competing Constraints; 1.6 Future Definitions of Project Success; 1.7 Different Definitions of Project Success; 1.8 Understanding Project Failure; 1.9 Degrees of Project Failure; 1.10 Other Categories of Project Failure 1.11 Summary of Lessons LearnedChapter 2: Causes of Project Failure; 2.0 Introduction; 2.1 Facts About Project Failure; 2.2 Causes of Project Failure; 2.3 Schedule Failure; 2.4 Failures Due to Unknown Technology; 2.5 Project Size and Success/Failure Risk; 2.6 Failure Due to Improper Critical Failure Factors; 2.7 Failure to Establish Tracking Metrics; 2.8 Failing to Recognize Early Warning Signs; 2.9 Improper Selection of Critical Team Members; 2.10 Uncertain Rewards; 2.11 Estimating Failures; 2.12 Staffing Failures; 2.13 Planning Failures; 2.14 Risk Management Failures 2.15 Management Mistakes2.16 Lacking Sufficient Tools; 2.17 Failure of Success; 2.18 Motivation to Fail; 2.19 Tradeoff Failures; 2.20 Summary of Lessons Learned; Chapter 3: Business Case Failure; 3.0 Introduction; 3.1 Changing Stakeholders; 3.2 Revalidation of Assumptions; 3.3 Managing Innovation; 3.4 Examples of Changing Business Cases; 3.5 Prologue to the Iridium Case Study; 3.6 Rise, Fall and Resurrection of Iridium; Naming the Project "Iridium"; Obtaining Executive Support; Launching the Venture; Iridium System; Terrestial and Space-Based Network Project Initiation: Developing Business Case"Hidden" Business Case; Risk Management; Collective Belief; Iridium's Infancy Years; Debt Financing; M-Star Project; A New CEO; Project Management at Motorola (Iridium); Satellite Launches; Initial Public Offering (IPO); Signing Up Customers; Iridium's Rapid Ascent; Iridium's Rapid Descent; Iridium "Flu"; Definition of Failure (October 1999); 3.7 Summary of Lessons Learned; Chapter 4: Sponsorship/Governance Failures; 4.0 Introduction; 4.1 Defining Project Governance; 4.2 Project Versus Corporate Governance 4.3 Roles, Responsibilities and Decision-Making Authority4.4 Governance Frameworks; 4.5 Governance Failures; 4.6 Why Projects are Hard to Kill; 4.7 Collective Belief; 4.8 Exit Champion; 4.9 When to Give Up; 4.10 Prologue to the Denver International Airport Case Study; 4.11 Denver International Airport; Background; Airports and Airline Deregulation; Does Denver Need a New Airport?; Enplaned Passenger Market; Land Selection; Front Range Airport; Airport Design; Project Management; Baggage-Handling System; Early Risk Analysis; March 1991; April 1991; May 1991; August 1991; November 1991 BUSINESS & ECONOMICS / Industrial Management bisacsh BUSINESS & ECONOMICS / Management bisacsh BUSINESS & ECONOMICS / Management Science bisacsh BUSINESS & ECONOMICS / Organizational Behavior bisacsh Wirtschaft Project management Projektmanagement (DE-588)4047441-0 gnd rswk-swf Electronic books Projektmanagement (DE-588)4047441-0 s 1\p DE-604 Erscheint auch als Druck-Ausgabe, Hardcover 1-118-80919-X Erscheint auch als Druck-Ausgabe, Hardcover 978-1-118-80919-8 http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=698897 Aggregator Volltext 1\p cgwrk 20201028 DE-101 https://d-nb.info/provenance/plan#cgwrk |
| spellingShingle | Kerzner, Harold 1940- Project recovery case studies and techniques for overcoming project failure BUSINESS & ECONOMICS / Industrial Management bisacsh BUSINESS & ECONOMICS / Management bisacsh BUSINESS & ECONOMICS / Management Science bisacsh BUSINESS & ECONOMICS / Organizational Behavior bisacsh Wirtschaft Project management Projektmanagement (DE-588)4047441-0 gnd |
| subject_GND | (DE-588)4047441-0 |
| title | Project recovery case studies and techniques for overcoming project failure |
| title_auth | Project recovery case studies and techniques for overcoming project failure |
| title_exact_search | Project recovery case studies and techniques for overcoming project failure |
| title_full | Project recovery case studies and techniques for overcoming project failure Harold Kerzner |
| title_fullStr | Project recovery case studies and techniques for overcoming project failure Harold Kerzner |
| title_full_unstemmed | Project recovery case studies and techniques for overcoming project failure Harold Kerzner |
| title_short | Project recovery |
| title_sort | project recovery case studies and techniques for overcoming project failure |
| title_sub | case studies and techniques for overcoming project failure |
| topic | BUSINESS & ECONOMICS / Industrial Management bisacsh BUSINESS & ECONOMICS / Management bisacsh BUSINESS & ECONOMICS / Management Science bisacsh BUSINESS & ECONOMICS / Organizational Behavior bisacsh Wirtschaft Project management Projektmanagement (DE-588)4047441-0 gnd |
| topic_facet | BUSINESS & ECONOMICS / Industrial Management BUSINESS & ECONOMICS / Management BUSINESS & ECONOMICS / Management Science BUSINESS & ECONOMICS / Organizational Behavior Wirtschaft Project management Projektmanagement |
| url | http://search.ebscohost.com/login.aspx?direct=true&scope=site&db=nlebk&db=nlabk&AN=698897 |
| work_keys_str_mv | AT kerznerharold projectrecoverycasestudiesandtechniquesforovercomingprojectfailure |