This document discusses user stories and provides guidance on properly structuring them. It emphasizes that a user story should follow the three C's - Card, Conversation, Confirmation. The Card outlines who wants what functionality for what benefit. The Conversation explores the details of the desired functionality. The Confirmation defines tests or acceptance criteria. The document also references several standards for writing effective user stories like INVEST, SMART, and definitions of done.

1. A User Story
some ideas
Antonio de la Torre (@adelatorrefoss)
Esta obra está bajo una Licencia Creative Commons Atribución-CompartirIgual 3.0 Unported.

2. 3 C's Ron Jeffries
Card
Conversation
Confirmation

3. Card
Como <usuario>,
quiero <una funcionalidad>
para <un beneficio>.

4. 1.- Card
As a <type of user>,
I want <some goal>
so that <some reason>.

5. Real Option Management
No dar soluciones técnicas definitivas

6. 2.- Conversation
Una historia NO es un requisito

7. ejemplos i
Como Director de Marketing
Quiero saber qué se dice en twitter sobre mi
empresa
Para mejorar la imagen si hiciese falta

8. As a user, I can backup my entire hard drive.
As a power user, I can specify files or folders to
backup based on file size, date created, and
date modified.
As a user, I can indicate folders not to backup
so that my backup drive isn't filled up with
things I don't need saved.

9. 3.- Confirmation
Conditions of satisfaction
Definition of Done
High-level acceptance test that will be true
after the user story is complete

10. ejemplos ii
As a vice president of marketing,
I want to select a holiday season to be used
when reviewing the performance of past
advertising campaigns
so that I can identify profitable ones.

11. Make sure it works with major retail holidays: Christmas,
Easter, President’s Day, Mother’s Day, Father’s Day, Labor
Day, New Year’s Day.
Support holidays that span two calendar years (none span
three).
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 to
the holiday.

12. INVEST Bill Wake
I – Independent
N – Negotiable... and Negotiated
V – Valuable
E – Estimable
S – Small
T – Testable

13. SMART George T. Doran
S – Specific
M – Measurable
A – Achievable
R – Relevant
T – Time-boxed

14. Mike Cohn
Big User Stories are Epics

15. Dependency or Definition of Ready

16. ¿Cuándo se crea? ¿Cuańdo se detalla?
US Workshop Backlog Grooming

17. ¿Cómo se detalla?
Se divide Se especifican
condiciones de
satisfacción

18. Documentación
O lo único que evite riesgos
O lo mínimo que estemos confiados
O es para la posteridad

19. US Template
* Como <>, Quiero <>, Para <>
* Definition of Ready / Dependency
* Solución técnica
* Definition of Done / Confirmation / Tests de
aceptación

20. US Workshop
Taller de Historias

21. User Stories Mind Map

22. Walking Skeleton

23. UML - Use Cases

24. Volere

25. referencias
http://xprogramming.com/articles/expcardconversationconfirmation/
http://www.mountaingoatsoftware.com/topics/user-stories
http://www.genbetadev.com/metodologias-de-programacion/historias-de-usuario-una-forma-natural-
de-analisis-funcional
http://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