Presentation Logistics

This page outlines how the in-class project presentations will be conducted. Please read carefully to ensure a smooth and fair experience for all teams.

Presentation schedules:

• Lecture 10 Presentation Slots
• Lecture 11 Presentation Slots

Arrival and Seating

• Class begins promptly at 10:40.
• All presenting teams should arrive by 10:30 to test display connections and get seated.
• At any time, the next three teams should be seated in the front row, ready to present.

Time Allocation (Strictly Enforced)

Each team has:

• 6 minutes to present
• 1 minute to transition to the next team

To ensure fairness to all teams and to respect classroom booking times, the 6-minute limit will be strictly enforced.

• At 1 minute remaining, the instructor will give a hand signal.
• At 6 minutes, the presentation MUST stop immediately, regardless of completion.

We strongly recommend practicing timed rehearsals in advance.

Required Written Introduction (Due March 18)

Each team must submit a short written introduction (70–100 words) to Quercus  by March 18, 2026, 11:59 PM EST.

Important: This written introduction is not a replacement for speaking during your presentation.

It is used for the following purposes only:

1. To populate Microsoft Forms for peer-review submissions
2. To be published on the course website, allowing students to preview their classmates’ projects before presentations

During your presentation, your team should introduce the project yourselves, as part of your 6-minute time slot.

Your written introduction should include:

1. Project name and one-sentence purpose
2. Target users or use case
3. 1–2 core features (what the system does)
4. Key web technologies used (e.g., Next.js or React + Express, database choice)

Word Limit: 70–100 words

Example

“Team 8 developed CourseFlow, a full-stack web application that helps instructors manage assignments and track student submissions efficiently. The system supports authenticated users who can create assignments, upload supporting files, and monitor submission status through a responsive web interface. CourseFlow is built using Next.js with TypeScript, PostgreSQL for persistent relational data, and cloud storage for file uploads. The frontend is styled with Tailwind CSS and reusable components, while the backend handles data validation and access control. Our goal is to streamline common instructional workflows in course management.”

Presentation Setup

To minimize transition time and ensure a smooth presentation:

• Use one single laptop for the entire presentation.
• Decide before class which laptop will be used.
• Have all slides, browser tabs, and demo windows open and ready before your turn.
• Check your display settings in advance. Some laptops default to “extended display” or disable the laptop screen when connected to HDMI/USB-C. Please ensure your laptop is mirroring correctly so that both the projector and your laptop screen display the same content.
• Teams should arrive by 10:30 to verify that the projector connection works and that the display is visible on both screens.

Live Demo Expectations

The main purpose of the presentation is to demonstrate that your project’s core technical requirements are implemented and functional.

• A live demo is strongly preferred.
• You may demo:
  • a locally running development environment, or
  • a deployed version of your application (if available)

Deployment is not required, but live interaction with the system is preferred whenever possible.

Network-Dependent Backup Option

Some features may depend on stable network conditions (e.g., deployed apps, external APIs, cloud storage). If a feature is likely to fail due to network instability, you may prepare a short pre-recorded demo clip as a backup.

Guidelines:

• The presentation must still be delivered live (not fully pre-recorded).
• The recorded clip should only cover the network-sensitive portion, not the entire demo.
• While the clip plays, the presenter should explain what is happening: what the feature does, why it matters, and how it is implemented.

Examples

Professional Communication Requirement

Clear communication is an important professional skill for engineers. To help you practice this skill, presentations should not be read from a full script.

Please avoid writing out everything you plan to say and reading it word-for-word. Instead, speak to the audience and explain your work in your own words.

You may use slides with short bullet points, keywords, or a brief outline. These are meant to support your presentation, not replace it. Perfect English is not required — clarity and natural delivery matter more than polish.

Because communication is a core professional skill, clear and direct oral communication is included as a small component of the presentation grading rubric.

Communication Support

The course provides optional communication support for project presentations, including guidance from Prof. Fiona Coll (ISTEP). See Communication Support for Project Presentations for details.

No Q&A During Presentations

Because of the large number of teams and limited class time:

• There will be no Q&A during or after presentations.
• Please do not interrupt presenters at any time.
• If something is unclear, you may reflect this in your peer evaluation, consistent with the Presentation Rubric.

This ensures fairness and allows all teams equal time to present.

Summary

• Arrive by 10:30; class starts at 10:40.
• Next three teams sit in the front row.
• Submit 70–100 word introduction to Quercus  by March 18.
• 6 minutes presenting + 1 minute switching, strictly enforced.
• One laptop, prepared in advance.
• Live demo encouraged; short clips allowed for network-dependent features.
• Professional, unscripted delivery expected.
• No Q&A and no interruptions.
• All members attend both days for peer review.