Project Milestones¶
The dates should be mapped to the current semester calendar.
| Milestone | Target stage | Minimum evidence |
|---|---|---|
| M0 — Team & problem | Early semester | Team, problem statement, stakeholders, repository |
| M1 — Requirements | After requirements unit | Prioritized backlog, acceptance criteria, scope boundaries |
| M2 — Architecture | After architecture/design units | Diagrams, ADRs, risk list, first vertical slice plan |
| M3 — Working increment | Mid-semester | Executable feature, tests, pull requests, CI |
| M4 — Quality increment | After testing/quality units | Expanded tests, quality analysis, refactoring, security review |
| M5 — Final release | End of semester | Reproducible release, demo, documentation, retrospective |
Milestone review format¶
For each milestone, teams should answer:
- What changed since the previous milestone?
- Which evidence demonstrates progress?
- What did we learn or revise?
- What are the top three risks now?
- What is the next smallest valuable increment?