Sign in or register
for additional privileges

Teaching and Learning Multimodal Communications

Alyssa Arbuckle, Alison Hedley, Shaun Macpherson, Alyssa McLeod, Jana Millar Usiskin, Daniel Powell, Jentery Sayers, Emily Smith, Michael Stevens, Authors

You appear to be using an older verion of Internet Explorer. For the best experience please upgrade your IE version or switch to a another web browser.

6. Proposal

For a significant chunk of the semester, you've been developing ideas for a digital project. By the semester's end, you'll provide a proof of concept (i.e., a working example that requires more content and polish) for that project. But for now, it's time to concretely explain the project's aims and motivations, not to mention some questions and concerns you have.

Learning Outcomes 

For you to:

  • Flesh out the particulars of your 507 project, including its audience, data model, and content,
  • Articulate how your project is intervening (or could intervene) in your field(s) of study,
  • Circulate the early state of your work for feedback from me and your peers, and
  • Gain experience writing proposals for digital projects (a common practice in digital humanities and digital literary studies).

What You Should Include in Your Response

Before seminar on Thursday, March 15th, please provide the following in your Scalar path:

  • A brief description (250-300 words) of your project as it stands (including project motivation, concise lit review, method/approach, and potential contributions to/interventions in DH, DLS, &/or your field of study);
  • Project rationale (50-150 words), including not only why you are studying what you are studying but how it figures into your educational / professional / personal trajectories;
  • The project type (i.e., multimodal essay, scholarly exhibit, or data visualization) you are selecting (elaborations here, complete prompts forthcoming);
  • Data model (if you are selecting the scholarly exhibit or data visualization), which you are welcome to run by me prior to submission (note: you need not provide all of your data; just your model for now; don't reinvent the wheel);
  • Sample media/data, provided either via a link (e.g., to a spreadsheet or diagram) or in your actual Scalar page (e.g., images to the left of your text);
  • Intended audience(s) for the project, including what exactly they would expect from a project such as yours; and
  • Any questions you have for me and/or your peers, meaning your proposal is an opportunity for getting feedback and circulating ideas in the rough. Embrace that.

During seminar on the 15th, you will individually present a Pecha Kucha version (20 automated slides / 20 seconds each) of your proposal, with an emphasis on describing your project, articulating its rationale, and posing questions for your audience (i.e., me + your 507 peers). We'll then have 6-8 minutes to respond to your questions and discuss your project. (I'm setting aside ~15 minutes for each presentation, including Q&A.)

Please reference your presentation in Scalar, mentioning it somewhere in your proposal, with a link to the slides (stored on the Scalar server or elsewhere). Let me know, too, if you need help automating the presentation. (If you're using Google Presentation, then it's a bit tricky.)

The proposal (including the Pecha Kucha presentation during our seminar meeting) is 10% of your final mark.

Get in touch with questions.

As per usual, the first person who responds to the prompt will need to convert the Scalar page into a path. 

Comment on this page
 

Discussion of "6. Proposal"

Add your voice to this discussion.

Checking your signed in status ...