ABSTRACT
As Deephouse et al. (1995) note, “A large proportion of systems developed to meet unrealistic commitments may be one cause of the high level of software maintenance expenses reported by many firms” (p. 191). They further state, “When not planned, as in a prototyping strategy, rework can play havoc with schedules and budgets. Substantial rework often introduces new bugs to a system, lowering overall quality” (p. 194). Jorgensen and Boehm (2009) note that challenges still exist in the software project estimation process and less than 10% of projects coming within 10% of initial estimates is the norm. This is after many years of attempting to improve software project estimation (a key component of the planning phase) both through formal methods and better practices within the IT project management community.
