More Problems
Other Risks
Customer sees no product until first release
Customer often cannot provide early feedback to early design, coding decisions
Late determination that system aims do not meet actual needs
Some identified features never really used
Some forgotten features highly desired
Design may anticipate different features than actually desired or needed
Customer distant from Developer
Customer not actively engaged in cost overruns, delays
If (when?) time runs short, customer often not involved in setting priorities
If (when?) money short (or cost overruns arise), project may be canceled before first release
Staff turnover (best staff may leave for new challenges before 2 years)
Integration and testing late
debugging expensive
defect rate may be high, as integration proceeds
created April 29, 2003
last revised April 14, 2003
previous
next