Week 5 [from Wed Feb 5 noon] - Tutorial

The goal of this activity is to come up with the smallest possible product that is still usable so that it can be implemented as v1.0. We try to make it small because you will have only two weeks to implement v1.0 and coding as a team is a lot harder than writing code alone.

• If the product can be of some use without a given user story, that user story should be left out of v1.0, even if the omission makes the product hard to use, as long as the product is not impossible to use e.g., in most cases a product can be used without an 'edit item' feature because the user can always delete an item and add a new item instead of editing an existing an item.
• Don't worry about v2.0. You can design v2.0 after v1.0 done.
• Don't worry about v1.0 being 'too small'. You can always add more features to v1.0 if you finish it ahead of schedule.
• If possible, narrow the scope of v1.0 further e.g., narrower target user, a smaller value proposition

Suggested workflow:

• First stage [10 minutes]:
  • Divide the user stories among team members.
  • Each member will go through their user stories to discard (e.g., cross out, or move to a different location, but not delete) which are definitely not needed for v1.0.
• Second stage [10 minutes]:
  • All members discuss the remaining user stories (i.e., the ones not discarded in the first stage), and try to trim the list further.

• Based on your user story selected previously, conceptualize the product in terms of how it will look like at v1.0. Suggestion: this can be in the form of a feature list.