►
Description
This video is part 1 of 3
Part 2: https://www.youtube.com/watch?v=Uw249U2U34w
Part 3: https://www.youtube.com/watch?v=J2u7OqBA_aQ
GitLab Handbook for the Marketing Department's guidelines for using GitLab project management: https://about.gitlab.com/handbook/marketing/project-management-guidelines/
A
Hello,
my
name
is
William
I'm
part
of
the
product
marketing
team
here
at
gitlab,
and
this
is
a
video
to
talk
a
little
bit
about
some
of
the
project
management
capabilities
of
gitlab.
In
particular,
I
want
to
talk
about
issues,
epics
milestones
and
roadmaps
along
the
way
we
might
touch
on
some
other
project
management,
capabilities
or
concepts,
but
this
should
give
you
a
basic
overview
so
that
you
can
use
some
of
the
features
of
git
lab
and
kind
of
understand
what
they
do
and
how
they
fit
together.
A
So
to
show
you
how
this
works,
I'll
show
you
a
few
of
the
issues
that
I'm
working
on
and
how
I'm
using
these
kind
of
concepts
together.
So
the
first
part
of
get
lab
to
understand
is
the
issue
think
of
an
issue
as
a
task
to
be
accomplished.
If
you
have
a
to
do
something
that
you
need
to
go,
do
you
should
go,
create
an
issue
to
go.
Do
that
and
that
issue
is
going
to
let
you
track
that
to
do
this
is
an
example
of
an
issue.
A
You
can
have
a
description
that
talks
about
what
you
need
to
do
in
this
case.
I
am
going
to
kick
off
the
market
requirements
for
get-ups,
but
you
could
have
any
kind
of
issue.
You're
kicking
off
and
I
can
add
a
few
to
dues
here.
Just
little
checkboxes,
but
mostly
an
issue
is
going
to
be
where
I
can
make
comments
and
collaborate
with
other
people
and
an
issue
is
the
unit
of
work,
something
to
go
and
do
now.
This
issue
is
part
of
an
epic.
A
A
So
if
you
have
multiple
things,
you
need
to
do
and
those
get
bucketed
up
into
like
a
larger
deliverable,
then
that's
what
you
use
the
epic
for
so
an
epic
is
a
bucket
of
issues.
I
can
think
of
these
as
like
a
project.
Unfortunately,
in
gitlab
we
have
something
else.
That's
already
called
a
project.
You
know
you
can
have
a
get
lab
project
is
the
entire
repository,
so
there's
a
marketing
project
and
there's
a
product
marketing
project,
there's
a
website
project.
A
So
unfortunately,
that's
called
a
project,
but
in
this
case
the
epic
epic
is
the
bucket
of
issues
is
so
in
this
case.
For
this,
epic
I
want
to
define
some
market
requirements,
and
it
has
three
issues
that
are
part
of
this
epic.
Now,
the
difference
between
the
issue
in
the
epic
is
first,
you
can
see.
The
issue
has
a
bunch
of
a
bunch
of
rich
elements
that
you
can
interact.
A
It's
design
for,
like
your
unit
of
work,
the
epic
is
a
lot
simpler,
there's
not
as
much
stuff
over
here,
because
an
epic
is
designed
to
be
a
bucket
of
work
rather
than
just
one
unit.
In
that
sense,
it
has
the
elements
that
are
bucketed
into
it,
and
it
has
the
timeframe
in
which
we
expect
this
project
or
this
epoch
to
get
done.
I
keep
saying
project
informally,
but
this
this
epic
is
a
set
of
deliverables.
A
So
the
way
to
think
about
an
epic
is
when
all
of
these
issues
are
closed,
then
the
epic
is
done
right.
So
an
epic
is
not
something
that
you
want
to
keep
open
for
a
long
time
and
you
keep
adding
issues
to
an
epic
is
you
is
something
like
here's
something
we
need
to
go
accomplish
in
order
to
accomplish
this,
it's
gonna
be
set
into
a
bucket
of
things
and
each
each
of
those
individual
things.
A
A
Now,
the
timeframe
for
when
this
issue
starts
or
sorry
when
this
epic
starts
and
when
this
epic
ends
that's
determined
by
the
milestones
that
are
part
of
the
issues
that
may
the
epic.
So
you
assign
issues
to
a
milestone
and
these
dates
will
automatically
be
generated.
The
epic,
because
it's
a
big
bucket
of
a
lot
of
things
to
get
done,
we'll
look
at
the
dates
for
the
individual
tasks
that
comprise
that
epic
and
it's
just
gonna
grow
or
shrink
automatically,
depending
on
the
milestones
there.
A
So,
let's,
let's
actually
take
a
look
at
what
a
milestone
is
so
in
this
case,
I
have
my
kickoff
epic
kickoff
issue,
and
it's
part
of
this
milestone
called
Bangalore
SM
strategic
marketing
Bangalore.
We
name
each
of
our
milestones
after
different
cities
around
the
world.
So
in
this
case
the
milestone
is
also.
It
looks
like
a
bucket
of
work
to
get
done
right
like
these
are
all
these
issues
that
are
open
in
the
milestone
and
closed
in
the
milestone
and
the
difference
between
the
epic
and
the
end.
A
The
milestone
is
that
epic
is
the
larger
project
or
deliverable
that
you
want
to
get
done
and
the
milestone
is
a
chunk
of
time.
So
there's
a
way
to
think
about
this
in
a
way
to
not
think
about
this,
but
we
did
not
think
about.
This
is
a
milestone
as
a
deliverable
right,
so
you
might
think
when
I
ship,
the
webpage
for
this
project,
when
I
when
I've
got
a
webpage,
live
I've,
completed
a
milestone,
and
certainly
that
is
an
important
milestone
in
the
project.
A
But
that's
not
how
this
milestone
should
be
used,
because
that
that
webpage,
even
though
it
comprises
a
lot
of
things,
need
to
happen
to
get
that
webpage
lives.
That
might
you
know
that
might
get
done
next
week
or
it
might
get
done
next
month
that
those
due
dates
can
change
instead
think
of
a
milestone
as
a
unit
of
time
like
January
or
February
or
March.
A
Usually,
when
you
set
the
start
date
and
the
due
date
for
a
milestone,
then
you
don't
change
that
in
the
concept
of
if
you're
familiar
with
agile
project
management
and
an
agile
software
development,
this
is
often
called
a
sprint,
and
usually
this
can
be
a
one
week,
period
two-week
period
or
a
month-long
period,
but
it's
at
a
street
period
of
time.
That's
what
a
milestone
is
so
for
us
we
use
two-week
milestones
and
the
Bangalore
milestone
is
everything
that
we're
gonna
work
on
between
June
15th
and
June
28th.
So
you
set
up
a
milestone.
A
You
say
this
chunk
of
time
in
this
two
weeks
and
then
you
ask
yourself
what
am
I
gonna
get
done
in
that
two
weeks?
What
do
I
think
I
can
accomplish
and
that's
how
these
issues
get
added
to
this
milestone.
So
the
reason
this
issue
here
this
kickoff
market
requirements
issue-
is
part
of
the
get
up
get
off
market
requirements.
Epoch
is
because
that
this
epoch
is
the
larger
thing.
I
need
to
get
done.
The
larger
deliverable
is
to
create
the
market
requirements.
A
A
A
So
the
idea
here
is
the
market
requirements
epoch.
It's
actually
part
of
a
bigger
epoch,
called
the
resource
page,
so
I
have
a
bigger
deliverable,
which
is
the
resource
page,
and
in
order
for
me
to
deliver
this
page,
I
need
to
do
a
market
overview.
I
need
to
have
a
market
requirement
solution,
I'll
review.
All
of
these
things,
and
each
of
these
things
comprise
of
their
own
set
of
issues
that
need
to
get
done
in
order
to
complete
that
deliverable.
A
So
this
is
the
topical
structure
of
the
things
I'm
working
on
the
epics
and
the
issues,
and
then
the
timeframe
in
which
these
things
might
happen
are
the
milestones
and
due
dates.
So,
for
example,
this
one
is
in
the
Bangalore:
that's
this
week,
I'm
getting
it
done
this
I'm,
not
gonna,
get
done
until
next
week,
and
so
I've
added
it
to
my
cape
town,
which
is
our
next
milestone
or
our
next
sprint.
Our
next
milestone,
that's
the
next
two
weeks
and
this
one
I
just
have
on
the
backlog.
That's
like
means
it's
not
a
sign.
A
10Th
is
because
the
last
milestone
that
our
issue
is
assigned
to
in
this
epoch
is
that
cape
town
milestone
and
it's
July
10th,
that's
where
that
date
comes
from
the
other
view
that
you'll
get
into
this
get
from
this
is
called
a
road
map.
So
the
road
map
view
takes
all
of
our
epics
and
our
milestones.
So
here
are
my
milestones
and
here
are
my
epics
and
it
lays
them
out
on
a
calendar.
So
here
is
my
Bangalore
milestone.
I've
been
telling
you
about
so
this
is
this
mica
period
of
time.
A
A
Are
the
discrete
units
of
time
asked
what
am
I
gonna
get
done
in
those
and
then,
if
we
look
at
this
epoch,
so
here's
this
top-level
go-to-market
epoch
and
within
that
I
have
a
get-ups
epoch,
which
is
the
whole
go
to
market
for
all
of
get
ops
within
that
I.
Have
this
deliverable
of
resource
page
within
that
epoch?
I
have
all
of
these
other
epochs.
You
can
see
you
can
nest
these
pretty
deep
and
here's
this
market
requirements
epoch
that
I've
been
showing
you
and
inside
of
that
market
requirements.
A
Epoch
I
have
those
few
deliverables
and
that's
how
this
time
frame
gets
determined
because
between
here
and
here
are
the
issues
that
are
part
of
these
two
milestones.
So
hopefully
that
gives
you
an
understanding
of
how
milestones
relate
to
epochs
and
on
this
roadmap
you
you
can
see.
How
long
is
it
gonna
take
me
to
complete
a
particular
epoch.
For
example,
you
know
this
one
should
be
done
within
this
time
and
the
epics
they
may
expand
or
they
may
contract.
So
you
know,
for
example,
this
market
requirements,
epic,
if
I
add
more
stuff
to
it.
A
It
might
take
longer
to
get
done
so
this
might
expand
or
contract
or
move
around,
depending
on
how
good
I
am
at
delivering
my
things
on
time,
but
these
milestones
up
here
these
aren't
going
to
change.
I
set
these
and
they're
for
a
particular
period
of
time,
for
example,
what's
happening
in
q1,
what's
happening
this
week
now
today
in
gitlab,
when
I'm
recording
this
video,
we
don't
have
the
ability
to
add
multiple
milestones.
So,
unfortunately,
today
you
have
to
choose.
A
You
can
either
have
something
the
next
two
weeks
in
the
Cape
Town
or
it
can
be
in
q1,
but
I
can't
have
them
in
both
an
ideal
world.
I
could
be
able
to
have
two
and
that's
a
future
feature.
That's
coming
a
good
lab,
but
today
I
I
just
used
these.
You
know
two-week
long
or
maybe
sometimes
a
month.
Long
milestones.
A
The
last
thing
I
will
touch
on
is
just
briefly
this
concept
of
labels.
This
is
for
another
video,
but
labels
are
way
to
categorize
your
work,
so
I
might
have
a
project
and
I
might
have
you
know
at
this
project.
I'm
working
on
as
a
market
requirements
and
I
have
these
things
that
I
need
to
get
done,
they're
getting
done
in
this
period
of
time,
but
I
might
want
to
categorize
them
so,
for
example,
by
priority,
for
example,
this
one
is
a
top
priority.
A
A
So
if
you
have
something
and
it's
the
concept
of
a
big
bucket,
a
big
deliverable
or
big
thing,
you
want
to
get
done.
You
should
use
an
epic
for
that.
You
probably
don't
need
a
label
for
it
as
well.
You
might
want
to
categorize
all
those
things
together,
but
put
them
into
an
epic.
You
might
have
you're
saying
what
are
we
doing
in
the
next
month?
That's
a
milestone,
put
that
in
the
milestone,
and
then
you
can
use
labels,
for
there
are
other
concepts.
So
hopefully
that
helps
you
out.
A
There
are
a
lot
of
folks
that
get
lab.
You
can
ping,
you
know
other
folks
in
marketing
and
there's
lots
of
folks
that
can
help
you
out
with
that.
If
you
are
using
get
lab-
and
you
know
your
get
lab
team
member
and
you
need
some
help
kind
of
using
the
structure
that
we've
outlined.
But
this
is
a
video
to
give
you
a
quick
overview.
How
we
use
it
here
and
hopefully
that
helps
you
out
Cheers.