Heyhey!
Ok, tons of thoughts and ideas swimming in my head again. I've written lengthy texts about building trust, product risk analysis, cool heuristics like FPS Nausea, test cases, how to gain by losing,
gaming testers, etc. All at alpha level still. All complete s**t still. The highest priority is however the recap about my experiences at recent Rapid Testing Intensive / Critical Thinking courses, held none other than the almighty
James Bach himself.
Well, the highest priority was that. Namely somehow my approach on managing exploratory testing with QC has gotten some attention lately. Perhaps it's because I'm actually training it now, finally. Perhaps it's because I've ranted about it more in Twitter and other mediums. Or perhaps it's because factory schoolers have grown tired of me ranting about borderline philosophical things about testing and thinking like a tester, and are finally demanding something tangible to mimic.
I don't know.
The actual reason I'm writing this is firstly the interest of some of the testers I greatly respect namely
Maaret Pyhäjärvi,
Aleksis Tulonen,
Huib Schoots and
Paul Carvalho. I've managed ET and teams doing ET with QC for some time now, but I've never actually gotten any peer reviews of my actions. I've roamed relatively blindly and I hope this blog post cures that.
But secondly and no less importantly I'm hoping others will get ideas how to manage ET either with QC or with other tools as well. The idea is basically the same with every tool.
So let's get crackin'!
Note: I made a summary paragraph and it can be found at the very end of this post. So if you're a member of the sales division or otherwise suffer from attention deficiencies, you can skip right into it... ;)
