...
- Do we have anything that will need Confidentiality (NDA, etc)?
- Balance Gratitude with Expectations - Thank you for testing but make sure to meet deadlines for reporting
- Keep Exec Committee Involved with On-going Activities
- Keep Exec Committee Current Regarding Project Progress
- Offer a Simple Consistent Method for Testers to Provide Feedback in the Forms we want
- Testing Matrix - need to offer paper copy as well as online - how can online version be copied multiple times
- Shared Google Doc for bugs?
- One person enter bugs in JIRA
- We could use Google Spreadsheet https://docs.google.com/spreadsheets/d/1ofG21FyCoHQ381iPvd59-2w0pljDxFIIkWdg85TUjZM/edit?usp=sharing
- What or what about Google Survey for post testing impressions? https://support.google.com/docs/answer/87809?hl=en
- Allow Testers to Communicate Amongst Among Themselves (increases participation, secure outlet for excitement)
- Respond Quickly to all Issues and Requests
- Contact Inactive Testers Directly (by phone if possible)
Beta Activities
Common Beta Activities
•Bug Reports
•Specific Testing Tasks
...
- Bug Reports - Google Spreadsheet for bug tracking (above)
- Specific Testing Tasks - create a set of testing matrixes for usability and break testing
- Forum Conversations (Open and Hosted)
...
- - Hip Chat room specifically for testing
- Surveys and Polls (Technical and Subjective)
...
•If Possible, Regression Between Builds
...
- - Set up Google Survey for post testing
- Do we have a way to run regression testing between builds - we seem to keep making changes and then breaking things that worked previously
- Collect Feature Suggestions and Testimonials - this is important for newsletters going forward
Managing Feedback
Effective Data Management•Use
- Use Your Tools Effectively
...
- -
- have spreadsheet tracker and matrixes reviewed
- ask for other ideas
- Drive For Details
...
- are we capturing enough detail?
- Develop a Strategy to Handle Duplicates
...
- do we need more details in the spreadsheet so we can sort for duplicates?
- Quickly Respond to the Needs of the Test
...
- Ensure the Right People Get the Right Data
- make sure workflow gets issues from tester, to PM, to JIRA, to resolution without getting dropped in a crack
Closing a Beta Test
Keys to Closing a Beta Test•Give
- Give Your Testers Time to Submit Final Issues
...
- Cut-off Tester Access to Submit Issues
...
- can the link to a Google Spreadsheet be changed? If I change the name will it change the shared link?
- Close all Open Issues
...
- - don't leave a bug behind
- Offer Testers a Simple Means to Return Product
- This is an interesting thought! - do we have a way once people are finished testing Brown Dog that it can be cleaned from their machine? an "Uninstall Script"
Incentives!
•Ensure Incentives Match Participation Requirements
...