Abstract
Accurate project status reporting is important to avoid the problem of information technology (IT) project escalation and to successfully manage and deliver IT projects. One approach that some organizations have taken is to audit their IT projects to avoid surprises that are frequently associated with inaccurate status reporting. Little is known, however, about the effects that such auditing arrangements can have on the dynamics of project status reporting. To examine the process of IT project status reporting in this context, we followed a grounded theory inspired approach in which we investigated nine IT projects in one U.S. state’s government agencies. All of the projects we studied were subject to the state’s IT oversight board. Based on 118 interviews with a variety of stakeholders including technical personnel, managers, users, and contractors, we present a grounded theory of project status reporting dynamics in which the reporting process can best be characterized as a self-reinforcing cycle of distrust between the project team and the auditors. Specifically, in some projects, we observed a pattern whereby project teams interpreted the auditor’s scrutiny as unfair and as not adding value to their projects. As a result, they responded by embracing some defensive reporting tactics. The auditors interpreted the project team’s actions as indicating either deception or incompetence, and they then increased their scrutiny of the reports, thus exacerbating the situation and further fuelling the cycle of distrust. We discuss implications for both theory and practice.
Recommended Citation
Keil, Mark; Smith, H. Jeff; Iacovou, Charalambos L.; and Thompson, Ronald L.
(2014)
"The Dynamics of IT Project Status Reporting: A Self-Reinforcing Cycle of Distrust,"
Journal of the Association for Information Systems, 15(12), .
DOI: 10.17705/1jais.00383
Available at:
https://aisel.aisnet.org/jais/vol15/iss12/1
DOI
10.17705/1jais.00383
When commenting on articles, please be friendly, welcoming, respectful and abide by the AIS eLibrary Discussion Thread Code of Conduct posted here.