icon-carat-right menu search cmu-wordmark

Software Development Risk: Opportunity, Not Problem

Technical Report
This 1992 report examines problems that exist in software development today and present the SEI's approach to turning risk into opportunity.
Publisher

Software Engineering Institute

CMU/SEI Report Number
CMU/SEI-92-TR-030

Abstract

What is risk? What is risk management? What does risk management have to do with software? Noted software expert Tom Gilb says: "If you don't actively attack the risks, they will actively attack you." 

But what does it mean to actively attack risks? We answer these questions by examining the problems that exist in software development today and presenting the SEI Risk Program approach to turning risk into opportunity. 

We begin by reviewing the fundamental concepts of risk and elaborating on how these basic concepts apply to the development of large, software-intensive systems. We then develop our strategy for seeing a systematic approach to risk management in software development be routinely practiced. 

There are two key activities we are using to implement our strategy. The first is our risk management paradigm. The paradigm defines a set of continuous activities that must be undertaken to resolve technical risk in a systematic and structured way. The second is our risk assessment process for collaborating with clients to identify their technical risks.  

We end with our ultimate goal: establishing an effective risk management ethic as standard practice in the software engineering industry.

Cite This Technical Report

Van Scoy, R. (1992, September 1). Software Development Risk: Opportunity, Not Problem. (Technical Report CMU/SEI-92-TR-030). Retrieved November 24, 2024, from https://insights.sei.cmu.edu/library/software-development-risk-opportunity-not-problem/.

@techreport{van_scoy_1992,
author={Van Scoy, Roger},
title={Software Development Risk: Opportunity, Not Problem},
month={{Sep},
year={{1992},
number={{CMU/SEI-92-TR-030},
howpublished={Carnegie Mellon University, Software Engineering Institute's Digital Library},
url={https://insights.sei.cmu.edu/library/software-development-risk-opportunity-not-problem/},
note={Accessed: 2024-Nov-24}
}

Van Scoy, Roger. "Software Development Risk: Opportunity, Not Problem." (CMU/SEI-92-TR-030). Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, September 1, 1992. https://insights.sei.cmu.edu/library/software-development-risk-opportunity-not-problem/.

R. Van Scoy, "Software Development Risk: Opportunity, Not Problem," Carnegie Mellon University, Software Engineering Institute's Digital Library. Software Engineering Institute, Technical Report CMU/SEI-92-TR-030, 1-Sep-1992 [Online]. Available: https://insights.sei.cmu.edu/library/software-development-risk-opportunity-not-problem/. [Accessed: 24-Nov-2024].

Van Scoy, Roger. "Software Development Risk: Opportunity, Not Problem." (Technical Report CMU/SEI-92-TR-030). Carnegie Mellon University, Software Engineering Institute's Digital Library, Software Engineering Institute, 1 Sep. 1992. https://insights.sei.cmu.edu/library/software-development-risk-opportunity-not-problem/. Accessed 24 Nov. 2024.

Van Scoy, Roger. Software Development Risk: Opportunity, Not Problem. CMU/SEI-92-TR-030. Software Engineering Institute. 1992. https://insights.sei.cmu.edu/library/software-development-risk-opportunity-not-problem/