Abstract
This paper presents the DNV approach to project risk management. It enhances most of the known approaches in two ways. First, it adds an initiation phase at the start of the process, before risk identification is started, in which the project objectives are defined. Knowing the project objectives it is much easier to identify risks and link them to the project objectives they have an impact on. The second aspect is the possibility of creating a risk model that includes all risks and their impact on various objectives, capturing their complex interaction. This way, the total risk picture of the project can be modelled and estimated, and uncertainties that affect more than one objective (often favourable against one objective, unfavourable against another) can be handled correctly. The presented (generic) ideas enhance and enrich currently available approaches for software project risk mangement.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
References
Boehm, B.W.: Tutorial: Software risk management. IEEE Computer Society Press, Washington (1989)
Boehm, B.W.: Software risk management: Principles and practices. IEEE Software 8(1), 32–41 (1991)
Boehm, B.W., DeMarco, T.: Software risk management. IEEE Software 14(3), 17–19 (1997)
Carr, M.J.: Risk management not be for everyone. IEEE Software 3, 21–24 (1997)
Charette, R.N.: Software engineering risk analysis and management. McGraw- Hill software engineering series. Intertext Publications / McGraw-Hill Book Co. (1989). lc89083763 R.N. Charette
Coletta, A.: The SPICE project: An international standard for software process assessment, improvement and capability determination. LNCS, vol. 926 (1995)
Dorofee, A.J., Walker, J.A., Alberts, C.J., Higuera, R.P., Murphy, R.L., Williams, R.C.: Continuous Risk Management Guidebook. Software Engineering Institute, Carnegie Mellom University (1996)
Glass, R.L.: Software Runaways. In: Monumental Software Disasters. Prentice Hall, Englewood Cliffs (1997)
Hall, E.M.: Managing Risk: methods for software systems development. SEI Series in Software Engineering. Addison Wesley Longman, Inc., Reading (1998)
International Organization for Standardization. ISO 9000: Quality management and quality assurance standards; Part 3: Guidelines for the application of ISO 9001 to the development, supply and maintenance of software, Geneva, Switzerland (1991)
Jones, C.: Patterns of Software Systems Failure and Success. International Thomson Computer Press (1996)
Karolak, D.W.: Software Engineering Risk Management. IEEE Computer Society Press, Los Alamitos (1996)
KPMG. What went wrong? unsuccessful information on technology projects (1997)
Kuvaja, P.: BOOTSTRAP: A software process assessment and improvement methodology. LNCS, vol. 926 (1995)
Paulk How, M.C.: ISO 9001 compares with the CMM. IEEE Software 12(1), 74–83 (1995)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2000 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Wieland, P., Høgberg, F., Strømseng, K. (2000). Enhancements in Software Project Risk Management. In: Keller, H.B., Plödereder, E. (eds) Reliable Software Technologies Ada-Europe 2000. Ada-Europe 2000. Lecture Notes in Computer Science, vol 1845. Springer, Berlin, Heidelberg. https://doi.org/10.1007/10722060_16
Download citation
DOI: https://doi.org/10.1007/10722060_16
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-67669-0
Online ISBN: 978-3-540-45098-6
eBook Packages: Springer Book Archive