agile > chapter 2 launch and planning > 8 user stories

User Stories

This is technique used to describe the requirements associated with a persona. User stories are written from the user's/customer's perspective. They should consist of only the essential information that is required for the work team to build the product to cater for that persona.

User stories consist of:

Writing user stories

One side contains the story text written in the form: As User, I need functionality or attribute for desired result.

On the back of the card, we place the acceptance criteria for the story. These are important because we want our product to not only be functional but also to perform its function very well.


Good user stories are:


As a teacher, I want to be able to tally my students' grades electronically so that I can tally and input them into the reports in a timely manner

Acceptance criteria:

Epics and Themes

An epic is a user story that is too large to be completed in a single iteration - its scope requires too much work effort.

As a teacher, I want to be able to manage all of my classrooms and complete all of my reports and administrative documents.

A theme is a collection of related user stories.

As a teacher, I want to be able to add student grades. As a teacher, I want to be able to delete student grades. As a teacher, I want to manage the list of students in my class.

User stories are not specifications

Specifications are detailed descriptions of requirements and the state of the final product whereas a user story tells us the minimum information about a requirement that is necessary for the work to be started.

User stories are easier to prepare and require less knowledge of the final product.