This site is from a past semester! The current version will be here when the new semester starts.

tP: Inception [week 4]tP: mid-v1.1 [week 6]


tP: v1.0 [week 5]

  1. Brainstorm user stories before the tutorial
  2. Prioritize the user stories before/during the tutorial

1 Brainstorm user stories before the tutorial

  • Get together with your team members and brainstorm for user stories  for the the product.
    • At this stage, aim to have more user stories than you can deliver in the project. Aim to create at least 30 user stories. Include all 'obvious' ones you can think of but also look for 'non obvious' ones that you think are likely to be missed by other teams.
    • Refer [Textbook Specifying Requirements → UserStories → Usage → (section) Tips] for tips on how to use user stories in this task.
    • You can write each user story in a piece of paper (e.g. yellow sticky note, index card, or just pieces of paper about the size of a playing card). Alternatively you can use an online tool (some examples given in [Textbook Specifying Requirements → UserStories → Usage → (panel) Tool Examples ]).
    • Note that you should not 'evaluate' the value of user stories while doing the above. Reason: an important aspect of brainstorming is not judging the ideas generated.

Recommended: You can use GitHub issue tracker to manage user stories, but for that you need to set up your team's GitHub organization, team repo, and its issue tracker first. Instructions for doing those steps are in the panel below.

Admin Appendix E: GitHub (extract)

2 Prioritize the user stories before/during the tutorial

  • Suggested workflow:
    • Take one user story at a time and get team member opinions about it.
    • Based on the team consensus, put the story (i.e. the piece of paper) onto one of these three piles:
      • Must-Have : The product will be practically useless to the target user without this feature.
      • Nice-To-Have : The target user can benefit from this user story significantly but you are not certain if you'll have time to implement it.
      • Not-Useful : No significant benefit to the target user, or does not fit into the product vision.
    • If you are using physical paper to record user stories: After all stories have been put in the above three piles, you can make a record of which stories are in the three piles.


tP: Inception [week 4]tP: mid-v1.1 [week 6]