User Scenarios and Storyboards

• Instructions
• Grading Rubric

Instructions

For each user story your team specifies, your team must design the user interfaces and interactions that will implement that user story. Your team must document this interaction design with a user scenario and storyboard for each user story.

See the User Stories, Scenarios, and Storyboards - M0 Activity for instructions regarding how your team’s user scenarios and storyboards must be written.

Grading Rubric

• High-Pass: 90% of scenarios and storyboards satisfy all the quality criteria.
• Low-Pass: 70% of scenarios and storyboards satisfy all the quality criteria.
• Fail: Fails to meet requirements for Low-Pass.

Quality Criteria

Looking over the set of scenarios and storyboards written, the instructor will assess how well they satisfy the following quality criteria:

• Scenarios.
  • For each user story, there is a scenario or storyboard.
  • Each scenario fully covers the feature described in the user story.
• Storyboards.
  • For each scenario, there is a storyboard.
  • The storyboard pages have no major data or clickable elements missing.
  • The outcome of interaction depicted (i.e., what the user sees at the end of the interaction with the app).
  • The page URLs that are not overly long or complex. Also, no non-standard Devise URLs.
• Clear and Correct. All scenarios and storyboards are valid and understandable (e.g., nothing confusing or that does not make sense).
• Coherent. Designs are consistent across all scenarios and storyboards (e.g., no storyboards that represent the same pages differently from one another).