Winter 2012 450/496 Proposals & Schedule

beware!

Your final project proposals are due Thursday, January 26, at 5:30. Your Project Proposal must contain:

1. A working title for your project.
2. A one-sentence description of your project.
3. A one-paragraph description of your project.
4. A one-page description of your project.
5. A description of your products of study—what you're going to actually produce during the course of your project.
6. Visual and/or written research for your project—other people’s work
7. Treatment visuals for your project—your own work
8. A written description of specific technical and research issues you will need to address during the course of your project.
9. A timeline of your project. When you will be doing all of this good stuff. You must include specific deadlines (for example: "May 17th", not "some time in May."
10. A blog containing all of the above. You must document your progress and process on the blog by updating it weekly.

Critique schedule is as follows.

Thursday, Jan 26, 5:30 - present your complete proposal and work in progress (WIP)

Thursday, Feb 9, 5:30

Thursday, Feb 23, 5:30

Thursday, March 8, 5:30

Final Critique Tuesday, March 20 5:00-6:30 *All Work Must Be Completed By This Date!*

Capstone Paper Guidelines

Before receiving a final grade you must present your final project in a capstone paper. The paper should be a 5-10 page reflective essay and include images and a bibliography. Images may be incorporated into the body of the paper or attached as an appendix. The paper is due 3:30, Monday, June 6 at the final critique.

1. Think of the paper as a presentation of your project to an audience of complete strangers. Use your project proposal to help you articulate your project and your process to this audience.

2. What were you trying to achieve with the project? Did you have a clear goal or purpose in mind? Were some aspects of the project more experimental? Discuss influences on the project, and include images and a bibliography.

3. Reflect on your process and give a post-mortem of the project. What went right? What went wrong? Did the project change as you went along? Did obstacles arise? Were they expected or unexpected? How did you overcome these obstacles? What advise would you give others undertaking similar projects?