What a real project looks like at 16
Inside a cohort sprint: scope, standups, and shipping something a stranger will actually use.
The word 'project' does a lot of work in school. It can mean a diorama. It can mean a slide deck. It can mean a group essay where one kid did most of it.
In a cohort, 'project' means something narrower: a thing that a stranger, somewhere, uses on purpose. That definition is the whole game.
Week 1: scope down twice
Every cohort starts with students pitching ambitious ideas. An app for youth mental health. A platform for local musicians. A tool that helps small businesses with marketing.
By Friday of week 1, those pitches have been scoped down twice. The mental health app becomes a text-message reminder tool for one student's grief group. The musician platform becomes a single-page site for one specific open mic. The 'small business tool' becomes a spreadsheet template for one bakery.
That looks like a downgrade. It's not. It's the first time most of these students have picked a scope small enough to actually ship.
Week 2 and 3: standups and mess
Standups happen three times a week. Fifteen minutes. What did you do, what's next, what's blocked. Nobody's allowed to say 'nothing.' If nothing happened, we talk about why.
Most of the messiness happens here. A student realizes their idea won't work as described. A mentor tells them to rewrite the readme. Two students merge their projects. One student quietly starts over.
Week 4: the first real user
The rule is: someone outside the cohort has to use it. Not look at it. Use it. That's when the project becomes real.
The first user always finds something the student didn't test. Always. That moment is more educational than any lecture we could give.
Week 5: writing it up
The last week is the case study. What was the problem, what did you build, what did the user do, what would you change. This is what employers read. It's also, quietly, what teaches the student the most.