User StoriesA QUICK GUIDE

What is a User Story

Short, simple description of a feature told from the perspective of a person who desires the new capability (usually a customer of the system)

As a <type of user>, i want <some goal> so that <some reason>

Examples

Epics As a user, i want to backup my entire hard drive

Stories As a admin user, i want to specify files to be backup based based on

file size so that only the ones specifed are backed up

As a admin user, i want to specify folders not to backup so that i can exclude non relevant folders

Bad Examples

As a developer, I want to finalize the database table changes

and additions for the release so that we don’t have to make

changes to the model later.

As a business user, I would like a report of item profitability so

that I can identify and highlight profitable items and consider

what to do about underperforming items.

As the system, I need to store customer account info and their

order lists in the database

Acceptance Criteria

Every User Story should contain acceptance criteria.

Its a way for the product owner to check that the user story is “Done”

Examples: As TOC user i want to search ports by date so that i can find ports

that occured within a particular date range.

Acceptance Criteria:

I am able to select a date range

When i submit the search only ports within the selected date range are visible

When i submit the search, the results show PortID, Port Date and External Reference

When i click “Reset” the form and its results are cleared

INVEST Model

I - Independent

N - Negotiable

V - Valuable

E - Estimable

S - Scalable

T - Testable

References

http://www.mountaingoatsoftware.com/ [Mike Cohn]

http://wikipedia.org

Who am I?

Filipe Louro

Certified Scrum MasterProfessional Scrum Master I

LinkedIn: http://pt.linkedin.com/in/filipelouro/Twitter: @lourofilipe