User Stories in Interaction Design

  • 1,565 views
Uploaded on

Lecture slides in Interface and Interaction Design course in Tallinn University, 10 February 2011.

Lecture slides in Interface and Interaction Design course in Tallinn University, 10 February 2011.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
1,565
On Slideshare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
18
Comments
1
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. User Stories in Interaction DesignHans Põldoja
  • 2. cbaThis work is licensed under the Creative CommonsAttribution-ShareAlike 3.0 Estonia License. To view a copy ofthis license, visit http://creativecommons.org/licenses/by-sa/3.0/ee/ or send a letter to Creative Commons, 171 Second Street,Suite 300, San Francisco, California, 94105, USA.
  • 3. What are user stories?• User stories are simple, clear and brief descriptions of functionality that will be valuable for real users• User stories are typically used in agile software development methods such as XP and Scrum• User stories build a bridge between the users, designers and the developers
  • 4. Start with paper cards
  • 5. Paper cards• User story• Note(s)• Test cases (on the back side of the card) (Cohn, 2004)
  • 6. ExampleA company can pay for a job posting with acredit card.Note: Accept Visa, MasterCard and AmericanExpress. Consider Discover.Test with Visa, MasterCard and American Express(pass)Test with Diner’s Club (fail)Test with good, bad and missing card ID numbersTest with expired cards (Cohn, 2004)
  • 7. Good user story• Independent• Negotiable• Valuable to users and customers• Estimatable• Small• Testable (Cohn, 2004)
  • 8. Refine the user stories
  • 9. Guidelines• Start with goal stories• Break large stories into smaller pieces• Write closed stories (that finish with completed goal)• Keep the UI out as long as possible• Include user roles in the stories• Write for one user• Write in active voive (Cohn, 2004)
  • 10. Discuss and accept the user stories
  • 11. SCRUM process• User stories are discussed and edited by the users, designers and stakeholders• User stories are accepted by product owners• Enhancement tickets are created from accepted user stories
  • 12. References• Cohn, M. (2004). User Stories Applied For Agile Software Development. Boston, MA: Addison Wesley.
  • 13. Photos• Rool Paap, http://www.flickr.com/photos/roolrool/4468175996/• Paul Downey, http://www.flickr.com/photos/psd/3731275681/
  • 14. Thank You!• hans.poldoja@tlu.ee• http://imkedesign.wordpress.com