Writing Stories


Purpose

The purpose of this exercise was to learn how to write user stories.

Description

The groups were given a one-page description of a course-scheduling application and were asked to write all the stories for this application. They were told to take turns, with one person at a time writing a story while the others asked questions and made sure the story was estimable and testable. The time limit for the exercise was 45 minutes.

Events

They wrote the stories just as if they knew how. By this time, the groups were much more relaxed and were even having fun.

The exercises tend to build on one another what you learn in one exercise is used and reinforced by the other exercises. In the previous exercises, the participants learned to think about acceptance testing and estimation. They also made a strong correlation between story "quality" and the ability to do acceptance testing and estimating. The participants knew the difference between a good story and a story that needs work.

At the end of the time limit, the groups shared their stories. Different groups had very different ideas about the systems that they would be implementing. Some groups were writing the stories for a batch system. Some groups wrote stories for an interactive Web-deployed system. The one-page description we gave them didn't specify any type of user interface, so they were free to do anything they liked.



Extreme Programming Perspectives
Extreme Programming Perspectives
ISBN: 0201770059
EAN: 2147483647
Year: 2005
Pages: 445

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net