31. Try Out the Prototype

Overview: A well laid-out test sequence is important. Evaluate test results. Standardized documentation provides an efficient and effective way to communicate issues and weaknesses.

Considerations: Selection of the test team is an important consideration. The team should understand the intention of the test. The objective is to identify and report errors, issues, concerns, and problems. They should expect to find problems. Their findings must be sufficiently documented. The development team must understand the nature and extent of each issue. Clear communication is the primary consideration in this task. Are all the primary stakeholder groups represented and participating in the prototype test? If not, why not? Are there any people that need to be informed about the test that are not directly part of the test? Who will be interested in the outcome of the test?


  • Confirm the availability of the test team.
  • For large changes, conduct a project orientation session.
  • Familiarize the testers with the objective of the trial to find problems. Clarify that big problems will be fixed and that all problems will be evaluated.
  • Emphasize fixes of some smaller problems may be deferred to a later time.
  • Provide testers with adequate instructions and directions to understand the nature of their task.
  • Identify what is to be tested and the test criteria.
  • Arrange the testing sequence in a logical way.
  • Standardize the feedback by providing standard reporting forms.
  • Collect feedback, monitor status, and provide support throughout.

Leave a Reply

Your email address will not be published. Required fields are marked *