“The new concept of Extreme Programming (XP) is gaining more and more acceptance, partially because it is controversial, but primarily because it is particularly well-suited to help the small software development team succeed… XP is controversial, many software development sacred cows don't make the cut in XP; it forces practitioners to take a fresh look at how software is developed.”

—  Kent Beck

Abstract
Extreme Programming Explained (2000)

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 "The new concept of Extreme Programming (XP) is gaining more and more acceptance, partially because it is controversial,…" by Kent Beck?
Kent Beck photo
Kent Beck 13
software engineer 1961

Related quotes

Barry Boehm photo

“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

“Software engineering concerns methods and techniques to develop large software systems. The engineering metaphor is used to emphasize a systematic approach to develop systems that satisfy organizational requirements and constraints.”

Hans van Vliet (1949) Dutch computer scientist

Source: Software Engineering: Principles and Practice, 2007, p. 2

Barry Boehm photo

“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)

“The growing complexity of software is the motivation behind work on industrializing software development. In particular, current research in the area of model driven engineering (MDE) is primarily concerned with reducing the gap between problem and software implementation domains through the use of technologies that support systematic transformation of problem-level abstractions to software implementations. The complexity of bridging the gap is tackled through the use of models that describe complex systems at multiple levels of abstraction and from a variety of perspectives, and through automated support for transforming and analyzing models. In the MDE vision of software development, models are the primary artifacts of development and developers rely on computer-based technologies to transform models to running systems.”

Bernhard Rumpe (1967) German computer scientist

Source: Model-driven development of complex software: A research roadmap (2007), p. 37

Lawrence Lessig photo

“In the context of software development, where you have sequential and complementary developments, patents create an extraordinarily damaging influence on innovation and on the process of developing and bringing new ideas to market.”

Lawrence Lessig (1961) American academic, political activist.

"Code + Law: An Interview with Lawrence Lessig" at O'Reilly P2P (29 January 2001)(29 January 2001)
Context: Our problem is that lawyers have taught us that there is only one kind of economic market for innovation out there and it is this kind of isolated inventor who comes up with an idea and then needs to be protected. That is a good picture of maybe what pharmaceutical industry does. It's a bad picture of what goes on, for example, in the context of software development, in particular. In the context of software development, where you have sequential and complementary developments, patents create an extraordinarily damaging influence on innovation and on the process of developing and bringing new ideas to market. So the particular mistake that lawyers have compounded is the unwillingness to discriminate among different kinds of innovation.
We really need to think quite pragmatically about whether intellectual property is helping or hurting, and if you can't show it's going to help, then there is no reason to issue this government-backed monopoly.

Grady Booch photo

“The amateur software engineer is always in search of magic, some sensational method or tool whose application promises to render software development trivial. It is the mark of the professional software engineer to know that no such panacea exist.”

Grady Booch (1955) American software engineer

Grady Booch, ‎Robert A. Maksimchuk, ‎Michael W. Engle (2007) Object-Oriented Analysis and Design with Applications Chapter 6.

“Walking on water and developing software from a specification are easy if both are frozen.”

Edward V. Berard

Source: Essays on object-oriented software engineering (1993), p. 46

Richard Stallman photo

“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)

Barry Boehm photo

“Software Engineering Economics is an invaluable guide to determining software costs, applying the fundamental concepts of microeconomics to software engineering, and utilizing economic analysis in software engineering decision making.”

Barry Boehm (1935) American software engineer

Barry W. Boehm (1981) Software engineering economics. Abstract.

“In all engineering disciplines nowadays, software engineering excluded, there exists an established engineering process to develop a system, which is accompanied by a number of suited modeling description techniques. Software engineering, being a rather new field, has not as yet established any clear methodical guidance or a fully standardized modeling notation.”

Bernhard Rumpe (1967) German computer scientist

Source: Executable Modeling with UML. A vision or a Nightmare (2002), p. 697

Related topics