User Stories

User story is a way of defining detailed requirements. It’s done with the following template:

As a {role}, I want to {function}, [so that {purpose}]

The third part is optional, because sometimes the purpose is really obvious (e.g., “As an end user, I want to reset my password.")

Capturing User Stories

User stories can be written down on sticky notes or index cards. Their common quality criteria is captured in the Definition of Done, which applies to every user story. If some of them has special criteria, it can be written down on the back of the card.

Usually the business value (or the MoSCoW Prioritization labels), and the estimated size (e.g. in Story Points) are also written on the card.

See Also

• Requirements focus area
• Plans theme

Written by Nader K. Rad

This is (and will be) a work in progress: More details will be added in the future, depending on the feedback.

This wiki is developed and managed by an accredited trainer, independent of AXELOS. While aligned with their guidelines, it’s not an official resource.