An article on testing strategy for non-functional requirements that stimulated a fantastic discussion about functional vs. non-functional requirements. Great points are made both to eliminate and to highlight the distinctions. The strategy for developing a test plan is good, and worth reading alone, but this article is fun in that it went in a completely different direction with a very well informed debate.

Article compares different approaches to testing the workflow of an application - specifically a web application.  Detailed analysis of the maintenance & skill level tradeoffs for each approach.  Also touches on Selenium and Watir approaches.

Deep analysis of the tasks that must happen in an iteration - development, analysis, testing, etc.  Focus on the problems with staggering them too much, and suggestions on how to properly organize the team around those tasks.