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 17-week semester.
This version is paced for a full-length semester. Sprint 0 is a one-week kickoff sprint, and the best rule of thumb is that the remaining sprints are two weeks long.
This syllabus intentionally avoids calendar dates. Exact due dates, holidays, and stakeholder meetings can shift by semester and should be announced in Canvas and class. Sprint 6 may be shortened depending on the spring or fall calendar, but the best rule of thumb is that sprints are two weeks long after Sprint 0.
How the Semester Is Structured
Students should plan around the published class meeting schedule and use those meetings for instruction, collaboration, and stakeholder-facing work.
| 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, and early implementation |
| Sprint 3 | Weeks 6-7 | Core implementation and Milestone Demo 1 |
| Sprint 4 | Weeks 8-9 | Feature expansion and Milestone Demo 2 |
| Sprint 5 | Weeks 10-11 | Refinement, testing, and Milestone Demo 3 |
| Sprint 6 | Weeks 12-13 (sometimes shortened) | Final polish, delivery, and final presentation |
Weekly Rhythm
- Scheduled class meetings focus on instruction, team coordination, and project work.
- Teams are expected to maintain momentum between meetings using Jira, GitHub, and shared documentation.
- Stakeholder communication and deliverable deadlines are announced within each sprint rather than tied to fixed syllabus dates.
On the next page, you can find a detailed breakdown of the sprint timeline and key milestones.