►
From YouTube: Using GitLab as a Project Management Tool
Description
Recorded using GitLab v13.0
Technical Bootcamp Prerequisite 1
A
Hi
everyone,
my
name,
is
Curtis
ACK
I
am
a
Solutions
Architect
with
gitlab,
and
today
I'm
gonna
be
talking
about
git
lab
as
a
project
management
tool.
As
many
of
you
know,
gitlab
is
a
platform
that
covers
the
ten
stages
of
the
DevOps
lifecycle
and
today
we're
gonna
be
covering
the
manage
and
planned
stages
so
to
get
started.
Let's
talk
about
how
to
organize
your
work
within
get
lab
at
the
top
level
groups.
Allow
you
to
assemble
related
projects
together
and
nest.
A
Subgroups
groups
are
useful
for
allowing
you
to
roll
up
analytics
from
downline
projects
for
greater
visibility
and
also
define
a
top
level
configuration
for
user
access.
That's
inherited
by
subgroups
and
projects
groups
aren't
a
requirement.
It's
totally
ok,
to
have
a
standalone
project.
That's
not
part
of
any
group
projects
are
where
teams
collaborate
and
they
contain
the
code,
repo,
individual
work
issues
and
CI
CD
configuration
and
other
tools
that
enable
operations
and
security
teams
to
work
closely
and
collaborate
with
product
owners
and
developers.
A
Epics
represent
a
strategic
initiative
or
a
large
effort
that
your
team
is
working
through.
They
allow
for
groupings
of
other
epics
and
issues,
and
they
enable
a
management
of
a
portfolio
of
initiatives,
capabilities
and
features
efficiently.
Epics
exist
across
subgroups,
sharing
a
common
parent
group
as
well
as
projects
and
milestones
issues
describe
small
discrete
pieces
of
work.
Some
systems
call
them
a
user
story,
a
bug
or
a
defect,
and
the
idea
is
that
issues
contain
as
little
or
as
much
definition
needed
to
come
accomplish.
The
actual
work
defined
roadmaps
are
visual
representations
of
an
epic.
A
They
have
a
defined
start
and
end
date
within
a
group
and
are
shown
in
a
timeline
view
similar
to
a
Gantt
chart.
The
epics
roadmap
page
shows
a
visualization
for
all
of
the
epics
which
are
under
a
group
and
its
subgroups
milestones
are
designed
to
organize
and
track
issues
and
merge
requests
against
a
set
period
of
time.
So
the
idea
behind
a
milestone
is
that
it's
created
with
a
start
date
and
an
end
date.
If
you're
coming
from
an
agile
environment,
you
would
call
this
a
sprint
here.
A
We
have
an
overview
of
how
the
different
components
of
gitlab
could
map
to
an
organization.
It's
possible
to
use
a
single
group
to
encompass
an
entire
org
and
then
use
subgroups
for
each
Division
or
business
unit,
which
then
encapsulate
the
individual
projects,
epics
gift,
product
owners
and
leaders,
the
ability
to
link
and
manage
work
over
an
extended
period
of
time.
An
epoch
can
span
groups
and
projects,
and
it
makes
it
easier
to
manage
the
overall
flow
and
priority
of
work.
A
Labels
allow
you
to
categorize
epics
issues
and
merge
requests
with
a
descriptive
title,
such
as
bug,
feature
request
or
documentation
or
really
anything
you'd.
Like
group,
labels
can
be
assigned
to
an
issue
or
a
merge
request
of
any
project
within
that
group
or
subgroups
within
it.
Project
labels
can
be
assigned
to
issues
a
merge
request
within
that
project.
Only
labels
are
super
useful
for
allowing
filtering
and
managing
of
issues
in
merged
quests
and
are
visible
throughout
the
entire
application.
A
Boards
are
the
visual
information
radiators
for
a
project
management
and
crucial
for
organizations
and
teams
using
scrum
and
Kanban
practices.
We
use
them
to
plan
organize
and
visualize
a
workflow
for
a
feature,
product
release
and
the
issues
or
user
stories
bugs
features
or
whatever
you
call
them
in.
Another
system
are
shown
in
the
boards
in
the
form
of
cards
and
they
provide
a
team
with
a
central
location
to
visualize
and
track
the
work
in
progress.