User Stories

In gathering and specifying the requirements for your app, you will create a set of user stories (USs).

Your team will be provided a stories spreadsheet into which you will enter your USs. Your team should have only one stories spreadsheet that is shared by all team members. Columns of the spreadsheet must be filled out as follows:

• Category: The category column may contain labels of your choosing that help you group and organize your USs.
• ID: The ID must be of the form US01, US02, US03, etc., and each user story must have a unique ID. Don’t change a US’s ID once a valid ID has been assigned, and don’t worry about sorting user stories by ID.
• Title: The title must follow the verb/noun template discussed in class.
• Description: The description must follow the who/what/why template discussed in class.
• How App Supports: A high-level description of how the user interacts with the app in order to fulfill the user story. Note that this piece necessarily includes some design decisions about the app’s interface (unlike the US description).
• Status: The status must be one of the following:
  • Not started
  • In progress
  • Complete

---

Grading Rubric

Scored out of 20 possible points.

Half of the points (up to 10) will be awarded based upon the percentage of stories that are free from defects, including (but not limited to) the following:

• One or more US fields are missing/invalid/unclear/out-of-date
• Failed to follow title and description templates
• Story is too big
• Story is not a functional requirement (e.g., it is a non-functional requirement)
• Not customer-oriented (e.g., contains technical jargon)
• Includes design or implementation details
• Story is redundant with another story

For example, if there are 42 stories, and 12 of them contain one or more of the above defects, then the points will be calculated as 10 * (30/42) = 7 points (rounded to nearest whole number).

The other half of points (up to 10) will be awarded based on the grader’s assessment of how complete the set of user stories is. For example, if the grader finds that only a couple USs were omitted, a small deduction (e.g., -1) might be taken; however, if the grader finds that a larger number of USs were omitted, a larger deduction (e.g., -4) might be taken.