►
From YouTube: GitLab 12.6 Kickoff - Plan: Project Management
Description
Quick run through of the Project Management portion of Plan's 12.6 Release Planning issue.
https://gitlab.com/gitlab-org/plan/issues/27
A
Hey
Gabe
here,
I'm
gonna
do
a
quick
kickoff
video
for
12.6
for
the
project
management
group
within
plan.
I'm
gonna.
Do
it
solo
today,
instead
of
the
typical
cross
group,
joint
kickoff
call
to
keep
things
short.
If
you
want
to
follow
along
any
more
details,
note
with
and
get
lab
work,
there
is
a
planned
project.
There's
issues
and
number
27
has
the
release
plan
for
project
management
as
well
as
portfolio
and
will
have
for
certifying.
A
This
is
kind
of
you
know,
high-level
our
issue
tracking
and
issue
board
strategies
are
up
to
date
and
kind
of
talk
about
where
we're
headed
next,
a
high-level
where
we're
going
to
focusing
on
improving
sprint
and
release,
cadence
understanding
and
tracking
scope
change
within
the
milestone
and
then
moving
on
to
issue
task
lists
and
tasks
which
I
don't
think
we're
gonna
get
to
in
twelve
six,
so
I'll
kind
of
just
stop
there.
But
if
you
want
to
follow
along,
you
can
check
this
out
and
then
for
issue
boards.
A
It
looks
like
the
kind
of
main
things
that
we're
looking
to
implement
is
real-time,
so
there's
an
issue
that
we'll
talk
about
a
minute
for
tracking
refactoring
the
boards
to
get
ready
for
that
main
features
that
we
need
a
ship,
and
these
are
for
showing
better
with
the
Gartner.
A
demo
is
coming
up
in
January,
adding
a
burn
up
charts
for
milestones.
This
is
the
first
step
for
tracking,
better
scope
change,
so,
instead
of
a
typical
burn
down,
we'll
also
have
a
burn
up
on
it.
A
That
shows
you
your
scope
throughout
the
course
of
the
milestone,
and
then
your
progress
of
completed
or
close
issues,
leading
up
to
that.
You
can
check
out
this
issue
if
you
want
to
read
more,
but
that's
the
short
version.
The
other
thing
we're
looking
at
is
improving
multiple
milestones,
so
an
issue
can
belong
to
multiple
milestones
and
milestones
can
all
have
also
have
a
type.
A
The
the
purpose
of
this
is
so
that
we
can
start
tracking
velocity
and
relationships
of
scope,
change
from
milestone
to
milestone
in
a
better
way,
and
we
can
also
support
those
users
who
practice
scrum
or
other
time-boxed
activities
where
there
are
multiple
time
boxes
happening
simultaneously.
This
is
a
pretty
well
requested
feature.
All
specifically
the
multiple
milestones
are,
but
to
make
that
kind
of
make
sense
and
accomplish
some
things
we
want
to
later.
We
also
need
to
do
the
milestone
types.
A
A
At
least
the
names
can
be
customizable
by
the
group
admin,
and
then
we
also
have,
as
we
add
those
types
they
will
show
up,
is
options
in
the
sidebar
that
you
can
then
add
specific
milestones
to
so
there's
a
lot
of
like
nuts
and
bolts
and
weird
things
to
figure
out
what
this
I
met
with
Sean
just
kind
of
talked
through
I
level,
and
we're
going
to
start
rolling
through
that.
But
we
will
do
these
two
things
behind
a
feature
flag,
because
that
there
are
lots
of
implications
lots
of
data
migrations.
A
We
have
to
make
sure
that
this
change
doesn't
break
the
triage
package
as
like.
There
are
some
dependencies
there
and
you'd
be
cleaned
up,
but
all
those
map
to
these
three
epochs
that
kind
of
we're
tracking
as
part
of
this
work
in
terms
of
refactoring,
we
are,
there
is
an
epoch
and
we
don't
need
to
go
in
there
for
refactoring
issue
boards
get
ready,
and
then
we
also
are
gonna,
take
the
lead
or
the
collaborate
really
closely
with
memory
and
12:6
to
start
work
on
the
WebSocket
implementation.
So
we
have
to
do
this.
A
It's
a
different
way
of
a
different
kind
of
network
transport
protocol,
instead
of
traditional
HTTP
requests
will
be
sending
things
over
WebSockets,
which
is
how
you
do
real-time
or
one
way
of
doing
it.
But
yeah
there's
a
some
other
design
priorities
to
cue
things
up
for
12
7c,
and
we
talked
about
issue
tasks.
We
want
to
finish
up
the
design
for
that
and
then
some
UI
UX
to
represent
debt
carryover
issues
on
milestones.
A
We
also,
like
generally,
want
to
look
at
milestones
as
a
whole
and
clean
them
up
because
they
haven't
gotten
any
love
and
oil,
and
you
can
tell
group
level
templates
is
another
thing
we
need
to
start
exploring
as
well.
It's
the
big
ask
for
most
of
our
customers
and
the
water
community.
If
you
have
a
hundred
projects
and
you
make
one
change
to
a
template,
you
have
to
change
it
in
hundred
projects
instead
of
one
place,
that's
not
very
efficient,
so
we
want
to
start
addressing
some
biessings.
It's
also
an
internal
customer
askin.
A
So
if
there's
some
design
stuff
to
think
through
there,
and
then
we
also
want
to
start
working
on
cleaning
up
labels,
they
they
need
a
little
bit
of
luck
too,
and
while
that
is
starting
with
removing
the
ability
to
duplicate
label
names
across
projects
and
groups
which
is
going
to
require
some
validation,
workflows
and
things
like
that,
that's
it
for
project
management
for
12:6.
If
you
have
any
questions,
you
can
ask
them
in
this
issue
or
bring
them
up
in
slack
channel
thanks
for
hanging
out
for
a
few
minutes.