►
From YouTube: GitLab 13 3 retrospectives summary
Description
Please join us for the Retrospective Discussion on Tuesday September 8th, 2020 at 4PM UTC (9AM PT)
13.3 Team Retrospective Issue:
https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8876
Retrospective Document: https://docs.google.com/document/d/1nEkM_7Dj4bT21GJy0Ut3By76FZqCfLBmFQNVThmW2TY/edit#
A
A
We
had
great
async
collaboration
between
the
ux
team
and
the
engineering
team,
using
a
design
planning
issue.
Nicole
from
release
management.
We
had
a
great
async
collaboration
between
the
front
end
and
backhand
engineers
regarding
performance
improvements
for
the
releases
page
that
resulted
in
identifying
an
ibc
for
optimization
in
the
api
server
from
create
editor
during
our
retrospective,
a
back-end
reacher
reached
out
to
a
front
end
to
ask
for
a
pair
programming
session
to
refresh
his
front
end
skill
set.
A
It
is
always
good
to
cross
specialty
boundaries
here
and
there
to
add
a
little
grass
to
our
skill
sets
results
ricky
from
verified
testing.
We
closed
a
lot
of
gene
unit
feature
related
issues
with
smilestone,
including
deleting
the
feature
flag
and
renaming
the
feature
to
unit
test
reports
cherio
from
ci.
Seeing
a
lot
of
success
with
our
graphql
migration
efforts.
A
We
draw
from
package,
we
released
the
new
package
details,
ui
changed
from
progressive
delivery.
We
made
it
possible
to
versioning
home
charts
in
order
to
ship
breaking
changes
safely
and
nick
from
geo.
We
completed
the
work
to
remove
jio's
reliance
on
foreign
data
drivers,
which
makes
geo
easier
to
set
up
and
maintain.
A
A
Degradation
efficiency
click
from
database.
It
has
been
noted
that
the
database
related
work
has
become
more
predictable
and
we
know
much
more
about
the
planned
work
than
we
did
a
few
months
ago:
diversity,
inclusion
and
belonging
created
from
the
memory
team,
as
called
out
by
lexi.
We
are
really
appreciative
of
the
friends
and
family
day
this
month.
A
Additionally,
it
is
encouraging
to
see
so
many
folks
taking
additional
time
off
this
month
to
disconnect
recharge
and
take
time
for
themselves,
iteration
from
nick
keeping
our
mrs
small
and
the
review
cycle
times
short
and
the
four
days
average.
We
saw
a
significant
increase
in
our
mr
rate.
Compared
to
previous
months
and
john
from
plan,
we
had
success
in
identifying
engineering
dris
earlier
in
the
product
development
flow
for
complex
features
which
led
to
better
breakdowns
and
better
collaboration.
A
A
A
A
And
how
we
can
improve
necklace
from
configure
giving
feedbacks
giving
feedback
for
design
issues
on
time
is
probably
related
to
discussion
of
having
too
many
issues
and
not
knowing
what
to
focus
on.
We
thought
that
everything
was
probably
discussed
when
new
comments
came
up
and
those
surprised
us
this
led
to
quite
a
bit
of
uncertainty
about
the
scope
and
status
of
the
front-end
issues.
A
As
we
started
running
more
experiments,
we
started
to
see
gaps
in
our
experimentation
process,
similar
to
our
product
development
flow.
We
are
now
starting
to
define
our
experiment:
workflow
iteration
ricky,
from
verified
testing.
We
had
a
bit
of
uncertainty
around
how
we
were
using
the
deliverable
and
stretch
labels.
We
merged
our
current
process
into
our
handbook
page
with
an
eye
for
improving
how
we
are
using
it
to
better
level
set
for
the
same
ratio
dashboard.
A
A
The
second
topic
is:
how
do
europe
groups
use
the
various
infrastructure
monitoring
dashboards
tools
that
are
available
now
that
we
are
using
feature
flags
more
rigorously?
It
opens
the
door
for
engineers
to
monitor
their
own
changes
in
production.
My
group
is
working
on
adding
a
process
around
the
monitoring
changes
after
a
feature
flag
is
enabled.