How User-Centered Design Can Put User Stories in Proper Context
User stories are a lightweight mechanism for gathering and verifying user requirements on Agile projects. Unfortunately, it is easy to lose the context of stories. Find out how techniques from user-centered design (UCD) can help avoid this problem.
by Jon Dickinson,
Darius Kumana
June 30, 2009
ser stories are probably the most popular tool for gathering user requirements on an Agile project. A user story represents some goal that a user would like to achieve, and collectively, user stories are a lightweight mechanism for gathering and verifying user requirements. Introduced to software development projects through Extreme Programming (XP), user stories have become standard on many Scrum projects.
Figure 1. Example User Story Card: User stories are often handwritten on cards. This example uses the format described in Mike Cohn's User Stories Applied.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
ser stories are probably the most popular tool for gathering user requirements on an Agile project. A user story represents some goal that a user would like to achieve, and collectively, user stories are a lightweight mechanism for gathering and verifying user requirements. Introduced to software development projects through Extreme Programming (XP), user stories have become standard on many Scrum projects.
