Agile Testing: A Practical Guide for Testers and Agile Teams

Some teams prefer to write testing tasks directly on the development task cards. It’s a simple solution, because the task is obviously not “done” until the testing is finished. You’re trying to avoid a “mini-waterfall” approach where testing is done last, and the programmer feels she is done because she “sent the story to QA.” See what approach works best for your team.

If you’re using a third-party product as part of your solution, you might assume it has been tested, but that might be a poor assumption.

Remember that when people panic, they go back to their old habits, even though those habits didn’t work.