►
From YouTube: Product Planning: Finding features to schedule for my team for the next 1-3 milestones in GitLab
Description
How a GitLab Product Manager uses GitLab in product planning tasks - Finding features to schedule for my team for the next 1-3 milestones in GitLab
A
Hey
everybody,
I'm
Amanda,
reeda
I
am
a
senior
product
manager
at
git,
lab
in
the
plan
stage
and
I
want
to
walk
you
through
how
I,
as
a
product
manager,
use
gitlab
for
my
planning
process
in
this
video
I'm
going
to
walk
through
kind
of
higher
level.
How
do
I
find
the
work
that
I
want
to
plan
for
this
Milestone?
Maybe
one
or
two
Milestones
out
and
I
want
to
walk
you
through
that
process.
Where
do
I
find
it?
A
How
do
I
find
it
using
gitlab,
so
I'm
going
to
share
my
screen
here
and
in
a
some
other
videos,
I
showed
you
how
I
break
down
work
and
some
other
tools
that
I
use
in
my
process,
but
here
I'm
a
specifically
targeted
on
how
do
I
find
the
work
that
I
want
to
plan
for
the
next
Milestone?
Maybe
the
next
two
or
three
Milestones
so
I
have
a
few
different
kind
of
methods
when
I'm
working
on
a
big
project,
I
like
to
create
a
single
epic
that
groups
everything
related
to
that
project.
A
So
in
this
case,
we
are
working
on
an
initiative
called
work
items
and
once
it
ships
I
am
going
to
be
migrating.
The
current
epic
experience
to
the
work
item
experience
in
order
to
do
that.
I
want
to
keep
track
of
all
the
moving
Parts,
because
there's
a
lot
that
goes
with
that
actual
migration,
so
I've
created
a
table
for
myself
in
this
epic.
A
It's
not
something
you
have
to
do,
especially
because
it's
a
markdown
table
and
not
everybody,
buddy
loves
markdown,
but
I
personally,
love
tables,
and
especially
because
the
tasks
or
the
kind
of
subset
features
that
I
need
to
get
scheduled
for
migration
is
actually
going
to
be
done
across
several
groups
here
at
gitlab,
and
so
this
gives
me
a
quick
view
of
who's
owning
what
and
if
there's
something
that
anybody
can
own.
We
can
easily
update
that
and
we
can
see
a
quick
status.
A
There
is
overhead
of
creating
a
static
table
like
this,
so
you
might
want
to
instead
just
focus
your
your
views
in
the
child
and
related
epic.
So
here
we
can
see
things
that
are
directly
related
to
the
migration.
Are
children
of
this
epic
and
things
that
are
laterally
related
because
they
might
have
a
different,
direct
parent
but
block
this
initiative
are
all
listed
here,
so
every
Milestone
before
the
Milestone
starts
I'm
looking
for
okay?
Well,
what's
in
the
backlog,
does
it
make
sense
to
start
bringing
one
of
these
things
in?
Because
this
is
an
initiative?
A
But
this
is
still
a
little
bit
too
much
for
me.
I
want
to
narrow
this
down
a
little
bit
more
and
I
know
that
as
I
am
reviewing
work.
Anything
that's
important
to
me
for
this
fiscal
year.
I
am
marking
with
this
label
fy24,
and
so
now
I
can
get
just
those
that
I've
already
triaged
and
earmarked
for
this
year
and
I
can
look
to
see
what
I
need
to
burn
down
so
from
here.
I
can
go
ahead
and
open
up
to
find
eligible.
A
For
example,
if
ordering
issues
and
issue
boards
is
not
blocked
by
anything,
I
can
start
scheduling
these
issues,
so
this
is
another
way
that
I
can
find
things
that
I
want
to
schedule
in
upcoming
Milestones
now
I'll
just
mention
that
we
have
some
new
functionality
here,
that's
being
displayed
with
colors.
You
may
want
to
organize
yourself
using
epic
colors.
Maybe
do
it
by
time
like
order
of
not
time
but
priority.
So
you
know,
Reds
are
the
first
thing:
you're
gonna
are
going
to
schedule.
A
Yellows
are
the
next
and
so
forth
and
to
change
the
colors.
Currently,
you
would
do
that
in
the
Epic
itself,
so
you
would
come
here
within
the
Epic
and
change
the
color.
Accordingly,
we
will
be
adding
features
so
that
you
can
change
it
right
from
this
view
in
the
future.
Okay
and
another
place,
I
like
to
find
things
when
I'm
looking
for
issues
or
work
to
prioritize
is
in
the
board
when
I'm
looking
at
the
board.
I
have
several
views.
A
A
A
So
I
I
like
to
come
to
the
issue
list
and
sort
it
by
my
group
and
then
sort
it
by
feature
which
we
use
a
label
for
and
then
sort
it
where
the
author
is
not
me
because
I
know
what
I've
created
and
when
I
create
an
issue.
I
will
typically
add
a
milestone
to
it
or
earmark
it
accordingly
and
then
I
will
sort
this
result
set
by
create
date,
so
that
I'm,
seeing
all
the
new,
the
latest
stuff
that's
been
created
by
other
people,
I'm
typically
watching
this
as
they
get
created.
A
But
you
never
know
something
might
sneak
by
me,
and
so,
if
I
find
something,
that's
interesting
that
I
didn't
realize
was
an
opportunity
for
us.
I
might
open
that
up
and
and
break
that
down
into
or
create
an
epic
click
for
it
and
then
break
it
down
into
smaller
parts
and
get
it
scheduled.
So
these
were
just
a
couple
of
tips
of
how
I
find
work
when
I
am
scheduling
work
for
my
next
one
to
three
Milestones
hope.
This
is
helpful
for
you
and
thanks
so
much
for
your
time.