►
Description
How a GitLab Product Manager uses GitLab in product planning tasks - Using a "Now-Next-Future" epic board to create a product roadmap.
A
Hey
everybody
I'm
Amanda
I
am
the
product
manager
with
product
planning
here
at
gitlab
and
I
want
to
show
you
how
I
use
epic
words
when
I'm
doing
longer
term
planning
so
in
a
prior
video
I
showed
you
how
I
use
issue
boards
to
track
my
milestones
and
or
to
plan
for
my
Milestones
when
I'm
thinking
about
when
I'm
thinking
about
a
little
bit
longer
term
I
use
an
epic
board
which
is
configured
by
labels
that
I've,
created
and
I
applied
to
my
epics
now
next
or
future,
and
basically,
what
we're
looking
at
is
now
are
the
things
that
I'm
hoping
to
accomplish
or
burn
down
in
the
current
Mile
in
the
current
quarter.
A
A
What
I
like
about
this
View
you
first
of
all
when
I
am
planning
for
the
next
Milestone
I
might
pop
in
here
and
look
at
the
Now
list,
because
I
I
might
look
at
okay.
Well,
what
are
we
almost
done
with
this
one's
at
90,
for
example?
Let's
just
pour
some
concentrated
effort
into
this
one,
so
we
can
close
it
out.
What
are
we
really
lagging
behind
on
that
sort
of
thing?
A
So
I
really
like
this
view
to
see
at
the
feature
level
or
the
larger
project
level,
to
see
kind
of
how
we're
doing,
but
then,
when
I'm
thinking
about
the
the
high
level
goals
that
I
want
to
accomplish
this
year,
I'm
grouping
these
kind
of
themes
in
these
kind
of
chunks
of
time.
A
It's
not
a
committed,
like
delivery
plan
that
you
would
use
the
actual
roadmap
for
with
starting
end
dates,
it's
more
of
kind
of
developing
that
product
roadmap
According
to
some
sort
of
loose
time
frames,
and
it
allows
me
to
see
okay,
how
realistic
am
I
with
you
these
plans.
So,
for
example,
the
next
up
I
have
48
epics
with
over
205
weight,
which
not
all
of
this
is
weighed
so
because
we
haven't
even
gotten
to
plenty
breakdown
yet
so
I
already
know,
this
is
really
loaded
right.
A
So
my
next
step,
I'm
gonna,
have
to
really
trim
down,
and
what
I
like
about
using
this
is
I
can
start
to
think
about
as
I'm
thinking
about
each
of
these
things,
I
can
drag
and
drop
and
I
could
say.
Okay
well
relationships
is
the
number
one
priority
for
me,
but
this
this
new
filtering
by
option
due
date
is
also
high
and
then,
if
I'm
doing
this
exercise
of
kind
of
Stack
breaking
each
thing
against
itself,
I
end
up
with
a
bottom
right.
A
So
at
some
point
I'm
going
to
have
the
last
48,
you
know
the
48th,
epic,
or
you
know
the
bottom
20
epics,
and
that
can
really
force
me
to
make
a
decision
about
what
is
the
most
important
in
terms
of
relative
priority.
So
I
can
do
things
like
to
use
the
rice
framework
to
determine
what
the
best
value
is
or,
for
example,
these
first
two
are
part
of
a
larger
initiative
that
we're
trying
to
close
out
this
year.
A
So
I
know
thought
I'd
doubt
those
are
the
first
priorities,
and
so
that's
how
I'm
going
about
right
like
identifying?
What
should
EMS
be
almost
shouldn't.
So
I
can
add
as
many
lists
as
I'd
like.
So,
if
you
don't
want
to
do
it
by
quarters,
you
can
always
add
more
lists,
and
you
know
whatever
you
might
be
searching
by.
Maybe
you
want
to
do
it
by
month
or
you
want
to
do
it
by
some
theme.
A
That's
also
pretty
handy,
so
I'll
show
you
one
other.
So
this
is
my
now
next
future
board,
which
is
what
I
typically
use,
but
I
also
have
the
the
maturity
board.
So
when
I'm
thinking
about
the
features
that
we
support,
I
have
our
work
labeled
for
maturity
as
well.
So
the
work
in
this
list
will
allow
us
to
achieve
the
viable
rating,
the
complete
rating
and
The
Lovable
rating.
These
are
all
ratings
within
gitlab.
A
So
this
is
another
way
that
I
can
take
a
look
at
my
work
to
say,
okay.
Well,
we
really
need
to
close
this
one
out,
because
this
gets
us
a
little
bit
closer
to
viable.
So
epic,
epic
boards
are
really
handy
when
we're
thinking
about
high
level
planning,
without
like
definitive
timelines,
that
we
want
to
create
this
kind
of
longer
term
product
roadmap
for
ourselves.