How we can forget a user story if we are speaking about Agile. What is a good user story, how can we differentiate between a user story, epic, feature or task. Who owns the user story creation, grooming, approval and implementation. Many new teams struggle with the idea of writing user stories. Teams often confuse user stories with requirements and tasks. This is the session where we will discuss the basics of user stories, how user stories fit into the overall Agile planning process, and how to write a user story.

1. S P E C I A L T H A N K S T O A L E X K A N A A N

2. WHO IS THIS USER STORY FOR?
As a manager, ……
As a mobile application tester, …..
As cutomer service, …..
“As a <user/role>

3. WHAT DO I NEED?
I want to search for customers by first and last names…
I want to run my test cases …
I want to start an application with the last edit open
I want <goal/feature>

4. WHY DO YOU NEED THIS?
I can better service customers by finding their information
To find any and all errors
I can service the customer faster by seeing the last
transaction right away
so that <benefit/value>”

5. USER STORIES EXAMPLE
“As a
<user>
I want to
<function>
so that
<value>
“As a
<Product Owner>
I want to
<quickly swap images on web pages>
so that
<I can change marketing promos>

6. ACCEPTANCE - ASK MAGIC QUESTION!
When creating tickets –
Ask requestor How Will I know I’ve Done That!?!

7.  Entering better tickets
 WHO,WHAT, WHY and HOW
 User Acceptance criteria (business)
 Testing perspective – Use Case(QA)
 Agree on Definition of READY
 Agree on Definition of DONE

11. 3 C’S OF USER STORIES
Card Conversation Confirmation
Storied are traditionally
written on note cards
Details of a story come out during
conversations with Product Owner
Acceptance tests confirm
the results are what the
requestor wants.

12. EXAMPLES OF ACCEPTANCE - BDD

13. USER STORIES - INVEST
I Independent
● Does not depend on other stories
● Easy to reorder/delete if priorities change
● Makes planning, prioritization, estimation much easier
N Negotiable
● User Story is an initial reminder of a conversation
● It starts by capturing the WHAT, WHY and WHO
● Details of the HOW can be worked out in later conversations
V Valuable ● Adds something useful to customer - (the so that part)
E Estimable ● Must have enough details to allow sizing & prioritization
S Small
● Smaller stories are easier to estimate and work with
● Avoids misunderstanding
● Max size 5 days
● Break down larger stories
T Testable
● Acceptance Criteria must define what it takes to test and the story with sufficient detail
● Acceptance Criteria should not be vague

14. GROUP EXERCISE
What you need
Sticky notes , Markers and pens, A long table
How to do this
Gather the group around a long table and have enough sticky notes at hand
The game:
Imagine your alarm wakes you up at 8:00 AM for work and you need to leave in 30 minutes.
Write down as many different tasks (at least 30) you can think that you will do in the
meantime.

15. Examples are:
• Turning the alarm off
• Getting out of bed
• Turn on the shower

16. Collect all the different tasks and put them horizontally on the table sorted by time.
The left the tasks will be related to getting out of bed and it ends with leaving the house.
Identify the tasks that can be grouped as a theme
Write this down on a different colored sticky note on top of it.
WOW You created an Epic!!!!

17. Select all the tasks that can be done when you have got only 15
minutes of time.
• Place the tasks that are still relevant one level higher.
AMAZING You created priorities!!!!
In round 3 the timescale is 10 minutes and in round 4 it’s only 5 minutes.
FANTASTIC You can re-adjust your priorities based on time left.

18. Lessons learned
• Visualizing all the tasks on sticky notes creates a transparent overview
of all the different tasks that can be thought even with a pretty much
routine activity.
• Limiting the amount of time available forces the team to set priorities
and create different releases.
• Determining the content of the releases stimulates the team to
collaborate and discuss the priorities together.