Written Standup + Clinic

Session: Mon Oct 26 · Written Standup + Clinic

Format. The standup is a post in each team's Discord channel by 10:30. Attendance is the post. The room is open for clinic, and clinic is optional. This changed after s16 (Oct 19), when most of the room was empty during midterms and the decisions made there had to be re-sent by email. A Monday standup works as well written, and it reaches the people who weren't there. Demo days, game days, and integration sessions stay in the room.

Before 10:30: read every post. Anyone without one by 10:45 is absent. Message them that day. Pull blockers that need you into clinic, and reply in the channel to the ones that don't.

Transition: Reminders first, then clinic.

Reminders

• DUE today: your team's GitHub Project board, linked in your standup post
• DUE Thu Oct 29: First Implementation Ticket review-ready, demoed from the preview deploy at Demo Day 2
• FEEDBACK: Game Day 1 worksheets, collected in class Thu Oct 22. Notes come back this week

Keep this to 60 seconds, for whoever came to clinic. Deadlines and returning feedback only.

Transition: Now, today.

CS 4535: Software Design & Delivery

Written Standup + Clinic

©2026 Jonathan Bell, CC-BY-SA

Why today. Three days before Demo Day 2. A first ticket that isn't review-ready by Thursday has no preview deploy to demo and gives its reviewers nothing to read. The board is due today because s16 showed a missing planning step: teams hadn't agreed on what depends on what. The board replaces the planning document students said nobody would read.

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

Learning Objectives

After this session, you'll be able to:

1. Write a standup post that's useful to someone who wasn't there
2. Name a blocker with a specific ask attached
3. Show your team's plan to Nov 23 on a board a teammate can act on

There's no talk. The objectives are met by the post and by clinic.

Transition: The post.

The Post: by 10:30, in your team's channel

• Done: what you finished since the last standup, with links
• Blocked: what's in your way, and the specific thing you need from someone. "Nothing" is fine if it's true
• Next: what you'll do before the next standup
• Today only: a link to your team's GitHub Project board (one person posts it)

The post is your attendance. "Still working on it" doesn't meet the format: A teammate who reads it should know what you did and what you need.

Same three questions as the async sprint. Check each board as you read: every issue has an owner, a size, a milestone, and the "how would we know it broke" line. A board missing that line gets one reply naming the issues that lack it.

Transition: Then clinic.

Clinic

The room is open for the whole session. Come if you have something to bring:

• a blocker from your post
• an architectural question or a design tradeoff
• a first-ticket PR that won't go green before Thursday

Posting is required. Coming is optional.

Priority today: red CI on first-ticket stacks. Thursday's demo is from the preview deploy, so a PR that can't deploy is the thing to fix here. Second priority: a team whose board has no issue past Nov 4.

Transition: Close on what's next.

Up Next

Wed Oct 28: Reading Presentations 2: Copilot Productivity · AI Slop

Then Thu Oct 29: Demo Day 2, where every first ticket is demoed review-ready from its preview deploy.

Before then:

• Read both one-page pre-reads for Wednesday
• First ticket: CI green, PR described, preview deploy working by Thursday

Put the reminders first and close on the transition. Students should leave knowing what today was for.