What counts towards your grade
Bookmark this page. It covers everything that is assessed, when it is due, and where it goes.
Final grade = Team performance (70%) + Individual contribution (30%)
Graded deliverables — full semester
Section titled “Graded deliverables — full semester”| Deliverable | Due | Where to submit | Portfolio section |
|---|---|---|---|
| Smart Product Challenge video (3–4 min, Weeks 1–2) | April 10, 23:59 | LMO | — |
| Project Brief (2-page Word doc) | Initial: March 27, 23:59 · Lock: April 10 | LMO Turnitin — group leader submits | Portfolio (5%) |
| Dev Log (7 weekly entries, Weeks 3–9) | Updated weekly · submitted Week 11 | Team SharePoint document — link shared with pathfinder | Group Reflection & Dev Log |
| Technical Documentation (6–9 pages) | Week 11 submission | LMO | Portfolio |
| Validation Report (4–6 pages) | Week 11 submission | LMO | Portfolio |
| Group Reflection (150–250 words) | Week 11 submission | Appended to Dev Log, submitted via LMO | Portfolio |
| Peer Evaluation Form | Week 11 submission | LMO | Individual contribution (30%) |
| Demo Day presentation (6 min + 4 min Q&A) | Week 10 session | Live — no submission | Assessed on the day |
Checkpoints (formative — not directly graded, but evidence-based)
Section titled “Checkpoints (formative — not directly graded, but evidence-based)”Checkpoints are not marked separately, but the evidence you bring directly feeds your portfolio and your pathfinder’s assessment of your individual contribution.
| Checkpoint | Window | Prep document due |
|---|---|---|
| Checkpoint 1 | Weeks 4–6 | 24 hours before your booked slot |
| Checkpoint 2 | Weeks 7–9 | 24 hours before your booked slot |
See Pathfinder Checkpoints for the exact questions your pathfinder will ask.
What the Dev Log must contain
Section titled “What the Dev Log must contain”Your Dev Log is the backbone of your portfolio. Every entry must have:
- Names — who contributed, not “the team”
- Evidence links — GitHub commits, Figma files, interview notes, test recordings
- Individual contribution — 30–50 words per person, written by that person
- Traffic light status — 🟢 🟡 🔴 + one honest sentence
A Dev Log entry without evidence links is not an entry — it is a paragraph of claims.
What each portfolio document requires
Section titled “What each portfolio document requires”Technical Documentation (6–9 pages)
Section titled “Technical Documentation (6–9 pages)”⬇ Download template — save a copy to your team folder and start filling it in from Week 6.
- System architecture (diagram + explanation)
- Technology choices and why (not just what)
- Deployment guide — someone else could set it up from your instructions
- IP Strategy section
- Limitations and future work
Validation Report (4–6 pages)
Section titled “Validation Report (4–6 pages)”⬇ Download template — see the Validation Guide for how to run and document your sessions.
- Research methodology — how you recruited, what you asked
- User findings with direct quotes and data
- Iteration history — what you built, what users said, what you changed
- Evidence appendix — interview recordings, notes, screenshots
Group Reflection (150–250 words)
Section titled “Group Reflection (150–250 words)”- What worked, what did not, what you would do differently
- Written collaboratively — not one person’s voice
The path from weekly work to final grade
Section titled “The path from weekly work to final grade”Week 3–4 Project Brief + roles + MoSCoW ↓Weeks 4–6 Sprint 1 → commits + Kanban + Dev Log entries ↓Week 5–6 User interviews (Stage 1 → Stage 2) ↓ Checkpoint 1Weeks 6–8 Sprint 2 → more commits + usability tests ↓Weeks 7–9 Technical Documentation draft + Validation Report draft ↓ Checkpoint 2Week 9 Portfolio assembly — all evidence linked ↓Week 10 Demo Day ↓Week 11 Final portfolio submissionThe teams that score well are not the ones who built the most complex product. They are the ones who documented their decisions, tested with real users, and have evidence for every claim.
Was this page helpful?