►
From YouTube: GitLab 13.3 Kickoff - Plan:Project Management
Description
Planning Issue: https://gitlab.com/gitlab-org/plan/-/issues/123
A
A
There's
not
much
different
in
terms
of
target
scope
for
this
release.
We
weren't
able
to
make
progress
on
what
we
had
planned
for
13.2,
because
at
the
percent
of
the
back
of
engineers
in
my
group,
were
alone
to
the
JIRA
integration
effort
to
make
sure
that
that
shipped
in
13.2,
which
I
believe
will
still
proud
of
our
team
for
completing
what
they
were
able
to
get
done.
This
iteration,
even
though
they're
short-handed
as
of
early
this
morning,
all
of
the
merge
requests
for
the
MVC
4
iterations
were
merged
in.
A
In
some
of
the
same
things
that
I'm
not
gonna,
go
to
detail
because
I
highlighted
last
kickoff
for
30.2.
What
I
will
talk
a
little
bit
about
is
some
of
the
changes
that
are
category
pages
Direction
pages
within
the
project
management
group.
One
of
the
things
that
I
did
to
try
to
help
better
communicate
where
the
progress
for
making
instar
themes
is,
is
updating
with
each
of
these.
What's
next
and
why?
A
Where
we're
at
and
what's
next
in,
what's
planned
so
for
the
manage
print
release,
cadence
I
think
we
will
hopefully
have
shipped
the
iterations
first
MVC
in
1302.
We're
going
to
continue
to
invest
in
the
in
the
roadmap.
For
iterations
for
the
foreseeable
future,
until
it
gets
to
the
point
where
it
supports
the
use
cases,
it
needs
to
for
single
teams
to
plan
as
well
as
role
of
reporting
upstream
through
the
group
are
key
and
we're
also
continuing
work
on
tracking
scope.
Change
within
a
milestone.
A
Henryk
took
over
working
on
in
13.1
and
made
a
lot
of
good
progress,
I'm
highly
confident
that
we
will
be
able
to
ship
burn
up
charts
on
milestones
as
well
as
iterations
in
13.3,
and
then
from
there
we're
going
to
continue
to
show
basic
improvements
and
changes.
The
issues
that
happen.
So,
if
issue
were
to
miss,
we
would
show
that
it
would
miss
within
the
report
for
that,
given
iteration
room
I,
also,
instead
of
showing
it
was
that
were
part
of
it.
A
Shipping
iterations
in
13
to
unblocks
us
for
working
on
velocity
and
volatility,
and
eventually
team
capacity.
So
we're
gonna
start
the
design
phase
of
this
and
13.3
and
sorting
that
out
and
working
with
the
analytics
group
and
manage
to
see
how
we
can
collaborate
together
on
that.
But
this
is
a.
This
is
kind
of
the
natural
evolution
of
iterations.
Is
this
will
allow
us
to
sum
over
the
average
wait
deliver
over
previous
number
of
iterations
help?
You
set
better
expectations
for
what
you're
able
to
deliver
within
the
next
iteration.
A
A
So
this
is
a
good
efficiency
game
and
once
we
get
a
little
further
along
with
this,
we'll
probably
circle
back
up
to
custom
fields,
I
also
updated
the
strategy
for
this
long-term
strategy
to
support
the
things
that
were
working
on,
which
is
the
working
group
for
simplifying
groups
and
projects
and
then
also
making
things
more
extensible.
These
kind
of
focuses
are
the
result
of
customer
feedback.
Think
it
lab
is
not
extensible
enough
to
support.
A
We
use
that
word
a
lot,
but
it's
not
possible
to
support
in
a
usable
manner
all
the
different
use
cases
that
companies
are
trying
to
use
it
for
whether
that's
mon
repos
micro
services
wanting
to
have
your
issues
at
the
group
level.
There's
just
a
lot
of
things
that
that
aren't
configurable
enough
to
support
the
emerging
needs
as
we
try
to
scale
and
support
enterpriser
at
this.
So
this
is
gonna,
be
an
ongoing
effort,
probably
for
the
next
12
months
ago.
A
So
use
your
set
up
the
integration
once
and
then
they
have
the
option
of
a
one-time
import
or
they
have
the
option
to
maintain
an
ongoing
Thule
discrimination
data
sync
between
JIRA
issues
and
get
lab
issues.
So
I
think
this
will
be
the
net
natural
evolution
of
the
importer,
and
it
also
makes
sense
so
that
we're
not
having
an
overlapping
solution
and
creating
two
different,
more
or
less
issue
integrations
with
JIRA.
The
this
hasn't
been
merged
in
yet
either.
A
Just
call
you
issue
boards,
one
of
the
things
that
we're
working
on
right
now
and
the
portfolio
group
is
going
to
be
shipping
and
13.3
is
epic
swim
lanes
after
epic
swim
lanes,
we're
gonna
repurpose
boards
and
extend
them
again
the
theme
of
extension
you're
using
things
we
have
small
permanent
support,
many
different
use
cases
the
extend
boards
to
support
epic
boards
or
program
boards-
and
this
is
another
key
component
of
being
competitive
with
those
organizations
that
you
safe
and
then
I
added
a
couple.
Other
kind
of
this
is
how
we'll
know
we've
achieved.
A
A
good
example
would
be
on
the
issue
card
if
there's
a
merge
request
that
is
done,
maybe
or
ready
for
review
or
whatever,
like
I
like
that
on
the
card
face.
So
you
don't
have
to
open
up
the
card
or
even
open
up
the
issue
to
know
that
you
have
to
take
action
or
there's
something.
That's
ready
to
be
reviewed
there
and
I
think
what
we
really
ultimately
want
to
work
towards.