Enthusiasm for new software capabilities is a good thing. But it needs to be tempered with a concern for early identification and resolution of a project's high-risk elements, so that people can get these resolved early and then focus their enthusiasm and energy on the positive aspects of their software product." - Meaning and context.">
p. 32
“

Most post-mortems of these software disaster projects have indicated that their problems would have been avoided or strongly reduced if there had been an explicit early concern with identifying and resolving their high-risk elements. Frequently, these projects were swept along by a tide of optimistic enthusiasm during their early phases, which caused them to miss some clear signals of high risk issues which proved to be the project's downfall later.
Enthusiasm for new software capabilities is a good thing. But it needs to be tempered with a concern for early identification and resolution of a project's high-risk elements, so that people can get these resolved early and then focus their enthusiasm and energy on the positive aspects of their software product.

— Barry Boehm

What It Means

This is a placeholder explanation generated by the low-overhead model. It interprets "Most post-mortems of these software disaster projects have indicated that their problems would have been avoided or strongly reduced if there had been an explicit early concern with identifying and resolving their high-risk elements. Frequently, these projects were swept along by a tide of optimistic enthusiasm during their early phases, which caused them to miss some clear signals of high risk issues which proved to be the project's downfall later.
Enthusiasm for new software capabilities is a good thing. But it needs to be tempered with a concern for early identification and resolution of a project's high-risk elements, so that people can get these resolved early and then focus their enthusiasm and energy on the positive aspects of their software product." in the context of "p. 32" to mean that wisdom is timeless.

Quote Image
Source: Wikiquote: "Barry Boehm" (Quotes, Software risk management: principles and practices (1991): Boehm, Barry W. "Software risk management: principles and practices." Software, IEEE 8.1 (1991): 32-41.) The 'What it means' explanation text was generated by Google Gemini Flash (accessed January 18, 2026). https://gemini.google.com/app
Barry Boehm

About Barry Boehm

Barry W. Boehm (May 16, 1935 – August 20, 2022) was an American software engineer, TRW Emeritus Professor of Software Engineering at the Computer Science Department of the University of Southern California, and known for his many contributions to software engineering.