Heads up! To view this whole video, sign in with your Courses account or enroll in your free 7-day trial. Sign In Enroll
Preview
Start a free Courses trial
to watch this video
User stories are special Product Backlog Items. They are called “stories” because they tell you about more than just how a feature behaves, but also about what is happening for the user.
User Story
The value of the user story is defined by who user is, what they need, and why they need it.
As a ______,
I need _____,
so that ____,
Related Discussions
Have questions about this video? Start a discussion with the community and Treehouse staff.
Sign upRelated Discussions
Have questions about this video? Start a discussion with the community and Treehouse staff.
Sign up
[MUSIC]
0:00
Now that we've covered the who,
what, when and
0:04
where of Scrum, we just have a few
details left, the why and the how.
0:08
We'll learn about how the product
backlog and user stories,
0:12
help the team understand why they
are doing what they are doing.
0:16
We'll also learn about other tools
used by the team in the sprint.
0:20
These tools are sometimes
referred to as Scrum artifacts,
0:25
because they are visible to the team and
people outside the team as well.
0:29
So far, you may have noticed that
we've used the terms user story and
0:33
product backlog item in ways that
have seemed almost interchangeable.
0:38
The truth is there is a distinction.
0:43
The term product backlog item is
a general term to refer to anything in
0:45
the product backlog.
0:49
A product backlog item can refer to a bug
or a defect, a piece of technical work,
0:51
a feature request or even large,
poorly defined items that need to be
0:56
broken down into smaller items,
sometimes called epics.
1:01
User stories, on the other hand
are special product backlog items.
1:05
They don't simply describe a feature or
a bug.
1:09
They are called stories, because they
tell you about more than just about how
1:12
a feature behaves, but
also what is happening for the user.
1:16
The value is always clear and
1:19
it's always described from
the point of view of the user.
1:21
Here's a template that is very helpful
in constructing a user's story.
1:24
It consists of three parts.
1:28
As a blank, I need blank, so that blank.
1:30
The value of the user story is defined
by who the user is, what they need,
1:36
and why they need it.
1:41
For example, if we were
constructing an interactive lesson,
1:42
we might write a user story for
English language learners.
1:46
As an English language learner,
I need to see the definition of a word
1:49
when I tap on it, so that I can
understand new vocabulary words.
1:54
Crafting a user story that effectively
conveys these three parts, takes practice.
2:00
So here are some tips.
2:05
To really focus on why you are writing
this user story rather than just on
2:07
a feature or requirement,
start with the so that part of the story,
2:12
then you can fill in the details of who
the user is and what exactly they need.
2:17
As you fill in the additional detail,
you can check to
2:22
make sure you are still describing
a single story and that it makes sense.
2:25
Here's another example.
2:30
Let's say,
2:32
we have a survey tool and we find that
users aren't completing the survey.
2:33
By talking to the users,
2:37
we find out that many only get part
of the way through the process.
2:38
But then they give up, because they
don't know how much longer it will take.
2:42
We want to help with that, so we write
a user story starting with the so that.
2:47
So that I know I'm almost done and
2:52
I don't give up is a clear statement
of the value of the user story.
2:54
We want a user taking a survey to be able
to see where they are in the survey and
2:59
be motivated to finish.
3:04
Now, I can think about
what the user needs.
3:06
I need a progress indicator for
the survey.
3:09
And finally, who needs it?
3:13
As a survey-taker.
3:15
As you can see, user stories are different
from other types of backlog items,
3:18
because they focus on
the value to the user.
3:23
It is intentional for user story to
steer clear of detailing a solution.
3:25
In Scrum, the team has flexibility
in finding a solution, so
3:30
long as it meets the described
need in the user story.
3:33
A user story is simply describes the need
the user has and who the user is.
3:37
Let's review the three
parts of the user story.
3:42
As a blank, I need blank, so that blank.
3:45
If you're a product owner,
you'll have a lot of practice crafting and
3:50
defining user stories.
3:54
If you're a development team member,
you'll learn to decompose stories and
3:56
ask clarifying questions to ensure that
your team has a shared understanding
4:00
of what value you will deliver and why.
4:05
You need to sign up for Treehouse in order to download course files.
Sign upYou need to sign up for Treehouse in order to set up Workspace
Sign up