You'll DESIGN, BUILD, and TEST your own crowdsourcing system.
This is a team-based, semester-long design project, in which you'll create an original crowdsourcing application on your own. You'll work in teams of 3-4 people. More information about each milestone will be added to this page. Here is the timeline and grading weights for each milestone:
Now that you've mastered the arts and skills of crowdsourcing, it's important that you apply what you learned to a problem you deeply care about. It's a great way to learn further, and potentially make impact.
We'll create an assignment in KLMS for each milestone.
For each milestone deadline, all members of your team will lose 10% for each late day. Submissions will be accepted until three days after the deadline. After then you'll get 0 on that assignment. Please note that late submissions for midterm and final presentations are not allowed.
You'll need to find teammates to work on an exciting crowdsourcing project this semester. Each team should have 3-4 people.
Here are three methods we provide:
Please email the course staff (me and TA) with a list of your team members, including name, student ID, and email.
In a team, you'll identify a problem that you'd like to tackle with your project, and brainstorm three distinct approaches to solving the problem.
In your report, please answer the following questions:
One report per team. Your report should be submitted as a zip file. The main report should be written in Markdown (please use the .md extension). We're going to publish your reports on the course website. Submit your team's report on KLMS.
Your team will now further develop the ideas that you came up with in Milestone #1. You'll create three types of artifacts that will capture your design process. Please follow the order presented below.
Your report should include the three components: storyboard sketches, a concept video, and an abstract.
One report per team. Your report should be submitted as a zip file.
Now that you've identified an interesting problem, a set of concrete tasks you want to support, and a set of possible solutions, it's time to turn these into a convincing pitch!
You'll have 10 minutes to do the following:
After the pitch, you'll have three minutes for Q and A.
Note: We'll enforce a strict 10-minute time limit by cutting off the presentation. Please plan and rehearse.
Here's how your pitches will be graded.
You'll present in class and submit your slides after the class.
Your team's slides should be submitted as a PDF file, via KLMS.
Now you have a clear idea and concrete tasks and scenarios to support in your crowdsourcing application. Let's start prototyping the idea!
Before making something that's fully functional with a server backend and a visually pleasing interface, it's more important to first "implement" the tasks and scenarios into a prototype.
Rather than use HTML and Javascript, you'll first use a prototyping tool to implement the tasks and scenarios. Specifically, we recommend Marvel, InVision, or proto.io. You can also choose any prototyping tool of your choice.
Functionlity does not need to be fully implemented. Please use hard-coded but realistic data, Wizard-of-Oz, and fake results, so that you can focus on the essential: the UI and the crowd workflow rather than the underlying implementation.
Your report should include:
One report per team. Your report should be submitted as a zip file. The main report should be written in Markdown (please use the .md extension). Submit using KLMS.
Finally, the tasks and scenarios you want to support need to be available in an interactive prototype.
Functionlity does not need to be fully implemented. Please use hard-coded but realistic data, Wizard-of-Oz, and fake results, so that you can focus on the essential: the UI and the crowd workflow rather than the underlying implementation.
Your report should include:
One report per team. Your report should be submitted as a zip file. The instructions should be written in Markdown (please use the .md extension). Submit using KLMS.
Now you're finally building a fully functional prototype, with live user interactions. Please make sure users can complete the tasks you initially outlined in the earlier milestones.
Your report should include:
One report per team. Your report should be submitted as Markdown (please use the .md extension). Submit using KLMS.
Now that have an awesome prototype that should be getting a lot of excitement from your crowds, it's time to tell us about what you built and what you learned from having real crowds use the system.
You'll have 10 minutes to do the following:
After the presentation, you'll have three minutes for Q and A.
Note: We'll enforce a strict 10-minute time limit by cutting off the presentation. Please plan and rehearse.
Here's how your pitches will be graded.
You'll present in class and submit your slides after the class.
Your team's slides should be submitted as a PDF file, via KLMS.
Now that you have deployed your system for a couple weeks, seen your crowd use the system, and collected useful data, it's time to write it all up! You've already read and written responses to 30+ crowdsourcing papers, so let's write one on your project.
Find a model paper that your team really likes or is inspired by, and use it as a template. Here's a suggested outline:
Here's how your paper will be graded.
You need to submit a maximum 4-page paper in the CHI Proceedings Format.
Your team's slides should be submitted as a PDF file, via KLMS.
Up to +10% on the final report
Video is a great way to demonstrate the awesomeness of your application. Follow the guidelines from the concept video to create an updated version of your video, which should feature the final interface design. Add the video link in your final report.
Up to +10% on the final report
A group that recruits the most active crowd deserves some credit! We'll reward one group that most successfully showed the power of the crowd. This does not just mean the most number of users, but includes the overall participation, quality of data, and your analysis of the data. We'll announce the winner and explain why they deserve the "Best Crowdsourcer" title.