Session 12 — Product Showcase, one step at a time

Back to the showcase · All help guides

Finish with: a presentation of your working product and the evidence of how you built it. Preparation uses your course-long homework. Your assigned slot is eight minutes to demonstrate and four minutes to discuss with Jared. There is no separate test.

1. Identify the version being reviewed

Open your own product repository, approved assessment agreement and the project rubric. Record the full repository URL, release/tag and exact commit. Copy the showcase template into your existing product evidence area; do not create a second application or move code into the lab submission repo.

Checkpoint: your demo, tests and evidence refer to the same reviewed version. Mark any later change clearly and arrange review.

2. Assemble an evidence index

Link existing artifacts for approved scope, earlier/intermediate milestones, issue → branch → PR → human feedback → revision history, manual checks, a meaningful regression, visual/keyboard/mobile improvements, business/data work, recovery and AI/cost decisions. Link setup instructions and known limits.

Do not invent missing historical work. Identify gaps and discuss specific follow-up. Use the rubric and your agreed project scope to determine applicability; do not invent an account system solely to satisfy a hypothetical security example.

3. Rehearse the eight-minute demonstration

0–1 minute: audience, problem and three core features.
1–4 minutes: main journey, saved result, error/recovery and responsive/keyboard behavior.
4–6 minutes: one actual development chain and meaningful regression, with earlier history already reviewed.
6–7 minutes: affordable model use, a correction you made, spending and a business decision.
7–8 minutes: release, setup, known limits and next improvement.

Set a timer and rehearse with synthetic data. Open the exact tabs/files ahead of time. Notes are allowed. Practice explaining one decision in your own words for the following four-minute discussion.

4. Prepare for a connection problem

Keep a local working copy, safe screenshots and a short fallback recording. Show which behavior a fallback actually demonstrates; unobserved functionality remains unverified. Close private tabs, notifications and credential-bearing terminals before sharing. State supported/tested platforms honestly. Paid hosting and desktop presentation software are not required.

5. Save and check your work

Send the full repository URL and reviewed release through the instructor-approved private cohort channel. Confirm your presentation slot. An optional Session 12 packet is only an index/summary using the submission workflow. Keep personal feedback, identities and certificate decisions private.

Course completion and AIQAA certification are separate human decisions. A green packet bot or completed checklist does not award either one. Missing evidence gets specific follow-up on the project.

If you get stuck

Choose the highest-priority evidence gap with Jared and agree on a concrete next action. If the app will not run, preserve the error and arrange follow-up; a polished slide cannot establish unobserved functionality. Help checklist.