Experiences in improving risk management processes using the concepts of the Riskit method

ABSTRACT

This paper describes experiences from two organizations that have used the Riskit method for risk management in their software projects. This paper presents the Riskit method, the organizations involved, case study designs, and findings from case studies. We focus on the experiences and insights gained through the application of the method in industrial context and propose some general conclusions based on the case studies.

REFERENCES

• 1: Anonymous, Risk Assessment Techniques. In: Defense Systems Management College Handbook, Anonymous Defense Systems Management College, 1983. pp. iv-l--25, F-l--13.
• 2: V.R. Basili, G. Caldiera, and H.D. Rombach. Goal Question Metric Paradigm. In: Encyclopedia of Sofware Engineering, ed. J.J. Marciniak. New York: John Wiley & Sons, 1994. pp. 528-532.
• 3: P.L. Bernstein. Against the Gods, New York: John Wiley &Sons, 1996.
• 4: Barry W. Boehm, Software Engineering Economics, Prentice Hall PTR, Upper Saddle River, NJ, 1981
• 5: Barry W. Boehm, Software risk management, IEEE Press, Piscataway, NJ, 1989
• 6: B.W. Boehm and Bose P., A Collaborative Spiral Software Process Model Based on Theory W 1994. Proceedings of the 3rd International Conference on the Software Process. IEEE Computer Society. Washington, DC.
• 7: M.A. Caplan, Risk Management in Practice 1994. Proceedings of the Third SE1 Conference on Software Risk Management. SEI. Pittsburgh, PA.
• 8: M.J. Cat-r, S.L. Konda, LA. Monarch, F.C. Ulrlch, and C.F. Walker. Taxonomy-Based Risk Identification, SEI Technical Report SEI-93-TR-006, Pittsburgh, PA: Software Engineering Institute, 1993.
• 9: Robert N. Charette, Software engineering risk analysis and management, McGraw-Hill, Inc., New York, NY, 1989
• 10: A.J. Dorofee, J.A. Walker, C.J. Alberts, R.P. Higuera, T.J. Murray, and R.J. Williams. Continuous Risk Management Guidebook, Pittsburgh, PA: Software Engineering Institute, 1996.
• 11: H. Englund, A Case Study to Explore Risk Management Methods 1997. Kunglika Tekniska Hogskolan, Stockholm, Sweden. Masters thesis.
• 12: Richard Fairley, Risk Management for Software Projects, IEEE Software, v.11 n.3, p.57-67, May 1994 [doi>10.1109/52.281716]
• 13: P.H. Feiler and W.S. Humphrey, Software Process Development and Enactment: Concepts and Definitions pp. 2840.1993. Proceedings of the 2nd International Conference on the Software Process, Berlin 1993. IEEE Computer Society Press. Los Alamitos, CA.
• 14: Simon French, Decision theory: an introduction to the mathematics of rationality, Halsted Press, New York, NY, 1986
• 15: M. Friedman and L.J. Savage, The Utility Analysis of Choices Involving Risk Journal of Political Economy, vol. 56, pp. 279-304.1948.
• 16: A. Gemmer and P. Koch, Rockwell Case Studies in Risk Management 1994. Proceedings of the Third SE1 Conference on Software Risk Management. SEI. Pittsburgh, PA.
• 17: J.C. Groth, Common-sense Risk Assessment Management Decision, vol. 30, pp. 10-16. 1992.
• 18: IEEE, Managing Risk IEEE Software, vol. 14, no. 3, 1997.
• 19: J. Kontio, The Riskit Method for Software Risk Management, version 1.00 CS-TR-3782 / UMIACS-TR- 97-38, 1997. Computer Science Technical Reports. University of Maryland. College Park, MD.
• 20: J. Kontio and V.R. Basili, Risk Knowledge Capture in the Riskit Method 1996. Proceedings of the 21st Software Engineering Workshop. NASA. Greenbelt, Maryland.
• 21: J. Kontio and V.R. Basili, Empirical Evaluation of a Risk Management Method 1997. Proceedings of the SE1 Conference on Risk Management. Software Engineering Institute. Pittsburgh, PA.
• 22: J. Kontio, H. Englund, and V.R. Basili, Experiences from an Exploratory Case Study with a Software Risk Management Method CS-TR-3705, 1996. Computer Science Technical Reports. University of Maryland. College Park, Maryland.
• 23: J.V. Michaels. Technical Risk Management, Upper Saddle River, NJ: Prentice Hall, 1996.
• 24: G. Pandelios, Software Risk Evaluation and Team Risk Management 1996. Tutorial Presentations at the 1996 SEPG Conference. Software Engineering Institute. Pittsburgh, PA.
• 25: J.L. Simon. Basic Research Methods in Social Science, New York: Random House, 1969. pp. -525
• 26: Visio Corp., VISIO Technical, ver. 4.0, rel. 1995. Visio Corporation. IBM compatible PC. MS-Windows, Windows 95.
• 27: R.K. Yin. Case Study Research: Design and Methods, Thousand Oaks, CA: SAGE Publications, 1994.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

Additional Classification:
  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

General Terms:
Design, Management, Measurement, Performance, Reliability, Theory

Keywords:
empirical study, project management, risk management