Disincentives for communicating risk: A risk paradox

Information and Software Technology

Volumn 41, Issue 7, 1999, Pages 403-411

  Schmidt, Cameron ^a   Dart, Philip ^a   Johnston, Lorraine ^a   Sterling, Leon ^a   Thorne, Peter ^a  

^a UNIVERSITY OF MELBOURNE   (Australia)

Author keywords

[No Author keywords available]

Indexed keywords

PROJECT MANAGEMENT; RISK ASSESSMENT; RISK MANAGEMENT;

SOFTWARE PROCUREMENT;

SOFTWARE ENGINEERING;

EID: 0032624339     PISSN: 09505849     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0950-5849(99)00011-7     Document Type: Article

References (20)

1. Down A., Coleman M., Absolon P. Risk Management for Software Projects. 1994;McGraw Hill, NY.
2. Gilb T. Principles of Software Engineering Management. 1988;Addison-Wesley, Reading, MA.
3. R.P. Higuera, A.J. Dorofee, J.A. Walker, R.C. Williams, Team risk management: a new model for customer-supplier relationships, Technical Report CMU-SEI-94-SR-5, Software Engineering Institute, Carnegie Mellon University, July 1994.
4. Charette R.N. Engineering Risk Analysis and Management. 1989;McGraw-Hill, New York.
5. Grey S. Practical Risk Assessment for Project Management. Wiley Series in Software Engineering Practice. 1995;Wiley, New York.
6. Hall E.M. Managing Risk: Methods for Software Systems Development. SEI Series in Software Engineering. 1998;Addison-Wesley, Reading, MA.
7. Jones C. Assessment and Control of Software Risks. 1994;Prentice Hall, Englewood Cliffs, NJ.
8. M. Myerson, Risk Management Processes for Software Engineering Models. Artech House, 1997.
9. Ould M.A. Strategies for Software Engineering: The Management of Risk and Quality. Software Engineering Series. 1990;Wiley, New York.
10. Boehm B.W. Software risk management: principles and practices. IEEE Software. January, 1991;32-41.
11. Boehm B.W., DeMarco T. Software risk management (guest editors' introduction). IEEE Software. May/June, 1997;17-19.
12. Marciniak J.J., Reifer D.J. Software Acquisition Management: Managing the Acquisition of Custom Software Systems. 1990;Wiley, New York.
13. Keil M., Cule P.E., Lyytinen K., Schmidt R.C. A framework for identifying software project risks. Communications of the ACM. 41:(11):1998;76-83.
14. Chittister C., Haimes Y.Y. Risk associated with software development: A holistic framework for assessment and management. IEEE Transactions on Systems, Man and Cybernetics. 23:(3):1993;710-723.
15. Chittister C., Haimes Y.Y. Assessment and management of software technical risk. IEEE Transactions on Systems, Man and Cybernetics. 24:(2):1994;187-202.
16. A.J. Dorofee, J.A. Walker, C.J. Albert, R.P. Higuera, R.L. Murphy, R.C. Williams, Continuous Risk Management Guidebook, Carnegie Mellon University, Pittsburgh, PA, 1996.
17. Karolak D.W. Software Engineering Risk Management. 1996;IEEE Computer Society Press, Los Alamitos, CA.
18. R.P. Higuera, D.P. Gulch, A.J. Dorofee, R.L. Murphy, J.A. Walker, R.C. Williams, An introduction to team risk management, Technical Report CMU-SEI-94-SR-1, Software Engineering Institute, Carnegie Mellon University, May 1994.
19. United States Department of Defense, Department of Defense Regulation 5000.2-R: Mandatory Procedures for Major Defense Acquisition Programs and Major Automated Information Systems Acquisition Programs, March 1996.
20. United States Department of Defense, Department of Defense Directive 5000.1: Defense Acquisition, March 1996.