User Story

By Jack Levy
 ✤ What is User Stor

✤ Basic concepts

✤ Statemen

✤ Characteristic

✤ Why is User Story important

✤ The purpose of User Stor

✤ Who should write it

✤ How to identify User Stor

✤ How to write a good User Stor

✤ 3C

✤ User Story with Story Ma

✤ 3 levels of Story Map

s

What is User Story

Basic Concepts

✤ An Agile method to describe system features from

users POV

✤ A Statement of product requirement

✤ A basic ideas that express users need

✤ A kind of To Do list that determine the steps along

project’ path.
.

What is User Story

Statement

✤ Answer 3 questions

✤ Who? (Users, segments, persona) as Role -> speci

✤ What? (Users expectation) as Action -> uniqu

✤ Why? (Real world result) as Bene t -> realistic

:

fi

fi
c

What is User Story

Template - Example

What is User Story

Characteristics: INVEST
✤ Independent: can tell the story itself, can be completed alone

✤ Negotiable: describe user’ need, should not write strictly.

✤ Valuable: deliver value to user.

✤ Estimable: can be estimated and t into sprint with priorities.

✤ Small: can be nalized within 3-4 days.

✤ Testable: can be tested and con rmed with pre-de ned criteria.
fi
fi
fi
fi

Why is User Story important?

The purpose

✤ Users develop more senses of product over time, so

requirements must adapt to users

✤ User-centric method is a lean process. Thus avoid

writing pages of SRS, rather we need to deliver result
quickly.
.

How to write a good User Story

How to identify User Story

✤ A stand alone step: a face to face meeting with

stakeholders

✤ Product owner with user-centric mindset.

.

How to write a good User Story

How to identify User Story - Steps

1. Understand user’ problems and needs

2. Write them down as User Stories

3. User Stories become source of requirements

4. Details can be lled later, but for User Story, we need

just-enough key points.
fi
.

Why is User Story important?

The purpose - Benefit with Agile
✤ Simple and consistent format which is compatible with
small or big feature

✤ Keep business value by delivering what user needs

✤ Avoid going into details to early and lock teams in one

solution

✤ Provide clarity for teams

✤ Leave rooms for technical function for appropriate teams

.

 How to write a good User Story

Cs

✤ Card: write the essential key sentences with intents. More requirements can be determined into
details later.

✤ Conversation: discussion between teams (product owner, shakeholders…) and possibly

target users to determine the behavior of product.

✤ Con rmation: a step acts as Acceptance Test to con rm satisfaction of user whether or not
the intent is ful lled.

✤ by product owner as Done or Complete

3
fi
fi
fi

How to write a good User Story

Story Map ( )

✤ In order to implant into roadmaps, we need a Story

Map

✤ Story Map reveals the project big picture, allows

arrange and prioritize tasks in backlog

✤ Gives clear view of system architecture

✤ 3 levels: User activities > User tasks > User Stories

.

2
.

How to write a good User Story

Story Map ( )
1. User comes rst

2. Personas as a source of user story

3. Must be created as a team via conversation

4. Simplicity and Consistency

5. Always start with Epics

6. Break Epics into smaller User Stories with more details

7. Add Criteria to Story so you’ll know once condition is ful lled.

fi
.

1
.

fi

How to write a good User Story

Story Map - Example

Understand not only what users THIN

But also what makes them TICK

Thank you!

Jack Lev
UX Superviso
vinhle.nguyen@icloud.com
y