Agile PracticesThis morning I participated in an Agile Software Development panel. It was early but even through my fog of only a couple (as in 2) hours of sleep, I think some interesting thoughts and comments surfaced.

One thing that struck me was the discussion about the role of software testing within Agile practices. ‘Typically’ you’d want your testers living side by side with your developers. Even better, you’d want them working with the Product Owner to verify that the story was implemented satisfactorily. There was some discussion/disagreement about the scope that Test Drive Development can realistically cover and the need for formalized acceptance testing. A few people chimed in that although software development practices have evolved, testing/QA/SV practices have failed to keep up to the pace of change.

Around this point, Paul Carvalho (a former senior tester of mine), theorized that we needed to get testers more comfortable with Agile practices like Exploratory Testing (ET) and even more importantly, developers needed to be comfortable with ET. My experience has been that developers’ initial reaction (mine included) to ET is pretty similar to  management’s first reaction to Agile. And while Paul eventually won me over with ET, I would’ve loved the kind comfort of a test plan in the early days.

Paul feels we can overcome the resistance to change through discussion and education but I’m curious -  is Exploratory Testing testing the Agile testing method of choice? What resistance have people felt to implementing Exploratory Testing?