Demo Day 2

Session: Thu Oct 29 · Demo Day 2

TODO — outline only. Fill in the arc, timings and content slides.

Topics on the schedule: Each team walks through its project board and every member's first-ticket PR (what it changes, how it's tested, its rollback sentence), five minutes plus questions. Running it live is optional, and there are no preview deploys. Then assign Code Review 1 in Pawtograder (two stacks per student, one teammate's and one cross-team) and spend ~15 min on what a substantive review looks like, from the code-review checklist. R4 (Code review at Google) was Oct 21: use it.

Transition: Reminders first, then what we're doing today.

Reminders

• DUE TODAY: First Implementation Ticket, review-ready
• ASSIGNED TODAY: Code Review 1, due Mon Nov 2, 10:30. Authors answer within 48 hours, and Jon merges by Wed Nov 4
• DUE: Checkpoint 2 survey, due Thu Nov 5

Keep this to 60 seconds. Deadlines and returning feedback only — questions about a specific assignment go to clinic or Discord.

Transition: Now, today.

CS 4535: Software Design & Delivery

Demo Day 2

©2026 Jonathan Bell, CC-BY-SA

TODO: framing — why this session, and what it unblocks.

Transition: Here's what you'll be able to do after today.

Learning Objectives

After this session, you'll be able to:

1. Demo working software in the real environment
2. Show change since the last demo, not a re-run of it
3. Take critical questions without defensiveness
4. Identify what your team ships next

TODO: time allocation across arcs.

Transition: Let's start.

TODO: Content

Outline only — content slides go here.

TODO

Up Next

Mon Nov 2 — Standup + Integration Session I, in the room

TODO: one-line transition from today into that session.

Before then:

• Checkpoint 2 survey, due Thu Nov 5

Close on the transition, not the reminders — students should leave knowing what today was for.