►
From YouTube: 13.2 Team Retrospective Summary
Description
Please join us for the Retrospective Discussion on Thursday August 6th, 2020 at 4PM UTC (9AM PT)
13.2 Team Retrospective Issue:
https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8418
Retrospective Document: https://docs.google.com/document/d/1nEkM_7Dj4bT21GJy0Ut3By76FZqCfLBmFQNVThmW2TY/edit#
A
Hey
everyone
welcome
to
the
13.2
team.
Retrospective
summary,
I'm
jerome
and
I'll
be
the
host
for
this
video.
What
we're
going
to
be
covering
today
are
three
things.
First,
going
over
what
went
well,
second,
what
went
wrong
and
third,
what
can
we
improve?
So,
let's
talk
about
what
went
well,
this
milestone,
starting
with
collaboration.
A
We've
got
a
lot
of
different
teams,
reporting
that
collaboration
went
well.
What
I
want
to
do
is
take
a
few
of
these
and
highlight
them.
So,
let's
take
a
look
at
jake
from
plan,
we
had
a
very
successful
cross-team
collaboration
with
ecosystem
for
the
jira
integration,
expansion,
mvc
thanks
to
solid
communication
and
collaboration,
we're
able
to
deliver
more
than
we
expected
for
the
13.2
release.
A
A
A
We've
got
john
from
package
saying
we
can
now
measure
adoption
of
each
package
manager,
format
in
our
dashboard
and
roman,
from
create
knowledge,
saying
we
release
to
figma
plugin,
so
designs
can
be
uploaded
to
issues
right
from
within
figma
and
then
michelle
from
create
source
code
has
a
lot
of
awesome
and
often
complex
issues
were
shipped
sectional
code
owners
moving
approvals
to
core
finding
references
with
code,
navigation
file
by
file
reviewing
and
squash
commits,
as
well
as
an
item
potency
issue
that
has
been
taking
a
while
to
get
out.
A
Let's
take
a
look
at
efficiency,
clement
reports,
sorry
clement
from
monitor
apm
reports.
We
had
a
technical
spike
and
design
issue
take
place
in
the
same
milestone
for
the
same
topic.
This
was
very
efficient
and
helped
to
make
sure
the
designs
were
actionable
and
ready
for
engineering
in
the
next
milestone,
and
then
we've
got
jake
from
plan.
A
A
A
Taking
a
look
at
efficiency,
this
one's
actually
mine
for
the
growth
conversion
team,
the
requirements
of
our
storage
project
change
multiple
times,
resulting
in
extra
work
and
increased
confusion
for
engineering,
ux
and
product.
We
think
having
a
clear
dri
up
front
is
crucial
for
cross-functional
projects
and
then
andre
from
create
source
code.
A
A
A
A
A
You
can
think
of
cross-team,
as
within
your
front-end
and
back-end
teams,
or
even
across
different
groups
or
stages.
I
noticed
that
a
lot
of
teams
mentioned
that
collaboration
went
well
I'd,
love
for
those
teams
to
be
able
to
share
what
sort
of
things
they're
doing
to
ensure
that
crosstalk
collaboration
goes
well.