►
From YouTube: GitLab Team Retrospective Summary 13.7
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
This
one's
going
to
be
a
little
bit
lighter
retro
than
previously,
just
because
13
7
ended
toward
the
end
of
the
year.
People
were.
A
lot
of
people
were
off
for
the
holidays,
while
we
were
having
the
individual
team
retrospectives,
but
hopefully
we'll
still
have
a
decent
amount
of
content
to
get
through.
A
A
Okay,
so
the
praise
you
have
for
your
team,
typically
we'd,
highlight
just
a
few
points
for
each
section,
but
again,
since
the
content
was
a
little
lighter.
This
milestone
I'll
try
to
get
through
everyone's
everyone's
points
here:
okay,
so
back
to
praise,
starting
with
jerome
from
the
growth
and
product
intelligence
team,
he
stated
that
the
team
has
done
a
tremendous
job
of
building
out
our
analytics,
tooling
and
processes
over
the
past
few
months.
A
We've
now
passed
a
thousand
metrics
implemented
via
usage
ping
280,
mrs
reviewed
by
our
team
thiago
from
threat
management
stated
that
the
vulnerability
management
category
reached
viable
maturity.
A
lot
of
hard
work
went
into
this
achievement
over
the
past
year
and
we
should
celebrate.
I
agree:
matt
from
ecosystem
said
that,
after
a
recent
realignment,
the
team
members
who
were
joining
a
new
team
felt
very
welcomed
by
the
existing
team
members.
Thank
you
for
everyone's
focus
on
the
belonging
value.
A
Okay.
Moving
on
to
what
went
well
we'll
go
through
each
of
our
values
that
had
points
starting
with
the
collaboration
value
where
jerome
said
that
we
had
multiple
team
pairing
sessions.
This
milestone
also
hosted
a
virtual
offsite
to
improve
alignment
between
the
data
and
product
intelligence
teams.
A
Jake
from
plan
said
that
we
had
several
successful
opportunities
to
collaborate
with
community
contributors,
contributors
to
add
new
features
and
functionality
to
gitlab.
One
standout
example
is
croquis
diagram.
Support
cz
from
global
search
said
that
led
by
rpm
john,
the
team
released
the
kickoff
video
collaboratively
valerie
from
ux
said
that
the
auto
devops
think
big
session
was
a
great
cross-team
collaboration
with
pm
and
director
participation
leading
to
a
new
vision
of
auto
devops.
A
A
A
Moving
on
to
results,
nick
from
geo
said
that
we
shipped
version
snippet
replication
and
completed
our
disaster
recovery
by
a
a
viable
maturity.
Epic
craig
said
that
we
have
addressed
the
final
remaining
tables
without
a
primary
key
and
have
unblocked
the
ability
to
use
logical
replication,
an
important
prerequisite
for
no
or
minimal
downtime.
A
major
update
to
postgres
12.x
craig
also
said
that
the
final
updates
for
supporting
automated
re-indexing
have
been
shipped,
and
we
have
already
started
successfully
using
our
reindexing
scripts
in
production
and
removing
index
bloat.
A
Finally,
from
on
the
memory
side
of
things,
craig
said
that
enabling
query
caching
for
the
loan
balancer
yielded
some
pretty
great
results.
To
quote
in
the
comment,
this
is
a
superb
improvement.
Thank
you.
It's
a
10
reduction
in
tps
across
the
fleet
as
measured
from
postgres.
A
For
the
efficiency
value
nick
said
that
we
followed
up
on
a
previous
retro
item
to
have
more
regular
acceptance.
Demos
douglas
and
gabriel
walked
us
through
setting
up
a
patrony
standby
cluster
on
a
secondary
site
and
akriti
did
a
demo
of
the
upcoming
maintenance
mode
feature
and
then
jake
said
we
were
able
to
effectively
use
deliverable
labels
to
highlight
top
product
priorities
for
engineers
and
ensure
we're
aligned
on
our
goals.
A
The
iteration
value
kyle
from
quality
said
that
the
calculation
for
m
rar
m-r-a-r
was
matured
with
the
issue
linked
there,
which
led
to
identification
of
5.7
million
mr
dollar
from
customer
contributions.
A
We
now
have
a
test
session
report
that
shows
what
test
case
ran
and
its
status
on
each
deployment.
This
will
show
us
in
one
picture,
and
then
he
lists
off
a
few
things
that
this
will
show
us.
Okay.
Moving
on
to
what
went
wrong
first
was
on
the
collaboration
side
of
things.
Jake
said
that
the
last
week
of
the
milestone
was
very
intense
and
confusing,
especially
with
regards
to
documentation.
A
We
had
some
confusion
around
when
feature
flag.
Functionality
should
be
documented,
as
well
as
when
docs
should
be
reviewed.
That
led
to
unnecessary
stress
and
crunch
proficiency.
Jake
said
that
life
around
the
holidays
can
be
difficult,
and
the
added
stress
for
some
some
interactions
between
the
pandemic
and
holidays
led
us
to
feel
less.
On
top
of
it
than
usual.
A
Matt
said
that
we
almost
doubled
the
size
of
ecosystem
of
the
ecosystem
team
recently
and
13-7
was
the
first
full
milestone
for
the
new
team.
However,
we
did
not
have
any
kind
of
transition
issue
or
checklist
that
team
members
could
follow
to
get
up
to
speed
faster
team
members
are
still
trying
to
learn
about
the
new
area
while
at
the
same
time
trying
to
deliver
new
features
that
are
high.
Priority
mech
said
that
an
issue
with
the
select
2
css
component
nearly
caused
the
previous
release
to
be
halted,
and
then
he
linked
the
issue
there.
A
I
also
said
that
omnibus
get
led,
mirror
pipelines
started
failing
after
webpack
acids
were
missing
for
the
iteration
value
ricky
from
verify.
Testing
said
that
we've
started
to
get
better
at
breaking
out
issues
and
we
are
not
sure
how
to
proceed
with
into
technical
investigations
and
separate
implementation
issues.
However,
we
aren't
doing
a
good
enough
job
time,
boxing
our
investigations
and
they
tend
to
drag
on
okay.
Now,
what
can
we
improve
for
collaboration?
Value?
Jake
said
that
we
want
to
improve
our
collaboration
on
documentation.
A
Specific
goals
include
always
including
docs.
In
the
same,
mrs
as
code,
if
there
are
many
mr's,
then
the
front-end
engineer,
em
decides
which
one
exposes
the
feature
to
the
user
for
docs
reviews
pinging
the
technical
writer
as
soon
as
there's
something
to
review
not
waiting
until
reviews
are
done,
then
we
can.
Then
you
can
ask
for
another
review
when
other
reviews
impact
the
ui
or
user
workflow
and
docs
need
to
be
amended.
A
A
A
suggestion
was
made
to
swarm
in
small
groups
tackling
the
refinement
of
more
complex
issues
or
when
a
larger
number
of
issues
need
refinement
for
results.
Jerome
said
that
our
team
has
been
moving
quickly
and
we're
now,
starting
to
run
into
performance,
scalability
and
efficiency
concerns
with
the
amount
of
metrics
we've
implemented.
A
We
need
to
spend
more
time
on
standardizing,
tooling
processes,
a
process
and
addressing
technical
debt,
and
craig
said
that
tooling,
tooling,
tooling.
The
research
into
our
two
gigabyte
efforts
reminded
us
how
difficult
it
is
to
measure
memory
performance
in
ruby,
okay,
and
then
we
have
a
few
for
efficiency
value
here.
Nick
said
that
we
can
do
a
better
job
of
making
sure
our
team
members
understand
the
infrastructure
of
our
staging
environment
beyond
just
the
geosecondary
atom
from
composition.
A
A
A
A
Craig
said
that,
with
the
new
year,
both
the
memory
group
and
database
group
have
an
issue
to
discuss
how
we
function
as
a
team.
What
processes
we
can
improve,
how
we
become
more
efficient
as
a
team,
etc.
It's
an
open
issue,
it's
an
open
issue
for
anyone
to
bring
suggestions
to
the
table
and
change
how
we
function
as
a
group,
rather
than
simply
continuing
to
do
things.
The
way
we've
always
done.
It
matt
said
that
the
issue
triage
process
for
our
team
could
use
a
better
process.
A
Okay,
thank
you
for
your
time.
Please
join
us
for
our
retrospective
discussion.
This
milestone.
It
is
going
to
be
a
little
bit
later
than
usual
it'll
be
next
week.
It's
actually
monday
january
11th
2021,
it's
11
p.m.
Utc!
It's
our
first
apec
friendly
retrospective,
which
is
great,
I
mean
that's
3pm,
pacific
time
included,
links
to
where
you
can
watch
it
on
youtube
or
use
in
our
internal
zoom
link.
A
We've
got
a
couple
topics.
We
want
to
talk
about
first,
one
was
kind
of
a
rollover
from
the
last
milestone
that
we
didn't
have
an
opportunity
to
get
to
that.
One
is:
how
does
your
team
handle
backlog,
refinement,
let's
share
tips
and
best
practices
with
respect
to
backlog,
refinement
or
sprint
planning
activities?
A
The
second
topic
we'll
talk
about
that.
A
few
people
brought
up
in
this
in
this
milestone
was
that
1307
was
a
transition
milestone
for
a
few
of
the
newly
expanded
teams
there
any
learnings
to
discuss
around
onboarding
new
team
members.