Hi Filip, On Jan 17, 2013, at 12:02 PM, Filip Kosík <208245@xxxxxxxxxxxx> wrote: > Hi Stephanie, > > It seems good to me. I think that introductory part contains everything necessary (e.g. I think it is great to motivate for thinking out loud during test) except some requirements around recording, which depends on other aspects (and it needs to be clarified as Stephanie mentioned in the draft). > > I have only one suggestion for the introductory part of the test scripts. There is the following sentence: “This session should take about 30 minutes”. I think that it can be a bit stressful for some participants. Maybe we can add the information that is not necessary to complete the task. Or we can just mention that they need not worry about time (we can terminate the test after our reserved time, of course). By giving them an idea of how long it will take helps them understand a little bit more of what to expect. I can change the wording a bit or add a statement after along the lines of: "Don't feel rushed or worry about the time." maybe to relieve any stress they may have. > > I think we should also get some immediate feedback after the task – How they felt during their task (e.g. frustrated, confused,...); Whether they have any comments / suggestions etc. Sounds good! I'll add that at the end. > > I have read quite a lot of literature about the usability testing, but I have no practical experience yet. But in my opinion, some tasks may be more specific (e.g. we can require specific settings during “Non-English/US Install”). Maybe we can try a pilot test before DevConf. I think a pilot test is a good idea. I'll add a few tasks for the first use case. > > Filip Thanks, Stephanie _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
