Preview
Video Player
00:00
00:00
The Product Backlog and Sprint Backlog
2:54The Product Backlog feeds into the Sprint Backlog. Items are taken from the top of the Product Backlog, where they have the highest priority, and are accepted into a Sprint.
So now we have a bunch of user stories and
0:00
other product backlog items
that the team will work on.
0:02
Where do they go?
0:06
How do we organize them?
0:07
We keep these items in
the product backlog.
0:09
The product backlog is an ordered list
of all the items the team might work on.
0:12
The highest priority items are at the top,
and
0:16
the lower priority items
are further down the list.
0:19
There are many digital tools that allow
you to maintain an ordered list for
0:23
your product backlog.
0:26
But many teams find it easier to start
with the simplest tools available.
0:28
Large index cards.
0:32
A team can set up their space with
the product backlog taped to the wall for
0:34
everyone to see.
0:38
Use painter's tape to attach the cards to
the wall, because it's safe to attach and
0:39
remove the tape.
0:44
Otherwise, you may find
yourself in trouble
0:45
when you remove a product backlog item,
and take a piece of the wall with it.
0:48
Maintaining the product backlog is one of
the responsibilities of the product owner.
0:52
The product owner makes
sure each piece of work for
0:57
the team is captured by
a product backlog item.
0:59
These don't necessarily start out
as fully formed user stories.
1:02
Sometimes you just need to get an idea,
like export to .CSV.
1:05
And then later,
1:11
work them into user stories that
are small enough to include in a sprint.
1:11
The product owner also maintains
the priority order in the backlog.
1:15
An advantage of a product
backlog that is printed on cards
1:21
is that it lends itself to sorting.
1:24
The product owner can hold
two items in their hand and
1:26
ask themselves the question,
which of these has a higher priority?
1:29
By repeating this question and comparing
items in sequence, higher priority items
1:34
bubble up through the list,
while lower priority items move lower.
1:38
When the product backlog is on
the wall for everyone to see,
1:43
it provides transparency to the team,
and even to the organization.
1:45
Everyone can see what
the team will be working on.
1:51
A common question is, when is
the product gonna have this feature?
1:53
With a visible product backlog,
1:58
stakeholders can see where each
feature sits in the product backlog.
2:00
They can talk to the product owner
if they think a particular item
2:04
deserves a higher priority.
2:07
The product owner is constantly
trying to gather information
2:09
about the priority of
items in the backlog.
2:13
They have conversations with stakeholders,
customers, support representatives, and
2:16
anyone else who can help them
understand the value and
2:20
priority of items in the backlog.
2:24
As we learned in sprint planning,
2:26
the products backlog feeds
into the sprint backlog.
2:28
Items are taken from the top
of the product backlog where
2:32
they have the highest priority and
accepted into a sprint.
2:35
A team can set aside space on the wall for
2:39
the sprint backlog where they can easily
see all the items of the current sprint.
2:41
Having the sprint backlog visible is
very important during the sprint,
2:46
as we will learn shortly when
we look at the task board.
2:50