Demo Day 1

Session: Thu Oct 15 · Demo Day 1 · 65 min

One spine: four teams show the problem, what the sprint found, and the scope they've set. Then everyone leaves knowing how to pick a first implementation ticket by Monday.

Structure.

• Reminders, title, and format (~4 min, three slides).
• Four demos (~40 min). One 10-minute timer per team: 0–5 demo, 5–9 questions, 9–10 everyone finishes that team's worksheet while the next team sets up. Draw the order at the start.
• First Implementation Ticket (~10 min, one slide).
• Up next (~2 min).

About 56 of 65. Demos always run long. Stop each demo at 5:00 and move to questions. The 10-minute timer doesn't stop for setup.

Before class:

• Four slips of paper for the order draw, or a random picker.
• Worksheets: cs4535/demo-day-worksheets/demo-day-1-worksheet.pdf, two half-sheets per page. Two pages per student, cut in half, gives each one four half-sheets (three to use, one spare).
• Production and staging both up. A team whose live product won't load demos from its sprint repro or screenshots.
• Sentry open on your laptop, in case a demo turns up an error.
• Note one question per team from reading their sprint artifacts.

Attendance: missing a demo day without arranging it in advance counts as two absences.

Transition: Reminders first.

Reminders

• ASSIGNED TODAY: First Implementation Ticket. Know it by the end of class, scope agreed by Mon Oct 19, review-ready Thu Oct 29, merged Wed Nov 4
• FEEDBACK: Checkpoint 1 and the sprint, by Mon Oct 19
• MON OCT 19, 10:30: Pre-reads for R4 and R1. Standup that day is a Discord post
• FUNCTIONS: Your first item is posted in your #fn- channel

Sixty seconds. If anyone didn't post a function item yesterday, ask them to do it by tonight.

Transition: Here's how today runs.

CS 4535: Software Design & Delivery

Demo Day 1

©2026 Jonathan Bell, CC-BY-SA

Framing: the sprint shipped nothing on purpose. Today is the last demo where showing the problem and the plan is enough. On Oct 29, every demo shows a review-ready change running on its preview deploy.

Transition: The format.

Ten Minutes per Team

Show	Say
The current product, in the flow you're changing	What a user can't do today
What the sprint turned up	One or two findings, each with a teammate's name on it
Your scope	What you're building by Nov 23, what you cut, and your first milestone date

10:00 timer: 5 min demo · 4 min questions · 1 min to finish the worksheet. Audience: fill in a half-sheet for each team you watch, and each other team asks one question. The sheets go to the team at the end of class.

Draw the order now, and hand out the worksheets.

The question rule keeps the room from going quiet: each other team owes one question per demo, so three student questions, then yours. A good question names something specific from the demo. "What happens if the scan is rotated?" works. "Cool, how long did that take?" doesn't count.

Your question for each team should come from the sprint artifacts. The one most worth asking is usually: what did the sprint change about your plan?

Transition: First team.

Demo 1

10:00 · demo 5 · questions 4 · worksheet 1

Start the 10:00 timer. At 5:00, stop and move to questions. At 9:00, call time on questions so everyone finishes their sheet. Write down the cut and the first milestone date each team names. They're what Demo Day 2 is checked against.

Demo 2

10:00 · demo 5 · questions 4 · worksheet 1

Start the 10:00 timer. Note the cut and the first milestone date.

Demo 3

10:00 · demo 5 · questions 4 · worksheet 1

Start the 10:00 timer. Note the cut and the first milestone date.

Demo 4

10:00 · demo 5 · questions 4 · worksheet 1

Start the 10:00 timer. Note the cut and the first milestone date.

Transition: Now that everyone has seen all four plans, pick your first implementation ticket.

Your First Implementation Ticket

XL. Know it before you leave today. Scope agreed with me on the issue by Mon Oct 19. Review-ready Thu Oct 29. Merged Wed Nov 4.

• Default: your own project. Start from your sprint artifact, your team's filed issues, or your Agents Activity analysis
• Already claimed an XL pool ticket in the Agents Activity? That's your ticket
• Pool: two XL tickets left, #467 and #1026. Comment to claim

XL means more than one layer, and a one-sentence "done" that mentions a user. Steps 4 to 6 of the Agents Activity are how you scope it.

Review, then it ships. On Oct 29 I assign two reviewers to each stack, one teammate and one from another team. Reviews are due Mon Nov 2 before class, and you answer within 48 hours. Then I merge, and you go look: click it in your team's demo class and post the verification in your team channel.

Handout: First Implementation Ticket

Ten minutes. Two minutes on the slide, then eight for picking, in the room, while you're here to agree scopes. Goal: everyone leaves knowing their ticket. Pool claims from the Agents Activity (Aryan, Zhirui, Bohan, Nour, David) carry over, so they're done. Go to the other eight first. Anyone with an own-project ticket opens the issue now and tags you.

Say the timing out loud: Game Day 1 is Oct 22, in the middle of the window. A ticket picked on Oct 24 gets four working days.

Point at the overlap with functions. An XL item on your function's starting list that sits outside your team's area counts for both the Pass item and the Distinction evidence.

Review is assigned, through Pawtograder (Code Review 1). Two reviewers per stack, one teammate and one cross-team, assigned Oct 29 and due Mon Nov 2 at 10:30. You merge once both are addressed. So Oct 29 is review-ready: CI green, described, rollback sentence, preview deploy working.

Transition: Here's what's next.

Up Next

Mon Oct 19, Tech Talk: Operations

Infrastructure as code, observability, and incident response, three days before Game Day 1.

Before then:

• Get your ticket's XL scope agreed with me on the issue
• Standup Mon Oct 19 is a Discord post by 10:30
• R4 and R1 pre-reads, Mon Oct 19 by 10:30

Before anyone leaves, sort the worksheets into four piles and hand each team its pile. Photograph each pile first: the sheets are the one record of what the room thought.

Close on the transition. Students should leave knowing what their first ticket is, or exactly what they need to decide by Monday.