Case study presentation details

Preparation: Presentations are on a given, assigned date (tbd based on student preferences). Prior to that date, everyone reads all the sections (if a section is >1 page you can skim). Those presenting read their whole section (even if longer than a page) and also finds some outside sources to tell us about the issue; with your partner you'll identify one or more relevant specific case (hence "case study") that isn't in the reading, to tell us about (or, go substantially more in-depth into a case that's merely mentioned in the book). To prepare for the presentation, you'll identify the stakeholders (people affected) in your case(s), and the particular choice or action that was made (or that could have been made) that you want to analyse. You'll talk to your partner about the five "workable" ethical theories and what an analysis under each might look like—but then you'll narrow down which of them seem most applicable, which you'll decide to present. You can in general flip a little forward or backward in the book from your assigned section to find other similar issues, including some where the book has performed the kind of ethical analysis you'll need to do here.

Content: We've all read the section, so a quick summary is fine (to remind us) but shouldn't take up much time. Some readings include a specific incident, but all presentations should include at least one relevant specific case (hence "case study") to tell us about, that isn't in the reading. Some personal experience is fine, but it should not dominate the presentation or be the primary case discussed. Probably no video unless it's extremely important to the case (and also very short), but pictures are good. The presentation should spend significant time on ethical analysis of the choices or actions, and should explicitly reference ethical frameworks to support your arguments (but need not and should not present a laundry list of all five frameworks—choose one or two that apply best).

Logistics: Each presentation should be about six minutes (plus a couple minutes for questions and feedback). The division doesn't have to be 50% but both partners should speak. Visual aids (e.g. slides) are permitted but not required; if you will have any technical needs you should talk to me before the class to double-check and/or transfer files or whatever. Your last slide (if you do slides) or a separate piece of paper should list the sources you used for anything you present as fact. (Wikipedia is a great place to learn about stuff and you're welcome to use it and similar sites, but it should not be the source of record for any citable facts.)

Rubric: This is the rubric I plan to use, and may help you plan your presentation. In general I will start by assigning the same score to both partners in a group, but if I have reason to assign separate scores I can do that too. This is a 10-point analytic rubric, and most items are either yes or no (what computer scientists call "boolean"); some items have a breakdown for full vs partial credit.

Content: Form: Strikes (i.e. things not to do!):

What happens if my partner doesn't show up? In general, the presentation will run even if only one of a pair is in attendance. If your partner is absent I will make allowances for the fact that we're getting "half a presentation", either by letting it run short or by filling some detail in myself (or both). (My goal here is to try very hard not to penalise one partner if the other is missing, though I can't deny it might be a bit more stressful.) If there is time in the schedule I might reschedule the presentation instead, but don't assume in advance that I will do so.