====== Lab 13: Final Presentation ====== During the final lab on **06.01.2026**, we will hold the Final Project Presentations (Investor Pitch Day). Please make sure you have **submitted the final progress report** and finalized your project **source code** and **README** on [[https://gitlab.fel.cvut.cz/|GitLab]] no later than **Sunday 04.01.2026** - your project will be evaluated based on the state of the repository at that time. Please arrive at least **5 minutes before** the lab starts (i.e., **10:55**). You will present in the following time slots: * 11:00-11:15 **Vidverto** - Jan Kupka & Ivan Samarskyi * 11:15-11:30 **FlashGen** - Matěj Klouček * 11:30-11:45 **NavigationAssistant** - Daria Kaminska * 11:45-12:00 **DigitalSignage** - Jan Kadlec & Victor Fredrik Kempf * 12:00-12:15 **ScamBaiter** - Rafael Galiev & Ramil Farzaliyev * 12:15-12:30 **FirstBite** - Natalia Li & Manya Kaur Bhutani We will try to fit everything into the standard 90-minute lab slot. However, please note that the schedule may slip slightly, and the lab may end later than planned. ===== Time schedule per team ===== Each team is expected to follow this structure: * **4 min** - Pitch (sell the idea) * **Demo:** * **4 min** - Live demo, or * **2 min** - Pre-recorded demo (if a live demo is not feasible) * **4 min** - Technology review + evaluation vs. PRD * **4 min** - Q&A Please stick to the time limits. If your presentation runs too long in one section, we may ask you to move on to the next part. ===== Pitch guidance ===== Imagine you are pitching your idea to a group of investors. You only have 4 minutes: introduce the problem, your solution, and why it is worth investing in. Suggested topics include: * The problem * The solution * Competition / alternatives * What makes your solution better * Traction and key metrics * ... You are free to choose any format and style. Feel free to be creative. ===== Live demo ===== If you plan a live demo (highly recommended), prepare a pre-recorded backup in case something goes wrong. If the live demo fails, switch to the recorded version and continue. ===== Technology review + evaluation vs. PRD ===== This part should focus on the engineering behind your project and should be strictly technical. You are expected to cover: * System overview * Data * Model * Evaluation - metrics, failure cases; **numbers are mandatory** * Deployment, runtime, expected cost * Comparison against the original PRD (what was achieved, what was omitted, and why) ===== Rating ===== The presentation is worth up to **20 points**. The score will not be based purely on code quality or technical complexity. We will primarily evaluate pitch clarity, demo quality and credibility, engineering approach, rigor of evaluation, honesty about limitations, and how well you justify changes relative to the original PRD.