A framework for assessing the reliability of software project status reports

EMJ - Engineering Management Journal

Volumn 14, Issue 2, 2002, Pages 20-26

  Snow, Andrew P ^a   Keil, Mark ^b  

^a OHIO UNIVERSITY   (United States)

^b GEORGIA STATE UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

INFORMATION MANAGEMENT; MANAGERS; MATHEMATICAL MODELS; PROBABILITY; RISK MANAGEMENT; SOCIETIES AND INSTITUTIONS; SOFTWARE ENGINEERING;

PROJECT MANAGERS;

PROJECT MANAGEMENT;

EID: 0036613356     PISSN: 10429247     EISSN: None     Source Type: Journal    
DOI: 10.1080/10429247.2002.11415158     Document Type: Article

References (21)

1. Abdcl-Hamid, Tarek K., and Stuart E. Madnick(1991), Software Project Dynamics: An Integrated Approach, Prentice Hall.
2. Abdel-Hamid, Tarek K., "Understanding the '90% Syndrome' in Software Project Management: A Simulation-Based Case Study," The Journal of Systems and Software 8(4) (1988), pp. 319-330.
3. Abdel-Hamid, Tarek K., "Investigating the Cost/Schedule Trade-Off in Software Development,(1990) "IEEE Software 7(1), pp. 97-105.
4. Abdel-Hamid, Tarek K., and Stuart E. Madnick, "Lessons Learned from Modeling the Dynamics of Software Development," (1989) Communications of the ACM 32(12), pp. 1426-1438.
5. Abdel-Hamid, Tarek K., Kishore Sengupta, and D. Ronan, "Software Project Control: An Experimental Investigation of Judgment with Fallible Information," 79(6)(1993) IEEE Transactions on Software Engineering, pp.603-612.
6. Boebert, W.E., "Software Quality Through Software Management," Software Quality Management, J. D. Cooperand M. J. Fisher (eds.), Petrocell i Books (1979).
7. Brooks, Frederick P., (1975) The Mythical Man-Month: Essays on Software Engineering, Addison-Wesley.
8. Brown, Carol V. "Advantage 2000 at Owens Coming," (1998) In Managing Information Technology, E.W. Martin, C.V. Brown, D.W. DeHayes, J.A. Hoffer and W.C. Perkins (eds.), Prentice Hall, pp. 640-658.
9. Burris, Rick, "Get the Green Light!" 7(2)(1994) The Wight Line, pp. 6-8.
10. Chen, Mark T., "An Innovative Project Report," 34:4(1996) Cost Engineering, pp. 41-45.
11. Coulter, Carleton, "Multiproject Management and Control," 32 10(1990) Cost Engineering, pp. 19-24.
12. DeMarco, Tom, (1982) Controlling Software Projects, Yourdon Press.
13. Hamming, Richard W., (1986) Coding and Information Theory, Prentice Hall.
14. Jones, Capers, (1994) Assessment and Control of Software Risks,. Prentice-Hall
15. Keil, Mark, "Pulling the Plug: Software Project Management and the Problem of Project Escalation," MIS Quarterly 19(4) (December 1995), pp. 421-447.
16. Keil, Mark, and Daniel Robey, "Turning Around Troubled Software Projects: An Exploratory Study of the Deescalation of Commitment to Failing Courses of Action," (1999) Journal of Management Information Systems 15(4), pp. 63-87.
17. Oz, Effy, "When Professional Standards are Lax: The CONFIRM Failure and Its Lessons," (1994) Communications of the ACM 37(10), pp. 29-36.
18. Sauer, Chris, Li Liu, and K. Johnston "Enterprise-Level Project Management Capabilities: A Comparison of the Construction and IT Services Industries," (1999) Proceedings of the International Conference on Information Systems (ICIS), pp. 440-445.
19. Snow, Andrew P., and Mark Keil, "The Challenge of Accurate Project Status Reporting: A Two Stage Model Incorporating Status Errors and Reporting Bias," (2001) Proceedings of the 34th Annual Hawaii International Conference on System Sciences (HICSS-34), pp. 1-10.
20. Zerega, Blaise, (1998) "Sears Tackles Y2K Compliance With Partners," Infoworld, 20:29, p. 16.
21. Zmud, Robert W., (1980) "Management of Large Software Efforts," MIS Quarterly 4:2, pp. 45-55.