►
From YouTube: Quality Department May 2021 Key Review Prep
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
Hi
everyone:
this
is
mikk
sutrai
vp
of
quality,
and
this
is
the
video
prep
for
our
key
review
for
the
month
of
may
2021
calendar
year
before
I
dive
into
the
metrics.
I
want
to
go
over
the
changes
we've
taken
from
your
feedback
from
our
last
q
review
and
we'll
go
through
our
current
state
of
affairs.
Afterwards,
first
off,
I
wanted
to
say
that
we
have
moved
ra
from
the
engineering
division
to
kpi
at
the
quality
department
level.
A
A
A
Let's
go
ahead
and
dive
in
our
current
state
of
affairs
raw.
This
is
listed
as
one
of
our
low
lights.
We
repeat
last
quarter
at
18
million
mr
dollars.
However,
in
in
in
the
current
quarter,
we
have
a
slow
start.
We
need
to
scrounge
more
and
then
work
work
upwards
with
the
community.
We
we
have
a
start
of
the
current
quarter.
At
500
k.
A
We
have
an
ocr
to
elevate
this
to
30
million
this
quarter.
We
have
around
17
million
in
the
pipeline
and
we
work
further
towards
getting
these
in
my
merch
and
working
with
our
with
the
wider
team
on
this.
I
do
want
to
note
that
the
attention
and
focus
of
my
has
been
diluted
for
in
favor
of
a
key
business
opportunity,
and
I
will
leave
it
as
that
as
an
update
there.
A
Next
up
is
the
percentage
of
merge
requests
from
from
the
community.
This
has
been
increasing
in
the
last
month
of
april.
We
need
to
define
a
target
and
we
can
discuss
that
in
in
the
meeting
together.
A
Next
up
is
the
average
successful
merge
request
pipeline
duration.
This
is
captured
as
part
of
a
highlight
because
we
have
improved
in
april
from
66
minutes
down
to
55
minutes.
We've
also
switched
out
some
infrastructure
for
the
same
cost.
I
believe
it's
an
n2
standard
dash
2
to
help
with
the
performance
and
cpu
and
you're,
seeing
some
improvements
there.
A
A
We
expect
this
to
to
even
out
as
we
collect
more
data.
Next
up
is
master
pipeline
success
rate.
So
good
news
is
that
we
have
stabilized
the
trend.
The
reason
for
the
the
dip
and
the
lower
trend
earlier
is
flaky
specs,
and
we
encountered
a
segmentation
fault
in
our
pipelines.
A
The
segmentation
fault
is
being
resolved,
resolved
partially
we're
still
working
through
to
solve
it
for
good,
and
we
have
a
kr
in
this
quarter
to
address
the
the
flaky
specs
as
well,
so
that'll
be
a
focus
for
our
teams
moving
towards
a
revamped
deployment.
This
is
in
the
highlights
we
have
increased
in
april
from
before
from
94
to
97.
A
The
dip
in
the
current
month
is
because
we
are
expanding
the
use
of
review
apps
and
that's
that's
good
news.
We're
going
to
enable
this
for
all
much
requests.
We're
also
going
to
run
all
our
qa
smoke.
Tests
against
review
apps,
so
we'll
be
getting
more
testing
out
of
the
the
cloud
native
environments,
but
that
comes
at
the
cost
of
the
short
term,
we'll
be
seeing
these
short
term
destabilization,
because
we're
stretching
the
environments
to
the
limits,
but
I'm
very
excited
about
this
effort.
A
Soon
we
will
have
a
motion
press
for
for
all,
mrs
and
in
the
gitlab
project.
Next
up
is
a
mushroomquest
pipeline
average
time
to
failure.
This
was
a
a
relatively
new
metric
measurement.
In
april
we
stabilized
at
around
51
minutes
again.
The
the
spike
in
data
is
because
we
only
have
a
limited
picture
within
may
and
it
isn't
our
normal
distribution
of
data.
We
expect
this
to
to
even
out
next
up
is
the
defect
matrix.
A
So
this
is
a
continuation
of
iteration
we're
no
longer
measuring
mttc
we're
not
measuring
average
age
of
open
bugs
s1
as
twos
for
us.
Once
we've
set
the
target
at
below
150
days.
We
do
think
we.
We
have
a
really
good
opportunity
to
improve
things
here,
because
the
numbers
of
s1
are
low.
We've
gone
through
roughly
half
of
the
current
open
ones
and
remind
people
to
to
update
their
security
and
close
it
out.
A
There
was
also
two
of
these
high
severity
long
whole
bugs
that
are
that
have
been
fixed
and
we
expected
that
number
to
reflect
here
in
the
future
as
well.
So
this
would
be
the
the
the
lower
ramp
to
improve.
A
Next
up
is
the
the
symmetric
for
open,
s2
bucks.
We
will
set
a
target
at
300
days.
We
want
to
move
towards
the
next
iteration
and
lower
this
down.
This
will
be
our
next
key
focus
after
solving
open
s1
and
to
make
sure
that
we
hear
your
feedback.
Clearly,
this
is
just
a
one
iteration,
the
next
iteration
we
are
thinking
of
how
to
capture
the
whole
achievements
of
both
open
and
closed
box,
and
we
do
want
to
turn
this
into
a
more
effective
measurements.
A
Currently,
it
is
only
measuring
all
of
open
bugs
next
up
is
our
software
insurance
test,
gearing
ratio.
We've
made
two
hires
from
the
last
time
we
talked
so
one
in
the
pipeline
authoring
group
and
one
in
the
import
group.
We
improved
this
slightly.
We
have
two
positions
open
for
as
part
of
our
staffing
requests.
A
We
continue
to
work
on
that
and
also
we
have
a
task
to
ensure
that
we
put
our
sats
in
the
most
highly
needed
areas
and
that's
it
for
our
overview
of
our
key
review
and
I
hope
to
see
you
all
tomorrow.
Thank
you.