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

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.

Sometimes the problem has to mature before the solution can mature.

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.

Of the four project development variables - scope, cost, time and quality - quality isn't really a free variable. The only possible values are "excellent" and "insanely excellent", depending on whether lives are at stake.

I don't like the feeling, but I've got to say that a little fear makes me a more focused, more responsible programmer.

If testing costs more than not testing, then don't test.