Schedule¶
Class meets Tuesdays and Thursdays. The module runs five weeks, from Tuesday, November 10 to Thursday, December 10, 2026. Thanksgiving week has one session, on Tuesday, November 24, delivered online as pre-recorded videos. There is no class on Thursday, November 26.
Read the assigned chapters before class. Each session starts a lab, and each lab is due at the start of the next session unless noted. Dates may adjust; changes will be announced in class and on Canvas.
Session by session¶
| # | Date | Week theme | Read before class | Lab | Due |
|---|---|---|---|---|---|
| 0 | Before Nov 10 | Setup | Computer Setup | Accounts and installs complete | |
| 1 | Tue, Nov 10 | Building with agents | Building with AI Agents | Lab 1: Ship Your First App | Sprint 1 assigned |
| 2 | Thu, Nov 12 | Building with agents | Directing the Agent | Lab 2: Direct the Agent and Deploy | Lab 1. Sprint 1 plan due Fri, Nov 13, 11:59 PM |
| 3 | Tue, Nov 17 | Analysis and design | Requirements Discovery | Lab 3: Requirements Elicitation | Lab 2 |
| 4 | Thu, Nov 19 | Analysis and design | Interface and Flow, Specs, Testing the Design | Lab 4: Requirements to Spec to Build | Lab 3 |
| – | Mon, Nov 23 | Sprint 1 due, 11:59 PM | |||
| 5 | Tue, Nov 24 (online) | Architecture | Anatomy of an Application, The Browser and Developer Tools | Lab 5: Anatomy Teardown (self-paced) | Lab 4. Sprint 2 assigned |
| – | Thu, Nov 26 | Thanksgiving | No class | ||
| 6 | Tue, Dec 1 | Data and delivery | Data and APIs | Lab 6: Model the Data | Lab 5. Sprint 2 plan |
| 7 | Thu, Dec 3 | Data and delivery | Version Control and Deploys, Tests and Tech Debt | Lab 7: Team Workflow | Lab 6. Peer Code Review assigned |
| – | Mon, Dec 7 | Peer Code Review due, 11:59 PM | |||
| 8 | Tue, Dec 8 | AI systems | How Models Work (first three sections), Models in Your Product | Lab 8: Add an AI Feature | Lab 7 |
| 9 | Thu, Dec 10 | Demo day | Storytelling and the Final Demo, Measuring What Matters (first two sections) | Live demos and Peer Product Testing | Lab 8. Final demo in class |
| – | Fri, Dec 11 | Sprint 2 due and Peer Product Testing due, 11:59 PM |
The project in two sprints¶
The labs teach a skill on a small example. The project is where you apply it to your own system.
| Sprint | Covers | Assigned | Plan due | Due | Points |
|---|---|---|---|---|---|
| Sprint 1 | Analysis, spec, and a deployed first version (weeks 1 and 2) | Tue, Nov 10 | Fri, Nov 13 | Mon, Nov 23 | 75 |
| Sprint 2 | Data, workflow, AI feature, and the final demo (weeks 3 to 5) | Tue, Nov 24 | Tue, Dec 1 | Fri, Dec 11 | 125 |
Where each phase of the SDLC happens¶
| SDLC phase | Sessions | Main readings |
|---|---|---|
| Planning | 1, 2 | Building with AI Agents, Directing the Agent |
| Analysis | 3 | Requirements Discovery |
| Design | 4 | Interface and Flow, Specs, Testing the Design |
| Physical design and architecture | 5 | Anatomy of an Application, Browser and Developer Tools |
| Implementation | 6 | Data and APIs |
| Testing and deployment | 7 | Version Control and Deploys, Tests and Tech Debt |
| Operation and evolution | 8, 9 | Models in Your Product, Measuring What Matters, Final Demo |