Project - Final Project

See also: GradingGrading
See also: Syllabus · Lectures

Tech 1 Grading Plan

Assessment and Grading Breakdown




#
Component
Weightage (%)




1
Attendance and Class... · Lecture 10Lecture 10
How Software Gets Built

The people part: how ideas become products, and how teams avoid chaos.

Hour 1 — The lifecycle

The SDLC: idea → requirements → design → build → test → ship → maintain
...

Brief

In teams of up to 3, take a product idea from concept to a working, deployed web application that a stranger could use — built primarily by directing AI tools — and present it at Demo Day.

The shape of it

• Kickoff (Week 10): form teams, pitch topics, submit a one-page proposal (problem, users, core flow, stack sketch)
• Sprint 1 (Week 11): core flow working end-to-end, however ugly. Live crit.
• Sprint 2 (Week 12): ship-ready — polish, empty/error states, performance and security pass. Feature freeze at end of week.
• Demo Day (Week 13): 7-minute live demo + process story, 3-minute Q&A.

Requirements

1. Deployed and public — a URL, working on mobile, on the day of the demo
2. Has a back-end — stores or fetches real data (database and/or external API)
3. Considered as a product — onboarding, empty states, error states, visual polish
4. Process documentation — your proposal, sprint plans, prompt logs, dead ends, and what you'd do differently
5. You understand your stack — every team member can answer "where does this data live?" and "what happens when I click this?"

An AI feature is encouraged if it earns its place, not required.

Scope advice

The best projects are one small thing that fully works. "Splitwise for hostels" beats "a social network." You will cut scope in Week 11 — teams that pick a small idea get to spend Week 12 on polish instead of triage.

Evaluation