U S E R S T O R I E SA Q U I C K G U I D E

W H AT I S A U S E R S T O R Y

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

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

E X A M P L E S

• Epics

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

• Stories

• As an admin user, i want to specify files to be backup based based on file size so that only the ones specified are backed up

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

B A D E X A M P L E S

• 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.

A C C E P TA N C E C R I T E R I A

• Every User Story should contain acceptance criteria.

• Its a way to help the team understand what the customer expects them to deliver.

• Examples:

• As TOC user i want to search ports by date so that i can find ports that occurred 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

I N V E S T M O D E L

• I - Independent

• N - Negotiable

• V - Valuable

• E - Estimable

• S - Scalable

• T - Testable

R E F E R E N C E S

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

• http://wikipedia.org

W H O A M I ?

Filipe Louro

Certified Scrum Master Certified Scrum Product Owner Professional Scrum Master I

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