Adopting automation tools can be a big decision. When it comes to test automation, it’s critical to incorporate an integrated test automation plan instead of piling together a mishmash of unrelated tools with the hope to create some taped together mess of a plan.

Too often, test-driven development still initially focuses on coding aspects, not testing. The first step in a test-driven approach has to be writing effective tests. It's not enough to simply ensure good coverage; effective tests should also confirm that decisions made in the code work correctly.

Of course it's important to work efficiently, without wasting time, money, or energy. But working effectively is just as important. Agile cycles between creating, testing, and getting feedback, allowing us to work in small chunks and make sure what we're producing has the most value. That's effective.