A User Story - some ideas


Published on

Some ideas to explain how a good User Story must be.
Include some good references.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

A User Story - some ideas

  1. 1. A User Story some ideasAntonio de la Torre (@adelatorrefoss) Esta obra está bajo una Licencia Creative Commons Atribución-CompartirIgual 3.0 Unported.
  2. 2. 3 Cs Ron JeffriesCardConversationConfirmation
  3. 3. Card Como <usuario>, quiero <una funcionalidad> para <un beneficio>.
  4. 4. 1.- Card As a <type of user>, I want <some goal> so that <some reason>.
  5. 5. Real Option ManagementNo dar soluciones técnicas definitivas
  6. 6. 2.- Conversation Una historia NO es un requisito
  7. 7. ejemplos iComo Director de MarketingQuiero saber qué se dice en twitter sobre miempresaPara mejorar la imagen si hiciese falta
  8. 8. As a user, I can backup my entire hard drive.As a power user, I can specify files or folders tobackup based on file size, date created, anddate modified.As a user, I can indicate folders not to backupso that my backup drive isnt filled up withthings I dont need saved.
  9. 9. 3.- Confirmation Conditions of satisfaction Definition of Done High-level acceptance test that will be true after the user story is complete
  10. 10. ejemplos iiAs a vice president of marketing,I want to select a holiday season to be usedwhen reviewing the performance of pastadvertising campaignsso that I can identify profitable ones.
  11. 11. Make sure it works with major retail holidays: Christmas,Easter, President’s Day, Mother’s Day, Father’s Day, LaborDay, New Year’s Day.Support holidays that span two calendar years (none spanthree).Holiday seasons can be set from one holiday to the next(such as Thanksgiving to Christmas).Holiday seasons can be set to be a number of days prior tothe holiday.
  12. 12. INVEST Bill WakeI – IndependentN – Negotiable... and NegotiatedV – ValuableE – EstimableS – SmallT – Testable
  13. 13. SMART George T. DoranS – SpecificM – MeasurableA – AchievableR – RelevantT – Time-boxed
  14. 14. Mike Cohn Big User Stories are Epics
  15. 15. Dependency or Definition of Ready
  16. 16. ¿Cuándo se crea? ¿Cuańdo se detalla?US Workshop Backlog Grooming
  17. 17. ¿Cómo se detalla?Se divide Se especifican condiciones de satisfacción
  18. 18. DocumentaciónO lo único que evite riesgosO lo mínimo que estemos confiadosO es para la posteridad
  19. 19. US Template* Como <>, Quiero <>, Para <>* Definition of Ready / Dependency* Solución técnica* Definition of Done / Confirmation / Tests deaceptación
  20. 20. US WorkshopTaller de Historias
  21. 21. User Stories Mind Map
  22. 22. Walking Skeleton
  23. 23. UML - Use Cases
  24. 24. Volere
  25. 25. referenciashttp://xprogramming.com/articles/expcardconversationconfirmation/http://www.mountaingoatsoftware.com/topics/user-storieshttp://www.genbetadev.com/metodologias-de-programacion/historias-de-usuario-una-forma-natural-de-analisis-funcionalhttp://lookforwardconsulting.com/2011/02/07/writing-good-user-stories/http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/http://www.agileproductdesign.com/presentations/user_story_mapping/index.html