Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

User stories workshop

2.152 visualizaciones

Publicado el

Library Staff Day in December 2015

Publicado en: Diseño
  • Sé el primero en comentar

  • Sé el primero en recomendar esto

User stories workshop

  1. 1. CONTENTS  What a user story is  Why use them  When and how to  Let’s give it a go!
  2. 2. USER STORIES
  3. 3. JUDGES Paul Tim
  4. 4. A USER STORY IS  A simple tool to focus on user needs  A single statement capturing who, what & why
  5. 5. EXAMPLE As a student, I want to borrow a modern laptop, so that I can work quietly & efficiently.
  6. 6. DATA Data from 2014 Library Client Survey
  7. 7. “User stories don’t make you think about how something will be implemented; instead they focus on the who and the why.” - Boost New Media http://www.boost.co.nz/blog/2010/09/user-stories/
  8. 8. LIBRARY USERS EXAMPLES
  9. 9. LIBRARY STAFF EXAMPLES As a library advisor I want front desk enquiry analysis In order to improve first level resolution
  10. 10. WHY USE THEM User stories help you …  think from the user perspective  generate discussion and collaboration  communicate requirements: • in plain English • without writing detailed documentation • in bite-size pieces
  11. 11. User stories help you …  show value  filter irrelevant content and functionality  drive user research  leave it to the experts to work out the best way of meeting the user need  prioritise and plan work WHY USE THEM
  12. 12. WHEN At the start of a project / initiative
  13. 13. HOW  write them on card/whiteboard  create a digital version
  14. 14. WHAT NEXT? Then deal with the how!
  15. 15. As a (USER) The user makes sure you’re thinking about who will use this feature. If there isn’t an identifiable user for the feature, reconsider whether you need it. COMPONENTS
  16. 16. I want to (TASK) The task or action describes what will happen, but not how it will happen. User stories are designed to start a conversation within the team about the best way to make this feature.
  17. 17. So that (GOAL) The goal describes the ultimate purpose of the feature. If you can’t think of one, it’s a signal that you should reconsider whether the feature you’re trying to describe is actually important.
  18. 18. LET’S GIVE IT A GO! As a (ROLE) I want to (TASK) So that (GOAL)
  19. 19. AT YOUR TABLE Choose one Write table number
  20. 20. ON A SEPARATE NOTE Write your names Write table number
  21. 21. WE COLLECT & SUBMIT Your user story
  22. 22. AFTER LUNCH

×