State | Team | Sport |
---|---|---|
Ohio | Indians | Baseball |
Texas | Rangers | Basball |
Software Project Failure Factors | In-house % | Outsourced % | Overall %![]() |
---|---|---|---|
Customers/Users did not make adequate time available for requirements gathering | 61.2 | 57.1 | 60.0 |
Project had inadequate staff to meet the schedule | 63.3 | 57.1 | 61.4 |
Staff added late to meet an aggressive schedule | 61.2 | 61.9 | 61.4 |
Schedule had a negative effect on team member\x{2019}s life | 71.4 | 42.9 | 62.9 |
Scope changed during the project | 67.3 | 57.1 | 64.3 |
Development Methodology was inappropriate for the project | 71.4 | 52.4 | 65.7 |
Aggressive schedule affected team motivation | 69.4 | 57.1 | 65.7 |
Process did not have reviews at the end of each phase | 75.5 | 47.6 | 67.1 |
Customer/Users had unrealistic expectations | 69.4 | 66.7 | 68.6 |
Risk not incorporated into the project plan | 65.3 | 80.9 | 70.0 |
Change control not monitored, nor dealt with effectively | 63.3 | 85.7 | 70.0 |
Customers/Users not involved in making schedule estimates | 69.4 | 76.2 | 71.4 |
Delivery decision made without adequate requirements information | 83.7 | 47.6 | 72.9 |
Staff had an unpleasant experience working on the project | 83.7 | 47.6 | 72.9 |
Staff were not rewarded for working long hours | 81.6 | 57.1 | 74.3 |
Risks were not re-assessed, controlled, or managed through the project | 73.4 | 80.9 | 75.7 |
Project under-estimated | 83.7 | 76.2 | 81.4 |
Delivery date impacted the development process | 93.9 | 90.5 | 92.9 |
I | Attachment | Action | Size | Date | Who | Comment |
---|---|---|---|---|---|---|
![]() |
DrawingName.draw | manage | 4.3 K | 2010-02-13 - 16:52 | JimSkon | TWiki Draw draw file |
![]() |
DrawingName.gif | manage | 5.4 K | 2010-02-13 - 16:53 | JimSkon | TWiki Draw GIF file |