“Like many fields in their early stages, the software field has had its share of project disasters: the software equivalents of Beauvais Cathedral, the S. S. Titanic, and the "Galloping Gertie" Tacoma Narrows Bridge. The frequency of these disaster projects is a serious concern: a recent survey of 600 firms indicated that 35% of them had at least one "runaway' software project.”

Source: Software risk management: principles and practices (1991), p. 32

Adopted from Wikiquote. Last update June 3, 2021. History

Help us to complete the source, original and additional information

Do you have more details about the quote "Like many fields in their early stages, the software field has had its share of project disasters: the software equival…" by Barry Boehm?

Barry Boehm18

American software engineer 1935

Related quotes

“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 (1935) American software engineer

Source: Software risk management: principles and practices (1991), p. 32

“Before Paul and I started the company, we had been involved in some large-scale software projects that were real disasters. They just kept pouring people in, and nobody knew how they were going to stabilize the project. We swore to ourselves that we would do better.”

Bill Gates (1955) American business magnate and philanthropist

Interview from Programmers at Work (1986)

“Brooks's Law: Adding manpower to a late software project makes it later.”

Fred Brooks (1931) American computer scientist

Page 25 (italics in source, bold added).
The Mythical Man-Month: Essays on Software Engineering (1975, 1995)

“Poor management can increase software costs more rapidly than any other factor. Particularly on large projects, each of the following mismanagement actions has often been responsible for doubling software development costs.”

Barry Boehm (1935) American software engineer

Barry Boehm (1981) as cited in: Tyson Gill (2002) Planning Smarter: Creating Blueprint-Quality Software Specifications. p. 14

“A little retrospection shows that although many fine, useful software systems have been designed by committees and built as part of multipart projects, those software systems that have excited passionate fans are those that are the products of one or a few designing minds, great designers.”

Fred Brooks No Silver Bullet

Page 202.
No Silver Bullet (1986)

“Success in all types of organization depends increasingly on the development of customized software solutions, yet more than half of software projects now in the works will exceed both their schedules and their budgets by more than 50%.”

Barry Boehm (1935) American software engineer

Abstract.
Software Cost Estimation with Cocomo II with Cdrom (2000)

“In fact, my main conclusion after spending ten years of my life working on the TEX project is that software is hard. It’s harder than anything else I’ve ever had to do.”

Donald Ervin Knuth (1938) American computer scientist

[Knuth, Donald, 2002, All Questions Answered, Notices of the AMS, 49, 3, 320, http://www.ams.org/notices/200203/fea-knuth.pdf, PDF]

“Software people seem to have a love-hate relationship with metrics. On one hand, they despise and distrust anything that sounds or looks like a measurement. They are quick to point out the "flaws" in the arguments of anyone who talks about measuring software products, software processes, and (especially) software people. On the other hand, these same people seem to have no problems identifying which programming language is the best, the stupid things that managers do to "ruin" projects, and who's methodology works in what situations.”

Edward V. Berard

Edward V. Berard (1998) " Metrics for object-oriented software engineering http://www.ipipan.gda.pl/~marek/objects/TOA/moose.html." The Object Agency, Inc.

“The APT and CAD Projects had one Air Force sponsorship, but it was actually a combination of about five or six projects, all going in parallel on both hardware and software matters, and I couldn't keep track of things, so I would take Polaroid pictures of the blackboard and then say what we had talked about into my dictating machine and my secretary would type it up.”

Douglas T. Ross (1929–2007) American computer scientist

Source: Retrospectives : The Early Years in Computer Graphics at at MIT, Lincoln Lab and Harvard (1989), p. 26.

“Over the years, many companies have contributed to free software development. Some of these companies primarily developed non-free software, but the two activities were separate; thus, we could ignore their non-free products, and work with them on free software projects. Then we could honestly thank them afterward for their free software contributions, without talking about the rest of what they did.
We cannot do the same with these new companies, because they won't let us. These companies actively invite the public to lump all their activities together; they want us to regard their non-free software as favorably as we would regard a real contribution, although it is not one. They present themselves as "open source companies," hoping that we will get a warm fuzzy feeling about them, and that we will be fuzzy-minded in applying it.
This manipulative practice would be no less harmful if it were done using the term "free software."”

Richard Stallman (1953) American software freedom activist, short story writer and computer programmer, founder of the GNU project

But companies do not seem to use the term "free software" that way; perhaps its association with idealism makes it seem unsuitable. The term "open source" opened the door for this.
1990s, Why "Free Software" is better than "Open Source" (1998)

Help us to complete the source, original and additional information

Barry Boehm18

Related quotes

Related topics