Skip to main content

Presentation (Final Portfolio Component)

TipSee a worked example

The the Presentation submission in the NHANES worked example shows one illustrative version of this milestone. Use it for structure and depth — your project must be your own.

Purpose

The presentation is the knowledge-translation slide version of the final project, submitted as a narrated 5-7 slide deck and scored as the Presentation component (10 points) of the Final Portfolio. It should explain the audience, question, data, one or two main findings, limitations, and the practical meaning of the work without overclaiming.

Due Timing

The narrated deck is submitted online with the Final Portfolio on Dec 11; there is no in-class presentation session. Record narration over your 5-7 slides (a narrated slides.html/slides.pdf export, or a short screen recording) and commit it with the slide source.

Points and Score Ownership

The presentation is worth 10 course points and receives one group score. The checklist below guides the direct 0–10 score; no contribution multiplier or performance-band conversion is used.

The ten points are allocated across five broad criteria:

Criterion Points
Audience, purpose, and story 2
Source, evidence, and interpretation 2
Limitations, privacy, and stewardship 2
Render, readability, narration, and pacing 2
Feedback, revision, reproducibility, and AI evidence 2
Total 10

These categories do not reward decorative polish or a particular presentation tool. A plain, readable, evidence-based presentation can earn full credit. One underlying problem is assessed under the category that most directly owns it rather than being automatically deducted in several categories.

Required Deliverables

Create or update:

milestones/m5-presentation/submission/

Include these files. All are required; tags follow How To Read Submission Lists.

  • slides.qmd [required]
  • slides.html or slides.pdf [required] — commit this explicitly required rendered file with slides.qmd
  • narrated recording [required] — a narrated export of the slides or a short screen recording; if narration is embedded in slides.html/slides.pdf, note that in presentation-checklist.md
  • source-and-limitations-note.md [required]
  • presentation-checklist.md [required]
  • peer-feedback-received.md [required] [brief — 1-3 focused bullets or sentences are enough]
  • ai-use-note.md [required]

What To Submit

Submit your GitHub repository link on Canvas after committing and syncing the files above. In the Canvas comment box, include the latest commit hash, the slide path, and any rendered slide link.

Slide Requirements

The presentation requires a renderable slides.qmd. If your A8 submission used the equally valid outline pathway, convert that revised story into the Week 9 slide starter now; this is the intended A8-to-presentation progression, not a new communication task.

Use 5 to 7 slides:

  1. Title, team, audience, and KT purpose
  2. Question and why it matters
  3. Data source, analytic sample, and stewardship note
  4. Main figure or table
  5. Interpretation and limitation
  6. Practical implication or next step
  7. Backup or Q&A slide [optional — include only if relevant to your project; a 5- or 6-slide deck with no backup slide loses nothing]

Source And Limitations Note

source-and-limitations-note.md should include:

  • data source and citation
  • key inclusion or exclusion choices
  • whether results are descriptive, predictive, or causal
  • one privacy or stewardship caution
  • one limitation that should be stated aloud

Peer Feedback Received

peer-feedback-received.md should summarize the feedback your group received, identify the source of the feedback, and state what you changed or chose not to change before finalizing the narrated deck. The main source is the M4 peer review your group received; peer feedback from the Week 9 exchange counts too if you used it. You are summarizing existing feedback, not writing a new response document.

Reproducibility Expectations

Slides should render in GitHub Codespaces or a documented local environment. Figures and tables should come from the project repository whenever possible. Screenshots may be used for dashboards, but the source page or app path must be documented.

AI-Use Expectations

AI may help improve slide wording, draft speaker notes, or identify jargon. Students must verify all numbers, citations, screenshots, and claims. The ai-use-note.md should state what AI helped with and what was checked manually.

Presentation Preparation Checklist

The bullets below unpack the five scored categories above; they are preparation checks, not additional scored rows.

  • audience and KT purpose are clear
  • question is focused
  • data source and limitations are transparent
  • main visual is readable on screen
  • interpretation is accurate and non-causal unless justified
  • privacy and stewardship risks are acknowledged
  • narration fits the target length
  • likely questions are anticipated in the deck or a backup slide

Definition Of Done

The presentation is done when the narrated slides are committed, rendered, and submitted with the Final Portfolio, and play without relying on local-only files.