We will spend the last weeks of this course focused on a collective final project. Over the course of the semester you will propose and refine topics based on your own interest. You’ll then be placed into groups of 3 based on shared interests and different backgrounds. You should then develop a complete, coherent design project worthy of the cover of your portfolio. This is the most important part of this course, and we should put considerable effort into it.
As a group, you will formulate objectives and success criteria for your Final Project. You are expected to go beyond merely building a cool visualization or a fun game. Instead, your project should develop around a central research question or hypothesis. For example, if you wish to develop an app for civic engagement, how will you test whether it's successful? While making a game just for fun is prohibited as a Final Project idea, gamification of another concept (e.g. child development, civic engagement) is encouraged.
Remember, the Final Project makes up 35% of your final grade.
| Deliverable | Due Date | Grade | |
|---|---|---|---|
| 0.0 | Precedents (individual) | Feb 1 | 3 |
| 0.1 | Three Ideas (individual) | Feb 8 | 3 |
| 0.2 | In-class Brainstorming (group) | Feb 22 | 3 |
| 0.3 | Proposals (group) | Mar 1 | 3 |
| 0.4 | Storyboards and Proof of Concept | Mar 15 | 3 |
| 0.5 | In-class Desk Crit (Outline) | Mar 15 | 5 |
| 0.6 | Minimum Viable Product | Mar 22 | 15 |
| 0.7 | In-class Desk Crit (MVP) | Mar 22 | 5 |
| 1.0 | Presentation | Apr 5 | 10 |
| 1.1 | Final Functioning Code | Apr 19 | 25 |
| 1.2 | Styling and Aesthetics | Apr 19 | 25 |
The Final Project will require you to jump into the collaborative features of GitHub. One member of your group should create a new repository for the Final Project, and invite your group members (and also me) as collaborators. The code from the final commit to your group repository before the deadline will be considered the final submission.