The community isn't nearly as afraid as it thinks it is.

The business changes. The technology changes. The team changes. The team members change. The problem isn't change, per se, because change is going to happen; the problem, rather, is the inability to cope with change when it comes.

I tell people to start implementing when they are pretty sure there aren't more important stories out there. An iteration's worth of data is worth months of speculation.

I mean, source code in files; how quaint, how seventies!

The system metaphor is a story that everyone--customers, programmers, and managers--can tell about how the system works.

Learning research tells us that the time lag from experiment to feedback is critical.

Responsible Development is the style of development I aspire to now. It can be summarized by answering the question, How would I develop if it were my money? I'm amazed how many theoretical arguments evaporate when faced with this question.