Kent Beck, et. al.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly (Beck et. al., “The Agile Manifesto,” 2001).
Eric Raymond
“Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone.” (Raymond, “The Cathedral and the Bazaar,” 2000)
“Release early. Release often. And listen to your customers.” (Raymond, “The Cathedral and the Bazaar,” 2000)
“Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.” (Raymond, “The Cathedral and the Bazaar,” 2000)
“When you lose interest in a program, your last duty to it is to hand it off to a competent successor.” (Raymond, “The Cathedral and the Bazaar,” 2000)
“Every good work of software starts by scratching a developer’s personal itch.” (Raymond, “The Cathedral and the Bazaar,” 2000)
“The next best thing to having good ideas is recognizing good ideas from your users. Sometimes the latter is better.” (Raymond, “The Cathedral and the Bazaar,” 2000)
James Surowiecki
“Information cascades” are what occurs when an initial decision is made by a few people, and then more or less accepted uncritically by more and more people.” (Surowiecki, “The Wisdom of Crowds,” 2005)
Fredrick Brooks
“Plan to throw one away; you will, anyhow.” (Brooks, “The Mythical Man-Month,” 1982)
Opening My Masters 