►
From YouTube: Product Planning: Planning the next milestone
Description
How a GitLab Product Manager uses GitLab in product planning tasks - Planning the next milestone.
A
Hello,
everybody,
I'm,
Amanda,
royda
and
I
am
a
senior
product
manager
at
git,
lab
and
I
want
to
show
you
how
I
dog
food
gitlab
for
my
everyday
processes
from
planning
a
milestone
perspective.
So
I
have
some
other
videos
in
this
playlist
that
show
you
how
I
decompose
an
initiative
and
how
I
search
for
new
features
or
plan
a
little
bit
longer
term.
In
this
specific
video
I'm
going
to
walk
you
through
the
steps
that
I
take
once
a
month
as
a
precursor
to
our
monthly
Milestone
planning
process.
A
A
Are
the
are
the
structure
of
the
epics
and
issues
good?
Do
I,
have
to
add
things
so
for
these
tasks,
as
I
mentioned
I
do
this
monthly
and
it
usually
lasts
about
a
week
a
couple
of
weeks
before
the
Milestone
starts.
I
am
really
leaning
heavy
on
gitlab
boards,
because
boards
give
me
the
flexibility
to
create
lists
and
I
really
like
lists
by
milestone.
A
This
is
typically
the
behavior
I
take
for
all
of
my
issues
or
all
of
my
features,
unless
it's
just
back
at
hubby
like
API
work,
or
something
like
that.
The
reason
why
I
like
to
do
that
is
because
I
can
schedule
them
for
separate
milestones
and
I
can
visually
see
on
that
board.
What's
coming
next,
as
the
team
can
as
well
and
I,
find
that
the
team
likes
to
see
what's
coming
next
right,
I
can
have
separate
assignees
for
each
of
those
and
create
another
board
by
assignee.
A
If
I
want
to
see
what
folks
are
working
on
and
one
of
a
really
nice
benefits
is
I'm
able
to
to
create
blocking
relationships,
so,
for
example,
if
this
design
issue
doesn't
land
in
1511,
I
know
that
it's
blocking
these
two
issues
so
I
have
to
push
these
out
to
the
next
Milestone
or
when
the
design
will
be
shipped.
So
those
are
all
the
reasons
why
I
personally
like
separate
issues,
not
everybody
get
up,
does
that,
but
I
do
and
I
find
it
super
helpful.
A
So,
let's
pop
into
this
eux
board,
these
are
the
things
that
we're
planning
for
the
next
Milestone
1511
and
what
I'm
looking
at
is
have
they
all
been
weighted
and
as
of
right
now
they
haven't
right
now,
there's
a
risk
that
we're
not
going
to
be
able
to
do
all
of
this,
because
this
feature
might
come
in
a
little
heavy.
Having
two
eights,
for
example,
in
a
single
Milestone,
is
a
little
bit
too
much
for
a
single
person.
A
If
I
do
that,
I
might
pull
a
smaller
one
from
a
future
Milestone
into
the
current,
so
I'm
looking
to
make
sure
we
have
the
right
amount
of
work,
then
I'm
also
looking
for
prioritization
of
work,
because
I
ask
my
teammates
to
work
the
boards
from
top
down,
meaning
that
I've
always
put
the
most
important
thing
for
them
to
ship
in
the
top
spot.
So
in
this
case,
actually
the
sort
by
Future
is
the
most
important
and
then
the
the
design
feature.
A
And
lastly,
the
full
screen
feature
so
I'm
looking
for
priority
order
and
then
I'm
looking
at
labels
making
sure
the
right
labels
are
assigned
so
that
they
get
picked
up
by
different
views
and
then
finally
I'm
just
taking
a
look
to
make
sure
nothing
is
blocked.
So
I'm,
taking
a
look
to
see
are
any
of
these
records
blocked
which
not
records,
but
these
issues,
but
typically
this
would
happen.
A
blocking
ish.
A
blocked
issue
would
be
more
on
the
deaf
board
and
not
on
the
design
board.
A
So
I
feel
pretty
good
about
design
next
month.
I
will
come
in
here
and
I
will
do
the
same
thing.
I'm
always
looking
at
the
the
next
Milestone
as
well.
To
make
sure
maybe
priorities
might
have
changed
and
I
might
need
to
swap
some
things
out
based
on
new
needs
of
the
business
and
so
I'm
always
looking
here
and
I
will
make
another
list
coming
up
here
soon,
I
like
to
have
at
least
two
Milestones
out
to
three
Milestones
out.
A
A
So
now
that
I
have
ux
down
I'm
going
to
jump
into
my
Dev
forward
and
from
here
that
I'm
looking
for
similar
things
in
that,
is
it
the
right
things
that
are
scheduled?
Are
they
blocked?
Do
I
expect
that
the
blockers
will
be
lifted
before
the
Milestone
starts?
Do
I
have
weights
do
I
have
the
right
labels
do
am
I
overweight,
I'm,
usually
targeting
for
our
team,
maybe
40
issues
at
this
stage.
A
I
create
that
front
end
and
back
end
at
the
same
time
that
I
create
the
design
and
I'm,
typically
already
adding
it
to
a
milestone.
So
those
features
that
we
see
here
already
went
through
that
process,
so
I
always
have
a
backlog
of
what's
coming.
Next
I
just
might
drag
and
drop
between
lists
on
what's
most
important,
especially
once
I
have
weights
to
determine
okay.
A
A
The
whoops,
the
product
org
here
at
gitlab
create
planning
issues,
and
this
is
the
wrong
one.
Sorry
about
that
and
every
for
every
release.
Every
product
manager
creates
a
planning
issue
which
outlines
for
the
team,
the
stuff
we
want
to
work
on.
So
once
I've
I've
kind
of
firmed
up
my
board
and
I
know
exactly
what
we're
working
on
for
both
Dev
and
and
ux.