User stories session - Agile Jordan

2. What are
User Stories?

3. A User Story is a short
description of a
feature told from the
perspective of a user

4. Why User
Stories?

5. Traditional Requirements: a comprehensive
description of what should be delivered
Traditional requirements are usually created by a few
people, while user stories are discussed between the
whole team

6. Problem definition
Personas
Journey maps
Assumptions
…etc.
Before writing user stories

7. Discussing
Features > Writing
Features
“Individuals and interactions over processes and tools”

9. When I say “Mary had a little Lamb” What do you Imagine?

10. “Mary had a little Lamb”

11. Who are
the users?
Before writing User Stories

12. Question
As a customer,
What features would you like to have ?

13. As a customer
I want to have an online food delivery service
So that I won’t have to leave the office midday
As a customer
I want to be provided with online payment options
So that I save time while paying for food orders

14. As a compliance team member
I want to make sure users agree to terms and conditions
So that we are less likely to get sued
As a member of integration team
I want the service to be secure
So that we maintain confidentiality

15. How to capture what customers
need and why they need it?
The WHO, WHAT and WHY

16. Assumptions vs. Facts
Assumptions are What we Think we Know
Facts are What we Know

18. How do we know a
User Story is
complete?

19. DoR: Definition of Ready
Used to determine
whether work is ready
to be started

20. ndependent
egotiable
aluable
stimable
mall
estable
INVEST
Criteria

21. A User Story should be: Independent

22. A User Story should be: Negotiable
“A User Story is
a promise of
conversation”

23. Each user story should be:
Valuable

24. A User Story Should be:
Estimable
Is the destination in a different
country?
What is the transportation method?
We can’t provide an ETA without
having some kind of clarity

25. A User Story Should be: Small

26. “I want fast food delivery”
How can we test this?
A User Story Should be: Testable

27. DoD: Definition of Done
Example: Preparing Burgers
• Vegetables should be washed
• Vegetables should be cut
• Meat should be cooked
• All ingredients should be layered between
the buns

28. Question
Share with us DoDs you use at work

29. The DoD
we all
miss

30. Acceptance Criteria
Test Scenarios that
are to be met to
confirm that the
software is working
as expected

31. Acceptance Criteria versus DoD
Each User Story has its own Acceptance Criteria
All user stories have the same DoD

32. DoD, DoR and Acceptance
Criteria evolve as we know
more about the product

33. Connect with Agile Jordan !
Agilejordan.org
linkedin/facebook/Instagram/Meetup
Connect with me on Linked In!
linkedin.com/in/dimaazazi