1. Paper Critique
Read the paper that your team selected which employs your chosen methodology as a methodology, and provide a critique of the paper based on the rubric that you created last week. While reading the paper, if you think of changes to make to your rubric, please feel free to do so!
Use this template to create the paper critique. You can add this critique to the critique Google Doc that is already pinned to your team's private channel.
2. Prepare for Presentation
If you are presenting this week, you will create a presentation based on the paper critique. Your presentation should (1) summarize the objectives, methodologies and key findings of the paper, (2) describe the rubric that you created last week, (3) provide a critique of your team's chosen paper based on your rubric. Your presentation should be 20 minutes long, followed by a 10 minute class discussion, and have at most 20 slides. Before the presentation (i.e., by 10am Thursday Feb 11), post your presentation slides on the #presentations Slack channel.
If you are not presenting this week, you must attend the presentation. During the discussion, students will be asked to reflect on and discuss the differences in the rubrics or the critique process amongst different teams.
3. Book a Project Check-in Meeting
On March 11, there will be no class; instead, there will be a meeting between each team and the instructor to check on the progress of the project. There are 6 time slots available. Please book the project meeting via the Office Hour Calendly (The link is pinned on #announcements on Slack.)
4. Prepare the Introduction and Related Work Sections
The Introduction and Related Work sections (min 3 pages total) are due on March 12, around two weeks from now. Add a file called "paper.tex" to your Overleaf project. This will become your evolving paper draft. Use the two-column ACM paper template.
On March 18, the presenting teams will prepare a short presentation (5-10 mins max) to the class about their Introduction and Related Work. The instructor will post a PDF of the presenting team's Overleaf paper to the #presentations channel by March 13. Teams who are not presenting should read the Introductions and Related Work sections of the presenting teams' papers, and be ready to critique the writeup and the presented argument during the discussion.
The Introduction serves as an argument about why your work is necessary, unique/new and significant. An Introduction is typically 4-5 paragraphs, and within this short text, you need to convince the reader (i.e., about the necessity, uniqueness and significance of your work) and pique their interest, so that they want to read further. It is essentially an argument, where each paragraph advances the argument along with supporting evidence. During the masterclass, we will critique the argument behind your Introduction and the evidence that you provide. Just as an example, your Introduction might look something like this:
For the purpose of this exercise, add a bolded "argument" sentence to each paragraph in the Introduction section, so that students who are critiquing your writeup can easily pick out the structure of your argument.
The Related Work setion is similar---you should think of it as an argument instead of a dump of literature. Typically, the Related Work provides an argument for why your work is different from or goes beyond previous work. Similar to the Introduction section, highlight and bold the "argument" sentence in each paragraph, so that students who are critiquing your writeup can easily pick out the structure of your argument.
5. Start Designing Your System/Study
By March 19, about 3 weeks from now, you will need to have completed a design for your system and/or study. If your project does involve a system, you need to add a "System Design" section to your paper, and describe the functionalities/interfaces that your system provides. For the "Study Design" section, you need to describe the methodology you are using, argue why this methodology is appropriate (use the rubrics as a guide!), outline the procedures that a participant will follow during the study, and describe your data collection instruments (survey questions, interview questions, behaviour log from the system, etc). It's not too early to start designing and developing your system and data collection instruments.
Due Friday March 5
● complete paper critique on Google doc.
● book project check-in meeting.
Due Thursday March 4 10am (presenters only)
● post presentation slides on the #presentations Slack channel.