Key points of failure for IT project business cases

Abstract

Large IT projects at companies generally underperform expectations—they either are delivered late, come in over budget, or fail to deliver their expected benefits. Studies reveal that there is no single driving factor for these failures, and no single “magic bullet” solution. But are many projects doomed from the start to underperform expectations—because the expectations were inappropriately set? This article focuses on this key element—the setting of expectations in the form of a formal business case. The author discusses five key points of failure in IT business cases, why they occur, and how they can be avoided. © 2012 Wiley Periodicals, Inc.

Process improvement project failure: a systematic literature review and future research agenda

“…Scope management techniques should be incorporated at the project planning stage and any necessary changes should occur through the formal control procedures within the predetermined time and costs (Antony and Gupta, 2018). Projects with clear (as defined by Iijima, 2012) and stretch-objectives are expected to yield higher results and stimulate experimentation and learning by organizational actors (Dillon and Madsen, 2015).…”