Standup + Integration Session I

Session: Mon Nov 2 · Standup + Integration Session I

Format. In the room, everyone. Integration Session I moved here from Wed Nov 4, which is now the panel watch party. The standup is still a post in each team's Discord channel by 10:30, so the session time goes to Code Review 1, which is due at 11:59pm tonight.

Before 10:30: read every post and the review threads so far. List the cross-team collisions: two migrations touching the same table, flags that interact, PRs editing the same shared files. Two are known already. #1168 and #1169 share migration version 20261029120000, and #1156 and the #1088 group each wait on the other's CI. That list is today's agenda.

TODO: integration arc outline only. Fill in the timings and content slides.

Transition: Reminders first, then the post, then integration.

Reminders

• DUE 11:59pm tonight: Code Review 1 reviews, links submitted in Pawtograder
• DUE Tue Nov 3, 11:59pm: your answers to the reviews on your own stack
• DUE Wed Nov 4: First Implementation Ticket merged
• DUE Thu Nov 5: Checkpoint 2 survey

Keep this to 60 seconds. Deadlines and returning feedback only.

Transition: Now, today.

CS 4535: Software Design & Delivery

Standup + Integration Session I

©2026 Jonathan Bell, CC-BY-SA

Why today. Code Review 1 is due tonight, and the authors of every stack under review are in the room. A cross-team review is where a collision with another team's work shows up first. The ticket has to merge by Wednesday, and Jon merges only after both reviews are addressed. When two first-ticket stacks conflict, both teams settle it in the room, before either stack merges.

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. Answer a code review with a change or with evidence
4. Identify where your team's work is coupled to another team's
5. Resolve a shared migration or interacting feature flag in the room
6. Agree on an interface contract and write it down

There's no talk. The first three objectives are met by the post and the review threads, the rest by the integration session.

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: if a stack you're reviewing isn't ready, say so in your post

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. Scan every post for a stack that isn't ready to review. Each one is an author to chase today, before their reviewers lose the evening.

Transition: Then integration.

Integration Session I: Reviews in the Room

Work on your two Code Review 1 reviews, due 11:59pm tonight. The authors are here:

• Stuck on a diff? Ask the author, then put what you learned in your review
• Shared schema: two migrations touching the same table, or numbered to collide
• Merge order: stacks that wait on another team's stack

Leave with each collision either resolved or assigned an owner and a date, written on the issue.

TODO: arc and timings. Start from the collision list built before class.

First priority: cross-team merge conflicts. When a first-ticket stack can't merge by Wednesday because of another team's stack, get both owners at the same screen, agree on the merge order, and write it on both issues. A stack that has to shrink to merge gets its scoped-down version agreed on the issue now, in writing.

Second priority: reviews in progress. Walk the room. When a reviewer gets an answer from the author in person, it goes in the review, so the finding is on the record and the reviewer can defend it on Nov 16.

Transition: Close on what's next.

Up Next

Wed Nov 4: Panel Watch Party: Human in the Loop. We watch the panel livestream together, in the room.

Then Thu Nov 5: Game Day 2: Pawtograder Is Slow, in your own workspace, in the same format as Game Day 1.

Before then:

• Answer both reviews by Tue Nov 3, 11:59pm
• First ticket merged by Wednesday, once both reviews are addressed

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