Dry run
The goal of a dry run is to test that the product can be accessed, that the remote moderated software setup works, and to try out the flow of the discussion guide. If the study sponsor wants to observe the dry run, they may expect to tweak the discussion guide based their observations. In this case, it is a good idea to have a preliminary dry run to test the mechanics before the second dry run with the study sponsor.
Results from the dry run may count as a valid session, as long as the session ran smoothly and the discussion guide was not significantly changed after the dry run.
Enough time should be available between the dry run and the first session to make any changes that are needed. A dry run might occur in the morning and the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access