Sprint Cycles

Each sprint is a full build-measure-learn loop, run in teams. The cadence: the class directs an inquiry; your team frames a testable hypothesis and a discovery plan; you build the smallest artifact that can generate evidence—a prototype, a landing page, a concierge test, whatever the hypothesis demands; you put it in front of real people (aim for at least 10 genuine customer conversations or user tests per sprint—synthetic users can sharpen your instrument, but they never count as evidence); and you report at a pin-up.

Pin-up reports follow the four questions: What did we initially think? What did we do? What did we learn? What will we do next? The presentation limit is 3.5 minutes, hard stop, with the artifact visible, then crits. We critique using “I like / I wish / What if”—every comment starts with one of those three stems.

Grading is process-over-product, per the rubric in each sprint’s eLC folder: sharpness of the hypothesis, quality and honesty of evidence, responsiveness of the iteration, and clarity of the report. A failed hypothesis with clean evidence outscores a polished demo with none. A pivot backed by data is a win, not a retreat.

Sprint 2: independent work and presentations

Thursday, October 8: Put about an hour into your project independently. Each student should post a progress update or questions in the project channel that day and @mention John.

Tuesday, October 13: Have your presentation deck/site ready by 1:00 p.m. (13:00). The presentation limit is 3.5 minutes, hard stop.

Cover a short benefit-focused pitch, entrepreneurship progress, AI/development progress, and one or two next priorities in each area. Practice with a timer; aim for two clean runs under the limit.

---

Source: Fall 2026 course syllabus — Sprint Cycles, copied October 6, 2026.

Presentation timing and Sprint 2 directions updated from John’s October 6 course announcement.