Project risk management: Lessons learned from software development environment

Technovation

Volumn 24, Issue 11, 2004, Pages 915-920

  Kwak, Young Hoon ^a   Stoddard, Jared ^b  

^a GEORGE WASHINGTON UNIVERSITY   (United States)

^b AGILENT TECHNOLOGIES   (United States)

Author keywords

Lessons learned; Organization; Project management; Risk management; Software development; Technology management

Indexed keywords

COMPUTER SCIENCE; INFORMATION TECHNOLOGY; PROJECT MANAGEMENT; SCHEDULING; SOCIETIES AND INSTITUTIONS; SOFTWARE ENGINEERING;

LESSONS LEARNED; SOFTWARE PROJECTS; TECHNOLOGY MANAGEMENT;

RISK MANAGEMENT;

EID: 7444231051     PISSN: 01664972     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0166-4972(03)00033-6     Document Type: Article

References (24)

1. Boehm B.W. Software risk management principles and practices. IEEE Software. 8:(1):1991;32-41.
2. Boehm B.W., DeMarco T. Software risk management. IEEE Software. 14:(3):1997;17-19.
3. Boehm B., Port D. Educating software engineering students to manage risk. Proceedings of the 23rd International Conference on Software Engineering: 2001;591-600.
4. Conrow E.H. Effective risk management: some keys to success. 2000;American Institute of Aeronautics and Astronautics.
5. Fuller A., Croll P., Di L. A new approach to teaching software risk management with case studies. Proceedings of the 15th conference on Software Engineering Education and Training: 2002;215-222.
6. Gemmer A. Risk management: moving beyond process. Computer. 30:(5):1997;33-43.
7. Gluch D.P., Dorofee A.J., Hubard E.A., Travalent J.J. A collaboration in implementing team risk management. Technical Report, CMU/SEI-95-TR-016. 1996;Software Engineering Institute.
8. Hall D.C. Development program risk management: a case study. 2001 INCOSE Proceedings of a Symposium on Risk Management:2001;3.
9. Hall E.M. Managing Risk: Methods for Software Systems Development. 1998;Addison-Wesley.
10. Higuera R.P., Gluch D.P., Dorofee A.J., Murphy R.L., Walker J.A., Williams R.C. An introduction to team risk management. Special Report, CMU/SEI-94-SR-1. 1994;Software Engineering Institute.
11. Jiang J.J., Klein G. Risks to different aspects of system success. Information and Management. 36:(5):1999;263-272.
12. Jiang J.J., Klein G., Discenza R. Information system success as impacted by risks and development strategies. IEEE Transactions on Engineering Management. 48:(1):2001;46-55.
13. Jiang J.J., Klein G., Means T.L. Project risk impact on software development team performance. Project Management Journal. 31:(4):2000;19-26.
14. Jones C. Minimizing the risks of software development. Cutter IT Journal. 11:(6):1998;13-21.
15. Jones G.F. What is different about it risks. 2001 INCOSE Proceedings of a Symposium on Risk Management: 2001;3.
16. Keshlaf A.A., Hashim K. A model and prototype tool to manage software risks. Proceedings of First Asia-Pacific Conference on Quality Software: 2000;297-305.
17. Klein S.A. Putting methodology in perspective from a project risk viewpoint. IEEE Power Engineering Society 1999 Winter Meeting, vol. 1: 1998;362-365.
18. Kwak Y.H., Ibbs C.W. Calculating project management's return on investment. Project Management Journal. 31:(2):2000;38-47.
19. PMI, 2001. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) 2000 Edition, Project Management Institute Publications.
20. Roberts B.B. Lessons-learned: round 2. 2001 INCOSE Proceedings of a Symposium on Risk Management: 2001;3.
21. Schmidt R., Lyytinen K., Keil M., Cule P. Identifying software project risks: an international Delphi study. Journal of Management Information Systems. 17:(4):2001;5-36.
22. SEI, 2001. Carnegie Mellon SEI Annual Report FY2001.
23. van Genuchten M. Why is software late? An empirical study of reasons for delay in software development. IEEE Transactions on Software Engineering. 17:(6):1991;582-590.
24. Yacoub S.M., Ammar H.H. A methodology for architecture-level reliability risk analysis. IEEE Transactions on Software Engineering. 28:(6):2002;529-547.