1. Are we(Software QA Engineer)the one that should create a beta Test plan?
2. Why create a Beta Test Plan? if its much easier for a Customer to test the product without guides or walkthrough.
3. Is there someone out there that already created this document? Can I have a look.
Currently, our team is struggling to create a good beta test plan for the End User "Tester" but it keep us wondering why we have to create a test plan for end user. It's just that I haven't encountered this test plan.
I don't usually create test plans for my Beta Programs, my task with the Beta being to have customers use the product based on their regular usage scenarios and not something I came up with.
What I like to do is to provide some guidance about the "new features" or the places where I want them to place special interest, but this can be done easily with a list of short walk-through of the application.
I enjoyed your blog post on the subject, Joel. I agree that it is important to have excellent communication with the clients performing beta testing. I used to work for a COTS developer and we tried to involve our larger client in our beta programs and we would often hold meetings with the users to gather feedback. We found that people provided much more information in person than they did in simple surveys or feedback forms.