Wir testen die Webapplikation, nicht dich! Fragen bitte gerne stellen, ich kann aber nicht versprechen, alle Fragen direkt zu beantworten! Bitte laut denken (<\/em>Think aloud<\/em><\/strong>). (\u00fcbernommen von Lab 07)<\/em><\/p>\n\n\n\n (2) Kontext der Anwendung erkl\u00e4ren<\/strong><\/p>\n\n\n\n Wir wollen eine Webapp entwickeln f\u00fcr online Spieleabende mit Freunden. Sie soll die remote Brettspielabende unkomplizierter und \u00fcbersichtlicher machen. Neben der Kommunikationsformen, wie Audio-, Videochat, soll unsere Webapplikation eine Filterfunktion f\u00fcr Brettspiele haben, sowie die eigentlichen Brettspiele eingebettet haben. Wir haben einen ersten Prototypen gebaut und w\u00fcrden in diesem Test gerne die Verst\u00e4ndlichkeit und \u00dcbersichtlichkeit testen. <\/p>\n\n\n\n (3) Fragebogen<\/strong><\/p>\n\n\n\n (4) Szenario(s) <\/strong><\/p>\n\n\n\n erste Szenario: per Link einladen<\/p>\n\n\n\n Du hast einen langen Tag der Arbeit beendet und w\u00fcrdest gerne mit deiner Freund_Innen ein Spielabend machen. Nach der Absprechung habt ihr entschieden, gemeinsam online ein Spielabend auf Social Play zu organisieren. Du w\u00fcrdest gerne erstens ein Account auf Social Play einlegen und deine Freund_Innen per link einladen. Du hast \u00fcber Social Play einen Link per email an deindem\/r Freund_In geschickt. Nachdem deindem\/r Freund_In sich eingeloggt ist, habt ihr eingefangen in einem Treffen zusammen Spiel auszuw\u00e4hlen. <\/p>\n\n\n\n zweites Szenario: Spiel aussuchen und filtern<\/p>\n\n\n\n Du triffst dich mit deiner Freund_Innen zusammen im online meeting Raum von Social Play. Ihr habt gestartet ein Spiel auszusuchen. Jenach euer gew\u00fcnschte Filterkriterien (z.B. Spielzeitl\u00e4nge, Spielart, geeignete Personenanzahl usw., die sollte Testperson selbst gegeben werden, um zu gucken, ob wir einige Kriterien vergessen haben) sollte eine Liste von Spiele ausgegeben werden. Dann du und deine Freund_Innen gucken solche Spiele durch und sucht ihr ein Spiel aus. Anschlie\u00dfend spielt ihr das Spiel zusammen.<\/p>\n\n\n\n (5) Aufgaben<\/strong><\/p>\n\n\n\n Mache dich mit der Anwendung vertraut<\/strong><\/p>\n\n\n\n Finde die Gruppe No board games, no gain.<\/em><\/p>\n\n\n\n Lerne die Gruppenm\u00f6glichkeiten kennen<\/strong><\/p>\n\n\n\n Erstelle ein Gruppe, bei welcher du deine Freund_innen hinzuf\u00fcgst.<\/p>\n\n\n\n Lerne die Filterfunktion kennen<\/strong><\/p>\n\n\n\n Finde ein passendes Spiel f\u00fcr deine Gruppe und w\u00e4hle es aus.<\/p>\n\n\n\n Lerne die Spielfunktion kennen<\/strong><\/p>\n\n\n\n Spiele ein Spiel durch mit deiner Gruppe<\/p>\n\n\n\n (6) Abschlie\u00dfende Fragen<\/strong><\/p>\n\n\n\n (7) Abschluss<\/strong><\/p>\n\n\n\n In the first and second usability tests Ina will be the Facilitator and in the third Brendan. Xin will be the Observer in all usability tests.<\/p>\n\n\n\n We don\u2019t want to record the test sessions as our users expressed uncomfort with the idea of being recorded. We will take notes on paper during the usability test, as we find it the easiest way to create \u201ccreative\u201d and adaptable notes. We will later summarise these notes in a more structured way in a Google Doc. <\/p>\n\n\n\n We first wrote down notes on paper block and then tranformed them into structured notes in word documents (each document for one single test person). The document is structured as the usability test workflow. We take Affinity Diagram to evaluate our results of usability testing since we consider it as the best way to fulfill our „gather and then organize“ evaluation steps.<\/p>\n\n\n\n Since we most concentrate on the improvement suggestions and critics from our test persons, we organize only the „negative“ feedback from our test persons and didn’t write down „positive feedback“ in our affinity diagram (of course positive feedbacks are noted in our structured documents).<\/p>\n\n\n\n The affinity diagram is generated using online tool Flinga<\/a>.<\/p>\n\n\n\n We learned that all test persons liked our design idea behind our application. And they think our first design is not overwhelmed with non-necessary information, wo that the it is easy to follow the test process. However, some confusions can also be found in testing. Part of the confusions are based on the Marvelapp<\/a> and partly is based on our design defects. There are also some functions we didn’t think of but proved to be important by testings. We think there are really lots of improvements to be done in further design iterations.<\/p>\n\n\n\n We first meet together in Discord and discussed the organisatorial stuff of how to organize the usability tests. Then we worked together on our script for further steps (Ina for contextual introduction and questionaire, Brendan for following-up questions, Xin for scenarios. However the separation is not 100% clear since we review and improved each other’s parts though).<\/p>\n\n\n\n The three usability tests are taken part separately over the weekends (responsible persons can be found in the table for task (2)). Notes are generated after the test and uploaded into our shared google folder.<\/p>\n\n\n\n We created the Affinity Diagram after gathering all three notes and evaluate the results. <\/p>\n\n\n\n We learned how to formly conducted a usability test. It was an interesting experience because somehow the test person can get confused by some designs which we didn’t notice it at all. We are pleased to get constructive feedbacks from our test persons. We will take their feedback into serious considerations and think about how to improve our design. <\/p>\n\n\n\n We successfully found 3 different test persons to help us with the usability testings, which we really appreciate their kindness and helpfulness. All our test persons are so cooperative which make our test processes much more smoothly.<\/p>\n\n\n\n It seems that the assignment workload is not so evenly distributed throughout weeks, for example three usability tests over a weekend is somehow a little bit more. It is also not so easy to find and contact test persons, and then finish usability testings so shortly within a week (for example, some people may be really suitable for usability testing but due to their tough schedule they need to be contacted at least one week before for appointments). That would be so nice if we can see some assignments in advance and maybe prepare it in advance.<\/p>\n\n\n\n Another improvement lies in our previous assignments. In our assignment #2 we didn’t chose „Analyze existing software“ for data gathering. Based on our usability testing results, we found it essential to do that since some of our design defects can be easily resolved by viewing similar apps or apps offer similar functions. If we view similar app designs, we at least won’t forget registration function on the main page. <\/p>\n\n\n\n Additionally, we didn’t undertake probe testing on ourselves before formal usability testing. If we did so, some problems can also be detected earlier. <\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" Part I. Assignments (1) Continue to develop (or start a new) paper prototype based on new insights or feedback from your peers. We skip this subtask since we considered the feed back from peers was planned to gathered during last lab session on 25. May which didn’t happen (question asked and got confirmed in Mattermost). … \u201e[A#6, P8] Paper prototyping and usability testing\u201c<\/span> weiterlesen<\/a><\/p>\n","protected":false},"author":6151,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"categories":[384608,395639,401100],"tags":[],"class_list":["post-1448","post","type-post","status-publish","format-standard","hentry","category-projekt-8","category-week-6","category-assignment-6"],"_links":{"self":[{"href":"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/wp-json\/wp\/v2\/posts\/1448","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/wp-json\/wp\/v2\/users\/6151"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/wp-json\/wp\/v2\/comments?post=1448"}],"version-history":[{"count":2,"href":"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/wp-json\/wp\/v2\/posts\/1448\/revisions"}],"predecessor-version":[{"id":1454,"href":"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/wp-json\/wp\/v2\/posts\/1448\/revisions\/1454"}],"wp:attachment":[{"href":"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/wp-json\/wp\/v2\/media?parent=1448"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/wp-json\/wp\/v2\/categories?post=1448"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/wp-json\/wp\/v2\/tags?post=1448"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}2.Document who is taking what role<\/h4>\n\n\n\n
3.Decide if you want to record your test session and how you take notes during the test sessions.<\/h4>\n\n\n\n
4.Document who you are inviting for a test session and how long the session lasted.<\/h4>\n\n\n\n
![\"\"](\"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/files\/2021\/05\/TestPersonen.png\")
(3) Document and evaluate the results of your testing.<\/h3>\n\n\n\n
Results Evaluation<\/h4>\n\n\n\n
![\"\"](\"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/files\/2021\/05\/AD_1-1024x444.png\")
![\"\"](\"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/files\/2021\/05\/AD_2-1024x462.png\")
![\"\"](\"https:\/\/blogs.fu-berlin.de\/hci1-sose2021\/files\/2021\/05\/AD_3-1024x402.png\")
Design defects is a subcategory which should not happen but we still have it based on our carelessness in first design. <\/figcaption><\/figure>\n\n\n\nLearning and Takeaways<\/h4>\n\n\n\n
Part II Reflexion<\/strong><\/h2>\n\n\n\n
(1) Team member contribution.<\/h3>\n\n\n\n
(2) Learnings from assignment.<\/h3>\n\n\n\n
(3) possitive\/successful experience<\/h3>\n\n\n\n
(4) What would you like to improve?<\/strong><\/h3>\n\n\n\n