Pragmatic Agilist

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...

I was speaking with a group of fellow would-be agile change agents last week, and one of us described "the opposite of agile" as "mortgage driven development."  Of course I found this funny and apt, and I looked it up online, where I found Jason Gorman's tongue in cheek manifesto for the MDD movement online: We are uncovering better ways of making money from software by doing it and hindering others from doing it. Through this work we have come to value: Timesheets and invoices over principles and ethics Unmaintainable software over clean code Contract renegotiation over a barrel Unlimited overtime over a sustainable pace Contracts that fall outside of IR35 over and over again But as I reflected on the matter, I realized I would prefer to describe the above manifesto in terms of "Marauder Driven Development" instead, if we must have a straw man abbreviated to MDD.  Our enemy isn't mortgage-holders with their desire to maintain a sta...