Are you new to the testing concept, or the "quality" concept, as I've learned to describe it? I'm still learning, myself. You may have seen some previous attempts, but I'm happier now. Here's the framework I've devised most recently to help express how I think you need to design and implement agile quality tactics. Your mileage will of course vary. Experienced quality people please jump in and help me, where I've gone completely off the mark! Step 1: Know what to test. This can be a metaphysical question, but our friends at ISO have come up with a good practical starting point, code named SQuaRE: Systems and Software Quality Requirements and Evaluation, aka ISO 25010. It has 31 separate quality dimensions which roll up into seven "non-functional" categories, and one "functional" category. From http://a2build.com/architectedagile/Architected%20Agile.html?ISO25010.html There are many quibbles out there about whether...
Non-zealot reflections on real life agile leadership, management and analysis practices.