How to effectively capture requirements with simple User Stories. This particular Deck is from the http://www.socaldotnetarchitecture.org/ group

1. @isidore_us
Capturing Requirements
with User Stories
By Llewellyn Falco

2. @isidore_us
Requirements Suck!
What everyday
household object
is this?
Top
Side
Front

3. @isidore_us
Requirements Suck!

4. @isidore_us
Requirements Suck!

5. @isidore_us
Requirements Suck!

6. @isidore_us
Exercise #1
Scrabble
Requirements

7. @isidore_us
Exercise #1.5
Scrabble
Story
Rules: The story must be told such as it
is believable that you actually saw it.

8. @isidore_us
Exercise #1.5
Scrabble
Story

9. @isidore_us
Requirements Suck!
So why do we use them?

10. @isidore_us
rules for
User Stories
Be Specific
Outlaw Conditional Words: If, maybe,
sometimes, usually, could be, either,
might
Richer Use Cases: while short, stories
don’t need to be artificially short

11. @isidore_us
Exercise #2
Web
Story

12. @isidore_us
real world example
SmartCare (Zambia)

13. @isidore_us
real world example

14. @isidore_us
real world example
SmartCare (Zambia)
There is a 38 year old woman named
Mary Pari, she is suspected of having TB
3 Swabs -, +, +
suspicion is confirmed
HIV-
Weight 46 Kgs
Is given the following Prescription:
[standard chart]

15. @isidore_us
Exercise #4
SQL Query
Story

16. @isidore_us
Exercise #3
Application
Story

17. @isidore_us
Contact
Llewellyn Falco
info@spunlabs.com