►
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
Hey
everyone:
this
is
mack
sutri
director
of
quality
gitlab,
and
this
video
is
the
overview
for
our
group
conversation
on
december,
the
14th
2020.
first
off.
I
want
to
highlight
the
progress
and
the
scope
of
our
okay.
This
quarter,
as
in
the
spirit
of
the
the
quality
department.
We
are
we're
continuing
to
gear
on
efficiencies
of
merge,
request
pipelines
and
average
ci
pipeline
duration.
A
Also,
we
have
added
the
focus
on
raising
raw
as
well.
We
ship
this
measurement
in
this
quarter,
which
I'll
highlight
in
a
bit
in
our
video,
as
well
as
for
the
product
okr,
we're
continuing
to
increase
the
product
quality,
and
this
quarter
will
focus
on
the
tooling
identification
of
trends
and
issues
and
also
fixing
them
and
for
overall
for
the
team.
We
are
increasing
our
maintainers.
A
A
Second,
is
delivering
on
key
engineering,
metrics
work
streams,
we'll
go
over
them
in
slide
10.
we
took
over
the
or
we
were.
We
are
facilitating
the
overall
progress
for
engineering
kpis
and
for
all
the
other
engineering
departments
as
well.
This
is
an
exciting
area
that
we
do
want
to.
We
are
looking
at
closely
to
make
sure
we
continue
to
provide
results.
A
Number
three
bugs
given
us.
We
are
an
open
core.
A
A
A
All
the
teams
in
quality
are
consistently
contributing
and
shoring
up
test
coverage
quarter
over
quarter
with
this
quarter
at
the
q4
it
being
one
of
the
highest
ever
that
all
teams
are
contributing
at
a
good
pace,
and
we
do
want
to
outline
a
performance
indicator
for
for
the
job
family
of
software
engines
and
tests.
That's
on
our
backlog,
kpis
really
proud
that
the
master
pipeline
has
been
stable.
It's
above
90
for
the
ninth
consecutive
month,
huge
kudos
to
the
engineering
productivity
team
and
kyle
who's,
leading
that
effort.
A
Duration
also
has
increased
the
decrease
to
under
one
hour
again.
Finally,
cost
has
uptake
quite
a
bit.
I'm
not
much
of
a
concern
here
and
review
app
deployment.
Success
rate
first
time
we're
hitting
99,
which
I'm
very,
very
proud
of
the
team
on.
There
are
two
new
metrics
here:
two
new
kpis,
it's
mtcc
for
s1
s2
bucks
mttc
stands
for
mean
time
to
close,
and
it's
a
new
measure
that
we're
measuring
how
fast
we
are
at
closing
bugs
and
that
segues
nicely
to
my
next
slide.
A
So
we
did
multiple
iterations.
First,
we
used
miss
slos,
which
didn't
really
resonate
with
a
lot
of
people,
and
it
wasn't
really
much
effective.
We
have
shifted
to
measuring
the
average
time
to
close
and
and
lately
pivoted
by
close
date
and
naming
it
mttc
to
to
line
up
with
all
the
other
indicators
from
infrastructure
security
on
mean
time
to
mean
time
to
dot
the
next
steps.
A
Here
we
are
planning
on
more
indicators
to
to
line
up
the
open
box,
the
age,
the
overall
age
and
the
bugs
that
are
not
severitized
or
uncharged
anjumra,
very
proud
of
the
team
on
delivering
this.
We
navigated
multiple
technicalities
importing
data
on
on
contributors
linking
them
to
to
arr,
and
now
we
finally
have
shipped
the
first
iteration
and
it's
also
related
to
our
three-year
strategy.
A
Next
up,
we
are
dealing
with
the
low-hanging
fruits
first,
we
want
to
ensure
that
we
account
for
all
contributors,
all
customer
contributions
and
the
projects
that
we
may
have
missed,
and
we
have
outlined
a
really
detailed
plan
here
to
execute,
with
within
r
d
and
also
with
partnerships
in
in
with
marketing
and
also
customer
success,
and
the
last
one
is
efficiency.
We
will
continue
to
improve
not
only
for
ourselves,
but
also
for
external
for
contributors,
efficiency
and
productivity,
as
well.
A
Next,
one
on
the
overview
product
development
workflow
has
been
updated.
I'm
really
happy
to
see
that
the
software
engineering
test
are
now
being
pulled
in
to
collaborate
further
now
in
the
design
phase,
and
then
we
outlined
that
if
there
are
to
be
quality,
test
plans
and
strategy,
it
should
be
done
at
the
planning
phase,
not
at
the
the
development
or
almost
shipping
phase.
So
this
would
move
us
closer
to
better
at
being
proactive
equality.
A
Next
up
is
the
update
on
the
centralized
handbook,
metrics
dashboards,
we're
currently
adding
indicators
from
security
and
infrastructure.
So
we
will.
We
are
planning
to
and
we'll
be
able
to
outline
the
security
vulnerabilities
mttr
for
each
product
group
and
also
pull
in
incidents
per
product
group
along
with
the
root
causes.
So
I'm
really
excited
to
provide
the
team
with
a
more
complete
picture
on
their
charter.
So
imagine
that
you
have
20
to
30
cars.
A
Next
up.
So
this
is
the
engineering
metrics
initiative
that
I
outlined
earlier
on
a
number
of
achievements,
the
this
past
this
past
month
a
month
and
a
half
mara,
was
also
addressed
or
helped
out
here
as
well,
and
a
number
of
things
from
ux
and
florida
development
and
some
of
the
working
group
trends
in
both
as
well.
A
You
can
see
more
on
our
process
and
we
have
an
open
board
that
shows
the
work
stream
that
we're
working
in
more
efficient
efficiency
pushes
so
we're
working
making
sure
that
our
team
is
productive
and
also
their
other
company
processes
that
we
are
working
as
well
apologies.
So
we
do
want
to
provide
a
single
social
truth
for
multiple
things.
A
On
the
next
slide
on
the
overview,
we
have
shipped
better
clarity
in
deployments.
So,
if
you
recall,
if
you
are
in
rd,
you
are
involved
in
the
release,
qa
issue
that
comes
closer
to
deployment,
we
we
provide
a
list
of
change,
sets
that
gets
they're
going
to
get
deployed
and
everyone
helps
out
with
testing.
Now
we
have
the
automated
test
reports
that
outlines
the
result
of
end-to-end
tests
and
the
automated
regression.
A
Essentially,
results
is
provided
for
traceability,
not
only
for
us
but
for
for
everyone
else
that
are
watching
us,
our
customers
and
the
whole
world.
Next
steps
we're
gonna
link
them
together.
So
when
you
have
something
deployed,
you
will
see
what
tests
were
ran
and
if
there's
an
incident,
we
can
easily
outline
if
there
are
any
tests
that
we're
missing
and
continue
to
to
shore
up
there.
A
A
So
when
you,
when
the
time
comes,
there's
a
little
to
to
no
manual
testing
at
all,
if
possible
and
then
lastly,
in
the
overview,
we
are
actively
participating,
collaborating
across
the
company
in
multiple
venues
in
the
working
group
so
outlining
outlining
them
here,
I'm
very
proud
of
the
the
progress
the
team
is
delivering.
A
That
concludes
it
for
our
overview.
There's
a
lot
more
information,
so
I
do
hope
that
you
spend
some
time
to
join
us
tomorrow
in
our
group
conversation
so
see
you
there.
Thank
you.