►
From YouTube: 14.3 Retrospective Summary
Description
Retro Content - https://docs.google.com/document/d/1nEkM_7Dj4bT21GJy0Ut3By76FZqCfLBmFQNVThmW2TY/edit
Summary Slides - https://docs.google.com/presentation/d/1OutJ5pQRfupipYS2yf3bBEwYSYYTIy_lEY0ElUaM-ok/edit#slide=id.g8e3e21f43b_0_10
Organization Issue - https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12442
A
A
A
Now
the
format
for
our
retrospectives
is
we
go
through
what
praise
we
have
for
the
team?
What
went
well
what
went
wrong
and
what
we
can
improve,
I'm
going
to
go
through
the
highlights
here,
but
there's
full
content
in
a
google
doc
that
you
can
find
linked
in
below
this
video,
so
praise
for
the
team.
It's
really
great
to
see
a
lot
of
praise
for
various
team
members
called
out.
There
was
shout
outs
for
all
sorts
of
activities,
including
new
team
members,
ramping
up
quickly
collaboration,
async
on
issues
and
delivering
key
features.
A
A
What
didn't
go
so
well.
What
went
wrong
so
a
couple
of
points
here
on
collaboration,
efficiency
and
transparency.
One
was
around
the
change
that
was
introduced
by
third-party
vendors,
wasn't
scoped
very
well
or
understood
as
well,
and
that
caused
a
lot
of
rework
in
the
team
and
then.
Lastly,
a
really
important
reminder
for
all
team
members
that
energy
and
stress
levels
continue
to
be
impacted
by
the
pandemic.
Some
countries
or
people
are
in
various
situations
relative
to
the
pandemic.
A
A
Some
highlights
that
I
saw
where
one
suggestion
was
that
we
need
to
ensure
when
we're
doing
rapid
actions
or
head
count,
resets,
where
we're
having
team
members
from
one
group
work
and
help
another
team
complete
items
in
their
area
or
scope
that
we
have
really
have
those
issues
prepared
for
handoff.
Another
one
was
making
sure
that
even
for
those
little
little
used
features
in
this
case
it
was
cost
factors
in
the
ci
group.
A
We
need
to
make
sure
those
get
documented,
because
eventually
you
will
want
to
utilize
them
or
build
upon
them
and
it
becomes
difficult
to
find
exactly
who
created
them
and
how
how
the
features
work.
Another
was
a
suggestion
about
how
we
can
improve
rolling
out
mvcs
in
high
traffic
parts
of
our
product
like
ci.
A
So
that
is
the
summary.
As
a
reminder,
we
have
the
retrospective
discussion
on
thursday
october
7th
at
9
00
a.m.
Pacific
time
you
can
join
it
on
git
lab
unfiltered,
there's
also
a
zoom
link
if
you're
internal
to
gitlab.
The
two
topics
that
I
have
proposed
for
discussion
are
the
first
one
is
that
this
release
there.
Also,
it
also
happened
to
coincide
with
a
couple
of
kind
of
company-wide
tasks,
including
our
360
review,
mid-year
check-in,
a
bunch
of
trainings,
and
so
especially
for
managers.
It
became
became
a
lot.
A
It
became
a
burden
to
try
to
do
that,
while
also
performing
regular
monthly
release
activities
and
then
the
other
one
was
what
I
mentioned
in
the
how
we
can
improve,
ensuring
that
we
continue
to
utilize
iteration
and
ship
mvcs,
but
figuring
out
what
kind
of
enablement
we
need
to
do
for
that's
to
happen
in
stages
or
parts
of
the
product
that
are
heavily
trafficked.
So
I'm
really
looking
forward
to
the
discussion,
and
I
hope
that
you
all
join
it
thanks
and
have
a
great
rest
of
your
day.