►
From YouTube: GitLab Agile Project Management 4-min Overview
Description
GitLab Agile Project Management Overview
Use Gitlabs Project management capabilities to build out your agile teams. GitLab gives you the ability to have end-to-end devops traceability by doing agile project management with Epics/issues that are directly connected to your merge requests and devops pipelines!
Read more about our product vision: http://bit.ly/2IyXDOX
Learn about FOSS & GitLab: http://bit.ly/2KegFjx
Get in touch with Sales: http://bit.ly/2IygR7z
A
A
The
Rome
app
is
a
scheduled
events
that
communicate
planned
solution.
Deliverables,
/,
planning,
horizon
gitlab
roadmaps,
show
epics
timeframes
and
can
be
visualized
as
a
timeline
with
our
portfolio
initiative
or
investment,
a
capability
or
feature
or
simply
a
large
story,
use
an
epic
to
capture
its
description
business
case
or
any
data
pertinent
to
describe
the
large
body
of
work.
A
In
kit
lab
an
epic
also
contains
a
title
description,
much
like
an
issue,
but
it
allows
you
to
attach
multiple
child
issues
to
it
and
indicate
that
hierarchy
break
down
a
large
epic
into
discrete
logical
pieces
for
individual,
independent
tracking
with
child
epics
and
issues
an
agile.
You
often
start
with
a
user
story
that
captures
a
single
feature
that
delivers
business
value
for
users
and
get
lab
a
single
issue
of
the
project
serves
this
purpose.
A
A
Product
owners
create
issues
to
reflect
the
needs
of
the
business
and
customers.
They
are
prioritized
in
a
product
backlog
to
capture
urgency
and
desired
order
of
development
and
communicate
with
stakeholders
to
determine
the
priorities
and
get
lab
they're
dynamically
generated
issueless,
which
users
can
for
you
to
track
their
backlog.
A
A
Sprint
represents
a
finite
time
period
in
which
the
work
is
to
be
completed,
which
may
be
a
week
a
few
weeks
or
perhaps
a
month
or
more
get
labs.
Milestone,
feature
supports,
it
assigned
milestones
a
start
date
and
a
due
date
to
capture
the
time
period
of
the
Sprint,
the
team
that
puts
issues
into
that
sprint
by
sending
them
to
a
particular
milestone.
A
A
Throughout
the
Sprint
issues
move
through
various
stages,
such
as
ready
for
dev
in
dev,
in
QA,
in
review
done
depending
on
the
workflow
in
your
particular
organization
in
kit
lab
issue
boards.
Allow
you
to
find
your
stages,
enable
you
to
move
the
issues
through
them.
The
team
could
configure
the
board
with
respect
to
the
milestone
and
other
relevant
attributes
during
daily
stand-ups.
The
team
looks
at
the
board
together
to
see
the
status
of
the
sprint
from
a
workflow
perspective
toward
the
end
of
a
sprint.
The
development
team
demos
completed
features
to
various
stakeholders
with
gitlab.
A
This
process
is
made
simple,
using
review
apps
so
that
even
code
not
yet
released
to
production
can
be
demoed.
Review
apps
and
see.
Icd
features
are
integrated
with
the
merge
requests
itself.
A
team
retrospective
at
the
end
of
the
sprint
can
be
documented
and
it
provided
wiki
so
that
lessons
learned
and
action
items
are
tracked
over
time.
During
the
actual
retrospective,
the
team
can
look
at
the
milestones
page,
which
displays
the
burned
out
chart
and
other
statistics
on
the
completed
sprint.