Overall, things seem to be going well. However, my “genius” strategy for the QA form turned out to be incorrect. I had wrongly assumed that the testers would be able to tell that the level they were testing wasn’t a Witch’s hut, and would naturally move themselves into the correct areas for the QA. Unfortunately, quite a few did not understand that they weren’t playing in the Witch’s hut, and wound up going down question paths they weren’t meant to.
I had hoped to use this QA form could be used regardless of which level we were testing, to have a higher level of adaptability, because things like “What are we testing?” is subject to change right up until the last minute. But I see now, that I was wishfully thinking. I’ll just need to either make two separate QA documents, or ask my team to stick to QA plans as best as possible. It’ll probably be the first option.
In terms of the process for QA going forward, not much will change, but things might become a bit more tedious, having to make two separate QA forms, each sprint. I’ll make a form that relates to one level, and whatever progress we’ve made on it, and format it so only the testers who would know where we were before, would answer questions about the changes we’ve made, and new testers would answer questions better suited to people seeing the project for the first time. I’d then repeat this process for the other level.
But, at the end of the day, I’m still angry with myself. I still made this mistake, and now our QA results for the last testing session are all messed up. I made things more annoying for my team. I should have seen this coming, and at least done something. But, I can’t change the past. I’ll just have to make sure to change things in the future, and not let this happen again.