Home / Sprint 3 / Build v2

Build v2 AB IS

Sprint 3 · Due · 10 points

v2 is not about being finished. It's about showing that you used feedback to make a deliberate change. The demo next week asks: where did you start, what changed your thinking, and what exists now? v1 → Review → v2 is that arc made visible.

— Prof. Sathya

What to Submit

Three things:

  1. Link or screenshot: Your revised build. Same format rules as v1 — deployed link, prototype, mockup, photo. Show the current state.
  2. What changed from v1: Point to the specific change(s) you made. What does v2 do that v1 didn't? Or what did you remove/simplify?
  3. One remaining limitation: Something you'd address with more time. This shows you're still thinking critically about your design, not just declaring victory.
▶ Go Deeper

What makes a strong v1 → v2 arc

The change should be traceable. Someone should be able to look at v1, read your review, and see exactly why v2 looks different.

Preparing for Week 11

Piranavan sees your build this time (not just your stake). He'll react to what you actually made. A peer will role-play your user. What would break if someone actually tried to use this?

Submit

Link or screenshot + what changed + one remaining limitation. Submit via Canvas.

Format: Link/screenshot + written text in Canvas submission
Due:
Points: 10
Submit on Canvas →