{'fraction_non_alphanumeric': 0.01267605633802817, 'fraction_numerical': 0.0, 'mean_word_length': 5.609302325581395, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Why software projects escalate: the importance of project management constructs

Previous research has documented that software projects are frequently prone to escalation. While the escalation literature acknowledges that project-related (as well as psychological, social, and organizational) factors can promote escalation behavior, there has been no investigation regarding the role that project management factors may have in discriminating between projects that escalate and those that do not. The objective of this study was to explore whether project management constructs could be used to distinguish between projects that escalated and those that did not. Based on a survey administered to IS audit and control professionals, data were gathered on projects that did not escalate as well as those that did escalate. We then applied logistic regression to model the relationship between various project management constructs and project escalation. The model was then evaluated for its ability to correctly classify the projects. The results of our research suggest that a logistic regression model based on project management constructs is capable of discriminating between projects that escalate and those that do not. Moreover, the model compares favorably to a previously published logistic regression model based on constructs derived from escalation theory. The implications of these findings are discussed.