Even Agile advocates some analysis and design over simply rushing to coding. The key is to not generate mountains of documentation, but just enough to get feel for what you need to do AND don't design and build anything that isn't needed.

You can start here http://en.wikipedia.org/wiki/Scrum_%28development%29

>Hi all -
>
>Of course when I need some articles that discuss the above I can't find them. Anyone have good links to sites that discuss the virtues, cost-savings, lower-bug rate, etc. of not rushing through the analysis and design phases and just "coding right away"? Would love sites that discuss this from both a technical (better class design allows use in a larger number of applications without change) and business (cost-savings, better user-experiences, etc.) perspective.
>
>Thanks!