Checkpoint 3 (CP3)

Phase 3 — Synthesising · Due Week 15 · 12%

Due: Week 15, December 14th — submitted to E3 by start of class. Weight: 12%.

Overview

CP3 closes Phase 3 and is the last major team submission before final presentations.

What to Submit

  1. Refined prototype — the version you will demo in Week 16. It must be stable, running, and tested. If it requires setup, the setup must be documented clearly enough that someone who has never seen your project can run it.
  2. Full evaluation report — outcome evidence that your tool reduces the collaboration problem you identified. “Users said they liked it” is not outcome evidence. “Users completed the primary task 40% faster” or “users no longer needed to re-explain context at handoff” is outcome evidence. Be honest about limitations — an evaluation section that only reports positive results is less credible, not more impressive.
  3. Poster — ready for the Week 16 station. Must clearly state the collaboration problem, describe the tool in one sentence, and make key evaluation evidence visible. Visitors should be able to understand what your project is and why it matters in 30 seconds.
  4. Full final report — a complete written account of the project with four required sections:
    • Technical section: what you built, how it works, key architectural decisions
    • Design section: the user experience decisions and what shaped them
    • Evaluation section: what evidence you collected, what it shows, and what you would test if you had more time
    • Team process section: how the team worked, what the collaboration structure looked like in practice, and a retrospective — what went well, what did not, and three specific things you would do differently
  5. Handoff README — a new engineer should be able to clone your repository and run the project without asking anyone a question. If they would need to ask, the README is not complete.
  6. DECISIONS.md — complete through Phase 3. Must include entries for all significant decisions made during Phase 3, including refinement decisions made after CP2 feedback.
  7. Demo rehearsal artifact — a DECISIONS.md entry confirming that all four team members ran the demo successfully during the Week 15 rehearsal session, and listing any issues found and fixed.
  8. GitHub contributor graph — confirming that all four team members meet the minimum verifiable collaboration outcomes for CP3.

Timing Warning

CP3 is due Week 15 — the guest lecture week. The final report requires contributions from all four team members and consistently takes longer than teams expect. Begin coordinating the report no later than Week 13. The team should agree on a writing schedule before anyone starts building new features in Phase 3.

What Happens After CP3

The instructor will provide written feedback on your final report before Week 16. This feedback will identify the strongest sections and flag anything that needs clarification or strengthening before the final presentation.

Submission

Submit one zip file per group to E3 under “CP3” by the start of class on December 14th. File name: GroupXX_CP3. The zip should contain all deliverables listed above plus a plain text file with the link to your GitHub repository.

← Back to Final Project