Course Schedule (Overview)
This course follows an Agile, sprint-based structure modeled after real-world software teams. The exact term format can change between a regular semester and a condensed summer offering, so this page stays intentionally date-free.
This syllabus is currently configured for a 12-week online summer semester.
This version is paced for a condensed summer term. The goal is still to preserve realistic two-week sprints where possible, with fewer total sprints and earlier milestone demos rather than turning every sprint into a one-week cycle.
This syllabus intentionally avoids calendar dates for easier reuse. Exact deadlines, live meeting details, and stakeholder sessions should be announced in Canvas and class. In summer, the structure uses fewer sprints overall, but the working rule of thumb is still to preserve two-week sprints whenever possible after Sprint 0. The three milestone demos remain in place, with Milestone Demo 1 appearing earlier, typically by the end of Sprint 2.
How the Semester Is Structured
Recorded lectures support the course, but synchronous online meetings remain the main working time for teams, demos, and stakeholder interaction.
| Sprint | Weeks | Focus |
|---|---|---|
| Sprint 0 | Week 1 | Project framing, team setup, and stakeholder onboarding |
| Sprint 1 | Weeks 2-3 | Requirements gathering, validation, and early design |
| Sprint 2 | Weeks 4-5 | Documentation completion, MVP planning, early implementation, and Milestone Demo 1 |
| Sprint 3 | Weeks 6-7 | Core implementation and Milestone Demo 2 |
| Sprint 4 | Weeks 8-9 | Feature expansion and Milestone Demo 3 |
| Sprint 5 | Weeks 10-11 | Refinement, testing, final delivery preparation, and final presentation |
Weekly Rhythm
- Recorded lectures should be completed before the associated synchronous work session whenever possible.
- Synchronous online meetings are used for workshops, coordination, stakeholder meetings, demos, and active project work.
- Because the term is compressed, milestone demos and major deliverables appear sooner in the semester and teams should expect less slack between them.
On the next page, you can find a detailed breakdown of the sprint timeline and key milestones.