Driven Development

Why and how does software get made? While Nicholas and I were pondering ways to make program development easier, I decided to waste some time and search google for "* driven development". Here are the results, sorted into some pretty arbitrary categories:

development driven by your desires:
resume driven development
curiosity driven development
employee driven development
brain driven development
asshole driven development (based on avoiding suffering, assuming that someone else is the asshole)

specification:
test driven development (evolving specifications)
model driven development (executable specification)
feature driven development
example driven development
documentation driven development (non-executable specifications)
storytest driven development
dialogue driven development
annotation driven development
bug driven development (implicit specification)
behavior driven development (implicit specification)
interface driven development
specification driven development
exception driven development
user-guide driven development


outside desires:
dilemma driven development
turmoil driven development
demand driven development
community driven development
task driven development
mission driven development
omoiyari driven development (Japanese for "what other people are thinking")

beverage:
tea driven development
coffee driven development

ill defined:
anecdote driven development
neo-liberal driven development
reality driven development
secret driven development
worksheet driven development
rup driven development
ontology driven development
pattern generator driven development
pajama driven development - working remotely
platform driven development
semantics driven development
diary driven development