The DOI matches its Crossref record.
Dealing with Risk: A Practical Approach
Open accessAbstract
Most software projects take place in a volatile environment in which many dangers exist that may affect the successful outcome of the project. After completion of the project an evaluation may show that many of the problems encountered during the project could have been foreseen before they actually occurred. Risk management is an approach that is aimed at predicting the occurrence of this type of problem and at taking counter measures to either prevent them from affecting the project or to soften their impact. In this paper the basic activities related to risk management are described. Furthermore a concrete method aimed at supporting risk management is presented. This method has been used successfully in practice. Some of the results obtained by using it are presented on the basis of five cases. Some conclusions are that: (1) the use of a short and structured checklist will ease identification of and discussions about risks, (2) a risk management method in which explicit use is made of a group related approach, involving all parties, will increase reliability and acceptance of the results, and (3) involvement of a neutral process risk advisor will further both the successful use of the method and the acceptance of the results.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
Risk assessment and prevention lower the likelihood of large-scale disruptions during the development of software and reduce the duration of IT projects that create software for computers.
“risk assessment and prevention lower the likelihood of large-scale disruptions during the development of software and also reduce the duration of IT projects that create software for computers (Heemstra and Kusters 1996).”
From Analysis of 105 IT Project Risks (2023) · cites this paper as Heemstra and Kusters 1996
Citations
Cites
No references could be resolved yet.
Research works printed but not linked: 8
- 10.1109/52.62930 · DOI
- Charette R.N., 1990, Application Strategies for Risk Analysis
- Heemstra F.J., 1993, Eindrapport
- Heemstra F.J., 1993, Risk Management in a governmental organisation
- Howard M., 1992, Bedrijfskunde, 64
- Rook P., 1993, Proceedings of the European Software Cost Modelling Meeting, Ivrea
- SEI, 1991, Proceedings of the SEI Software Risk Management Conference
- SEI, 1993, Proceedings of the Second SEI Conference on Software Risk
Cited by
Sorted by citations
Analysis of 105 IT Project Risks
Nikolaenko, V., & Sidorov, A. (2023) · Journal of Risk and Financial Management · doi:10.3390/jrfm16010033 · Cited by 22
Metadata
- Authors
- Heemstra, F. J., & Kusters, R. J.
- Affiliations
- The Open University (GB)
- Eindhoven University of Technology, Department of Technology Management, P.O. Box 513, 5600 MB Eindhoven, The Netherlands
- Venue
- Journal of Information Technology
- Publisher
- SAGE Publications
- Published
- 1996-12
- Volume
- 11
- Issue
- 4
- Pages
- 333-346
- ISSN
- 0268-3962 (ISSN-L)
- 1466-4437
- OpenAlex
- W1985299236
- Cited by
- 80
- References
- 0
- Citations by year
- 2025: 1 · 2024: 1 · 2023: 3 · 2022: 2 · 2020: 1 · 2019: 2 · 2018: 2 · 2016: 1 · 2015: 5 · 2014: 8 · 2013: 8 · 2012: 6
- FWCI
- 0.68
- Type
- journal article
- Language
- en
- Open access
- green
- research.tue.nl
- Locations
- Journal of Information Technology (publishedVersion)
- TU/e Research Portal (publishedVersion, other-oa)
- TU/e Research Portal (submittedVersion)
- Journal of the Association for Information Systems (submittedVersion)
- TU/e Research Portal (submittedVersion, other-oa)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Social Sciences › Decision Sciences › Management Science and Operations Research › Construction Project Management and Performance
- Social Sciences › Economics, Econometrics and Finance › Finance › Capital Investment and Risk Analysis
- Keywords
- software project risk management, risk identification, risk mitigation, risk assessment checklist, software project success
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
