Session 12 · All class materials →
Lesson 12 — Product Showcase and Professional Practice
Duration: 120 minutes per showcase block; at most six individual presentations. Deck: Product showcase Lab: Your final product presentation
Outcomes
Learners demonstrate their own useful, visually appealing software; connect GitHub history, QA evidence and AI-assisted decisions; explain limitations and hand off a reproducible release. Jared Cluff records completed learning activities separately from demonstrated product quality and skills: course completion and AIQAA certification under the two-award policy. No separate exam or surprise coding challenge.
Instructor preparation
Apply the 21-criterion rubric to the frozen assessment agreement and release SHA. Complete the detailed evidence inspection before the showcase, keeping not-yet findings, unverified evidence and review-wide holds explicit. Use the published calibration and revision rules; no final-day hidden requirements, personal taste score or separate certification exam.
Use Product Studio, review checklist and showcase template. Review repositories and evidence before presentation day, including early/intermediate/test-fix/release history and a learner-explained issue-to-release chain; eight demo minutes cannot substitute for ongoing inspection. Use the private certification review for the two distinct decisions. Confirm release SHAs, synthetic data, local fallback, accessibility arrangements and each learner's appointment.
Schedule six learners or fewer per block, each with eight minutes to demonstrate and four minutes to discuss the work with Jared. For larger cohorts book additional two-hour blocks or individual appointments with Jared present. Parallel coach panels and team presentations cannot replace an individual's presentation to him. Additional showcase blocks extend delivery time for larger cohorts; the standard 26 contact hours include one block.
Use isolated, credential-free environments for student code; no secrets or personal account access on demo machines. Prepare a private progress/decision register. Do not announce certificates automatically before Jared's review.
Agenda
| Time | Facilitation |
|---|---|
| 0–10 | Welcome and expectations: useful product, evidence, growth and honest limitations. Confirm presentation order. |
| 10–20 | Demo setup and fallback checks; close private tabs/notifications and load synthetic data. |
| 20–56 | Three individual slots, 12 minutes each: eight-minute demo and four-minute conversation with Jared. |
| 56–66 | Break. |
| 66–102 | Three more individual slots, 12 minutes each. Unused slots become coached follow-up, not new assessed tasks. |
| 102–112 | Written reflection, apprenticeship interests and one concrete next skill. |
| 112–120 | Explain separate course-completion and AIQAA decisions, private issuance and certification follow-up. Celebrate shared progress without public marks. |
What to discuss
Ask about decisions already represented in the product: who benefits, why a feature was cut, what a regression proves, what the model got wrong, what changed after review and what remains risky. This is a supportive conversation grounded in the learner's work, not an unseen test.
A polished UI alone is insufficient; neither is a passing CI badge on an unusable app. Look for the agreed working journey, visual/accessibility care, GitHub practice, business artifacts, verified AI use and safe recovery.
Completion and support
Record course complete / course activities outstanding separately from AIQAA certified / not yet demonstrated / review pending. Completion recognizes finished learning activities and the presentation; certification requires all AIQAA-1.0 areas demonstrated through product quality, history and skills review. A learner with remaining product defects can complete the coursework and receive the completion certificate while working toward certification.
Only Jared authorizes each award. No numeric average or automatic issue from a bot. Record specific missing activities or certification gaps and arrange follow-up without repeating already demonstrated work. Use separate private certificate templates and issuance dates.
© 2026 Jared Cluff.
