Agile and Extreme Programming rely on testing and user stories. Cycles are shorter and waste is limited. Every conversation begins with "how do we achieve the goal" and ends with "what's the proof we've achieved it?"

That's test driven development.

So, it's not simply the software we test for features and reliability. We also create tests or challenges to clearly define how each deployment is a success. If the set of tests aren't approved or passed, we don't launch. It removes most of the stress associated with typical project deployment because goals are clearly defined and checked off like a grocery list.

Moving folks to a testing culture is difficult. Test driven development is a pain until you overcome the learning curve and the tests become as natural as taking notes or writing email. It's like telling someone to swim properly in the middle of a race. If the race is the length of a home swimming pool, it's likely a waste of time.

Test driven development likely won't work with short run projects like installing a blog or building a tiny flash application. If the race is longer, like say an entire career or a business' lifetime, then it's much more practical to develop a test driven culture. Like any culture change, it requires universal adoption from the top down. If management is screaming about project delays while the adoption process is taking place, the culture shift will always find its way to the back burner. "We'll do that later," is the bane of any culture architect.