{"id":209,"date":"2023-03-27T19:47:26","date_gmt":"2023-03-27T19:47:26","guid":{"rendered":"https:\/\/projects.etc.cmu.edu\/disco\/?p=209"},"modified":"2023-04-17T02:07:25","modified_gmt":"2023-04-17T02:07:25","slug":"week-8-tests","status":"publish","type":"post","link":"https:\/\/projects.etc.cmu.edu\/disco\/week-8-tests\/","title":{"rendered":"[Week 8] Tests"},"content":{"rendered":"\n
\"\"
Halves Feedback<\/figcaption><\/figure>\n\n\n\n
\"\"
Timeline & Availability<\/figcaption><\/figure>\n\n\n\n

After halves, our project focus shifted from exploration and ideation to testing and iteration<\/strong>. After discussing with Jessica in our regular meeting, we totally have 4 opportunities for us to test.<\/p>\n\n\n\n

Opportunity #1<\/strong>: Ricardo\u2019s DAS class<\/strong><\/p>\n\n\n\n

    \n
  1. Reaching out to working with DAS\/Ricardo : sending out a survey to fill out and gather the information is good.<\/li>\n\n\n\n
  2. Talk to Ricardo about the acceptable timeline for exchanging data – when we should gather and return the feedback for the students to make use of their projects. <\/li>\n<\/ol>\n\n\n\n

    Opportunity #2<\/strong>: <\/strong>Class context<\/strong><\/p>\n\n\n\n

    Jess\u2019 connection: Eric – Design for Educational Games also runs a 6-week project for his class so this can be an option if we\u2019re interested in working with him to gather real data.<\/p>\n\n\n\n

    Opportunity #3<\/strong>: Presentation context<\/strong><\/p>\n\n\n\n

    Jess is giving a talk on Thursday 4pm<\/strong> and we can use this session to send out a google form (remote\/in-person) to the audience to gather feedback. If we\u2019re not ready by Thursday, she has more talks scheduled that we can incorporate. <\/em><\/p>\n\n\n\n

    Opportunity #4<\/strong>: Mentor context<\/strong> <\/p>\n\n\n\n

    (ex. She mentors PhD students in HCII) for performance feedback<\/p>\n\n\n\n

    We’ve reached out to Ricardo Washington this week and settled down our long-term collaborative relationship for using Filer to improve students’ feedback performance. Then, we decided to use his class on Thursday to be the first test day to collect students’ feedback (because we didn’t have workable demo yet).<\/p>\n\n\n\n

    Also, we decided to use Jessica’s talk to collect feedback. <\/p>\n\n\n\n

    Two forms we wrote:<\/p>\n\n\n\n

    \n
    \n
    \n
    DAS’s Feedback Collection<\/a><\/div>\n<\/div>\n<\/div>\n\n\n\n
    \n
    \n
    Jessica’s Talk Feedback Collection<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

    We printed QR code and sent them out in the DAS class. We also put the Talk’s QR code into the presentation slides, along with the link sent in zoom.<\/p>\n\n\n\n

    \"\"
    Printed QR Code<\/figcaption><\/figure>\n\n\n\n

    However unfortunately, we didn’t get good quality answers from the survey. The survey was only filled by few people in the class, which is not good for us to implement a long-term learning test.<\/p>\n\n\n\n

    \"\"
    Received Survey<\/figcaption><\/figure>\n\n\n\n

    After collecting all the feedback, we tried to write sample feedback in Friday based on the rubric in Jessica’s previous paper. We used codes to categorized all the sample feedback.<\/p>\n\n\n\n

    \"\"
    Rubric from the Paper<\/a><\/strong><\/figcaption><\/figure>\n\n\n\n
    \"\"
    Sample Feedback<\/figcaption><\/figure>\n\n\n\n

    Tech demo updated by our programmer – Muru:<\/p>\n\n\n\n