Anyway, I stumbled on this Quote on the C2 Wki:
What really matters?If I had my way these four points would be prominently displayed in every IT Department out there.
Software is too damned hard to spend time on things that don't matter. So, starting over from scratch, what are we absolutely certain matters?
1. Coding. At the end of the day, if the program doesn't run and make money for the client, you haven't done anything.
2. Testing. You have to know when you're done. The tests tell you this. If you're smart, you'll write them first so you'll know the instant you're done. Otherwise, you're stuck thinking you maybe might be done, but knowing you're probably not, but you're not sure how close you are.
3. Listening. You have to learn what the problem is in the first place, then you have to learn what numbers to put in the tests. You probably won't know this yourself, so you have to get good at listening to clients - users, managers, and business people.
4. Designing. You have to take what your program tells you about how it wants to be structured and feed it back into the program. Otherwise, you'll sink under the weight of your own guesses.
Listening, Testing, Coding, Designing. That's all there is to software. Anyone who tells you different is selling something.
-- KentBeck, author of ExtremeProgrammingExplained