Paul Hutton - Making User Stories Work for Your Product
•Als PPTX, PDF herunterladen•
0 gefällt mir•24 views
Paul Hutton Presentation for Agile Impact Conference 2018 Day 1. "Making user stories work for your product"
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Paul Hutton - Making User Stories Work for Your Product
Ähnlich wie Paul Hutton - Making User Stories Work for Your Product (20)
Mehr von Agile Impact
Mehr von Agile Impact (19)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Paul Hutton - Making User Stories Work for Your Product
- 1. Presenter PAUL HUTTON Principal Consultant, Ekipa Singapore Making User Stories Work for Your Product Agile Impact Indonesia 19 Sep 2018
- 2. ABOUT ME
- 4. Agenda Why User Stories? Origins of User Stories Identifying User Stories for a Product Content and required elements for a User Story? Gaps in User Stories and how to fill them Definition of Ready (DoR) Practice writing User Stories! Q & A (if required and time permits)
- 6. Why User Stories? • “A User Story is an invitation to a conversation” • Written in simple, non-technical language • Concise enough to be written on an index card • Eliminates the need for “Big Requirements Up Front!”
- 8. Origins of User Stories • Referenced in Extreme Programming (1996) (Beck, Jeffries, Cunningham) • Contributions by Alistair Cockburn (1998) • “Three C’s” – Ron Jeffries (2001)
- 10. Definition of a User Story Created using the following method (known as the 3 C’s): Card Conversation Confirmation
- 11. Definition of a User Story 1. Description “As a <who> I want to <what> so that <why>” 2. Acceptance Criteria Used to identify test cases for each story Confirms that the story is “done” in the product demo
- 13. Start with User Personas
- 14. Identification of the User Stories
- 16. What’s missing from User Stories? Q: What additional information should be added to a User Story to make it fit for design, development and testing? A: The User Story definition does not include any information that describes or illustrates the User Interface!
- 17. DoR
- 18. Definition of Ready (DoR) • Ensures that only well-defined User Stories can enter the Sprint Backlog • Can also include the use of “INVEST” I = Independent N = Negotiable V = Valuable E = Estimable S = Small T = Testable
- 20. Let’s Practice Writing User Stories!
- 22. Further Learning • User Story Mapping (Jeff Patton) • User Stories Applied for Agile SW Development (Mike Cohn) • Attend an Ekipa Agile Workshop!