This

article makes for an interesting read, but it suffers from a common

misconception about agile methods and planning. Namely that Agile doesn’t do

planning. I’m more familiar with XP than the other agile methods, but as far as

I know, none of them claim that ‘planning doesn’t work so lets throw it out’, as

the article states. There’s even a book called “Planning Extreme Programming”,

by Kent Beck and Martin Fowler. What XP does recommend is that you should have

just enough planning/design/whatever for your specific needs. Its about

removing anything that doesn’t add value to your process.