Understanding the “90% syndrome" in software project management: a simulation-based case study
Journal of Systems and Software
Software project management
Components of Software Development Risk: How to Address Them? A Project Manager Survey
IEEE Transactions on Software Engineering
The Mythical Man-Month: Essays on Softw
The Mythical Man-Month: Essays on Softw
Critical Success Factors In Software Projects
IEEE Software
The Challenges of Accurate Project Status Reporting
HICSS '01 Proceedings of the 34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 8 - Volume 8
Escalating commitment to information system projects: findings from two simulated experiments
Information and Management
Understanding software project risk: a cluster analysis
Information and Management
Keeping Mum as the Project Goes Under: Toward an Explanatory Model
Journal of Management Information Systems
Management of large software development efforts
MIS Quarterly
IEEE Transactions on Systems, Man, and Cybernetics, Part A: Systems and Humans
Analysis of systems development project risks: an integrative framework
ACM SIGMIS Database
Analyzing project risks within a cultural and organizational setting
LMSA '09 Proceedings of the 2009 ICSE Workshop on Leadership and Management in Software Architecture
Runaway Information Technology Projects: A Punctuated Equilibrium Analysis
International Journal of Information Technology Project Management
Hi-index | 0.00 |
Anecdotal evidence suggests that project managers (PMs) sometime provide biased status reports to management. In our research project we surveyed PMs to explore possible motivations for bias, the frequency with which bias occurs, and the strength of the bias typically applied. We found that status reports were biased 60% of the time and that the bias was twice as likely to be optimistic as pessimistic. By applying these results to an information-theoretic model, we estimated that only about 10-15% of biased project status reports were, in fact, accurate and these occurred only when pessimistic bias offset project management status errors. There appeared to be no significant difference in the type or frequency of bias applied to high-risk versus low-risk projects. Our work should provide a better understanding of software project status reporting.