Comment by camccann

Hmm. A solid idea, but it's important to contrast it with a less desirable, but superficially similar methodology, namely "Development Driven Development":

1. First, develop some code

2. Think about whether it solved the problem

3. If not, repeat until it does

...which I fear is a rather more common variant.