COMPSCI 320 F26
Syllabus
Schedule
  • 09/10
  • Git 1
  • Rapid Prototyping
  • Customer Communication
  • Integrative Experience 1
  • Third Party Software
  • Git 2
  • Testing
  • UI Heuristics
Presentations
Code Review Checklist
  • Intro to SE
  • Process Models
  • Selecting 3rd-Party Software
  • Teams Workshop
  • Evaluating User Interfaces
  • Giving Presentations
  • PEaRCE Introduction
Edstem Forum
Syllabus
Schedule
  • 09/10
  • Git 1
  • Rapid Prototyping
  • Customer Communication
  • Integrative Experience 1
  • Third Party Software
  • Git 2
  • Testing
  • UI Heuristics
Presentations
Code Review Checklist
  • Intro to SE
  • Process Models
  • Selecting 3rd-Party Software
  • Teams Workshop
  • Evaluating User Interfaces
  • Giving Presentations
  • PEaRCE Introduction
Edstem Forum
  • Sprint Presentation Requirements

Sprint Presentation Requirements

This document describes requirements specific to your sprint presentations. You are also responsible for following (i.e., graded on) the guidance shown in the lecture on giving presentations, instructor feedback you receive on your presentations, and additional presentation requirements stated in class or in new or updated course materials.

Each presentation must be delivered by 3 team members, and each student must partake in at least 3 presentation.

Table of Contents

  1. Sprint Presentation Requirements
    1. Presentation Structure
    2. Presentation Quality Requirements
      1. Speaker Delivery
      2. Slides Quality
      3. Length

Presentation Structure

This section describes how your sprint presentations must be structured. Each presentation must be delivered by 3 team members, and each student must partake in at least 3 presentation.

Introduction

  • Your title slide should include the project name, team name, and team members
  • Presenters should introduce themselves, their team name, and give a one-sentence description of the project. Do not put this project description on the slide verbatim.
  • State the 3 key sprint goals; you will go into more detail on them in the next section
  • Each presenter should deliver part of the introduction.

Sprint Goal Updates (One section for each of the 3 key goals)

  • State the goal
  • Provide a bit more detail about the task. This should be some subset of why it is important, how it fits into the overall project, and what is involved in achieving it.
  • Show & explain your progress visually, e.g., a flowchart, layperson-friendly technical diagram, demo, or design diagram
  • Each presenter should present one sprint goal update.

Conclusion

  • What challenges did you face? Did anything unusual/interesting happen? If everything went smoothly, what contributed to that?
  • Summarize your sprint goals and progress. This should be concise enough that it helps the viewer remember what you talked about.
  • Closing "Thank you" slide
  • Each presenter should deliver part of the conclusion, unless there isn't enough material to meaningfully do so.

Presentation Quality Requirements

Speaker Delivery

  • Presenters should be prepared with any equipment they need and be able to quickly set up their device for presenting.
    • Have the necessary adapters with you (and have a backup adapter)
    • Know how to arrange your presentation windows across multiple monitors (i.e., mirror vs. extend displays)
    • Have a backup device ready in case your main one doesn't work and you aren't able to resolve the issue in a few seconds.
  • Presentations should be well-rehearsed.
    • Speakers should be able to deliver the verbal aspects smoothly from memory or subtly from notes.
      • You may use physical notecards or "speaker notes" in your presentation software.
      • Do not read notes from a phone or other secondary device.
  • Speakers must speak clearly and at an appropriate speed and volume.
  • Speakers must engage with the audience; look primarily out at the audience; only glance at notes when you need to.
  • When explaining a diagram or other visual, speakers must point to where they want the audience to look; use your hand, a physical or laser pointer, the mouse, etc.
  • Speakers must position themselves effectively. I.e., stand to the side rather than in front of the screen.
  • Spoken and visual elements should complement each other. I.e., the viewer should be able to understand what is shown on the slide and follow what is said verbally at the same time. Things like too much text on the slide detract from this.

Slides Quality

  • Slides should be visually consistent and show an appropriate degree of quality and professionalism (colors, fonts, etc.)
    • Note: This does not necessarily mean "boring"
  • Slides must be numbered, and all slide numbers must be visible
  • Proper use of images.
    • Use images when they convey information more effectively than text.
    • Images should serve a purpose & help the audience remember your key points.
    • Images should not distract the viewer from the main content.
  • Diagrams must be labelled & numbered, e.g., "Figure 2"

Length

Aim for your presentation to be 5-6 minutes long. Your presentation may be no more than 7 minutes in length.

The instructor may end your presentation at the 7 minute mark if it isn't clear you're wrapping up.

Last Updated:: 9/2/26, 12:46 PM
Contributors: James Perretta