Overview

Today we’re going to focus on how to evaluate how well your projects are meeting the requirements of a hypothetical user. Some of this will be review from early in the term, since it’s time to evaluate how well you have achieved your desired user stories.

Basic Learning Objectives

Before class, you should be able to:

  • Define user story in a computer science context
  • Write out the “equation” commonly used for user stories
  • Evaluate how well your team’s user stories are currently being supported

Advanced Learning Objectives

After class, you should be able to:

  • Explain what a user story is and how it’s used in user-centered design
  • Differentiate between effective and less-effective user stories
  • Turn a user story into a task for usability testing

Readings

To achieve the basic learning objectives, read the following in User Stories Applied (linked on Moodle):

  • Chapters 1 and 2, “An Overview” and “Writing Stories”

Checks

Submit the following to Moodle:

  • What was one of the user stories your team decided on?
  • Now that you’ve read more about user stories, including that they should be “Independent”, “Negotiable”, “Valuable to users or customers”, “Estimatable”, “Small, and “Testable”, how does your chosen user story do on those dimensions? Should it be changed to be better?