►
From YouTube: Quality Department March 2021 Key Review Prep
Description
Quality Department March 2021 Key Review Prep
A
A
A
First
off
is
the
bug
severity,
one
mttc,
which
is
mean
time
to
close,
we
believe
this
metric
is
in
a
good
state.
The
status
is
green,
also
I'll
call
out
that
the
percentage
of
slo
attainment
has
been
trending
upwards.
I
believe
it's
90
plus
now.
I
believe
the
the
s1s
are
in
a
good
state.
A
However,
with
mtc
cs2
in
the
last
meeting,
we
saw
an
uptick
of
a
closure
time
in
in
in
february,
unfortunately,
we're
seeing
the
same
in
march
as
well,
but
we
do
have
an
outcome
of
an
investigation
thanks
to
kyle
webers.
A
The
uptick
is
because
the
teams
are
going
in
and
closing
out
old,
bugs
that
are
invalid
and
not
not
reproducible
anymore.
We
have
an
investigative
issue
here,
linked
that
most
of
these
are
closed
as
non-reproducible.
They
don't
have
a
milestone
in
it.
It
wasn't
packed
to
a
release
and
it's
it's
also
not
assigned
and
we're
we're
doing
more
investigation
there.
A
If
we
should
capture
it,
we
still
think
it
should
be
captured
because
it
signals
a
healthy
adjustment,
but
the
team
is
needs
to
be
aware
of
why
the
numbers
go
up
because
of
that
we
have
labeled
this
as
as
orange
and
not
not
red.
A
It
has
our
attention
and
we
will
keep
a
close
eye
on
it.
Moving
on
to
the
average
successful
merge
request
pipeline
duration.
This
has
been
trending
up
recently,
and
this
is
because
we
have
some
transient
failures
and
also
some
cache
misses.
A
We
believe
that
the
the
correction
is
already
underway
listed
here
in
the
issues
we're
keeping
a
close
eye
on
it.
We
want
to
move
this
down
closer
under
60
minutes
going
forward.
We
believe
the
corrections
are
underway.
A
We
should
be
seeing
some
improvements
coming
in
next
month,
moving
on
to
master
pipeline
success
rates,
it's
been
stable,
but
it's
been
trending
down
slightly
differently,
and
this
is
because
new
longer
running
tests
have
been
added
to
to
the
pipelines,
and
our
team
has
caught
this
at
the
very
tail
end
where
it's
it's
been
merged
already.
We
have
already
enacted
some
corrective
actions.
If
you
see
from
the
linked
merge
requests
here-
and
I
believe
we
should
be
seeing
improvements
coming
in
next
month
as
well.
A
We
don't
have
historical
data,
unfortunately,
to
show
for
this
chart,
but
from
a
snapshot
perspective
we
we
know
this
has
increased
from
last
month
from
95
to
97,
and
the
team
has
been
keeping
a
close
eye
here.
A
We
also
have
planned
action
items
underway,
trying
to
move
the
needle
here
upwards
in
the
future
as
well.
Moving
to
the
next
one,
I'm
very
excited
for
this
metric.
This
is
an
achievement
from
the
team
last
last
month.
This
is
a
new
metric.
This
is
a
measuring
average
type
average
time
to
failure.
A
A
Moving
down
to
handbook
update
frequency
rate.
This
is
kept
at
red,
it's
improved
from
the
last
it
improved
in
february,
compared
to
the
month
before
a
debate
is
still
under
target.
We
are
considering
having
a
round
down
to
1mr,
instead
of
1.1,
to
ease
with
socializing
and
encouraging
the
engineers.
So
if
every
everyone
in
the
department
can
do
one,
mr
per
month,
we
should
be
in
a
good
spot,
so
we
will
look
to
champion
small
iterations
and
being
more
handbooked
first
as
well.
A
The
last
of
the
key
is
a
non-headcount
plan
versus
actuals.
We
are
green
here,
I
believe
you're
only
at
31
of
the
budget.
Moving
on
to
the
regular
performance
indicators.
This
is
a
relatively
new
metric
as
well.
It's
measuring
our
percentage
of
slo
attainment.
A
This
is
where
I
vocalized
earlier
that
for
s1s,
oh
okay,
we
have
apparently,
this
month
we
are
at
100
entertainment.
So
all
the
issues
all
the
closed
s1s
are
at
or
below
slo
target.
So
this
is
great
news.
S2
is
is
hovering
steadily
at
60,
I
believe
and
we're
keeping
an
eye
on
it.
We
don't
have
a
target
set.
Yet
this
is
a
supplemental
indicator
to
our
mttc
and
defects.
So,
overall,
this
child
has
been
relatively
the
same.
A
We
do
think
that
there's
a
the
team
is
focused
on
s2s
and
we
think
that
the
uptick
in
closure
time
is
a
is
a
facet
that
we
are
cleaning
out
the
backlog
of
s2s
we're
monitoring
this
this
metric
closely.
A
Since
it's
been
trending
up,
we
haven't
adjusted
the
the
grading
here,
I'm
going
to
touch
on
these
two
relatively
quickly.
This
is
also
a
supplemental
measurement
on
the
average
age.
A
Recently
we
have
we're
measuring
average
age
of
open,
s1s
and
s2s.
The
age
has
been
hovering
steadily
and
we're
keeping
a
close
eye
on
it.
We
haven't
set
up
a
target
yet
for
these
metrics
moving
on
to
percentages
of
unknown
severity,
we
have
been
hovering
steadily
at
30
percent
before
so.
This
is
bugs
without
severity,
so
the
unknown
unknowns.
It's
been
upticking
recently
in
in
the
recent
month.
A
The
team
is
keeping
an
eye
on
this
and
we
do
think
that
some
automated
solution
here
will
help
as
well
and
we
are
attracting
those
moving
on
to
community
mean
time
to
merge.
It's
been
turning
down
recently.
The
team
has
a
target
set
now
at
10
below
10
days,
we're
working
closely
with
the
community
relations
team
on
this
metric
next
up
is
community.
Unique
community
comes
your
viewers
for
a
month.
This
has
been
trending
lower.
Recently,
it's
a
concern
on
our
lens
as
well.
A
A
Coaches
and
our
coaches
were
not,
we've
been
slowly
increasing
thanks
to
all
the
departments
in
engineering,
we
have
a
an
issue
track
for
this
quarter
to
have
mr
coach
specialties,
so
development,
coaches,
test,
quality,
coaches
and
ux
tech
writing,
coaches,
and
this
should
help
improve
this
metric
in
the
coming
in
the
coming
months
as
well.
A
Next
up
is
percentages
of
feature
in
contributions
and,
I'm
happy
to
say
we
have
hit
the
30
target
we
said
earlier
before,
and
it
seems
to
be
on
an
upwards
trend
on
the
narrow
amount
rate
we're
tracking
closely
as
well
we're
holding
steadily
at
six
seven
and
six.
It
hasn't
reached
the
target.
Yet
we're
still
monitoring
this.
I
believe
the
the
on-call
process,
the
triage
and
the
working
group
lately
has
been
stretching
the
team
thin.
A
So
this
has
been
taken
an
effect
on
on
the
outputs
of
the
team,
average
costs
and
and
pipelines
emerge
requests.
I
believe,
has
been
stable,
we're
missing
historical
data
here
as
well,
so
we
could
not
show
you
the
rest
of
the
chart.
There
are
issues
underway
that
we
are
we're
tracking
on
on
these
two.
Those
costs
has
been
changed
to
a
regular
rpi.
We
are
focused
on
mean
time
to
failure
and
duration
moving
to
the
the
next
change.
So
we
we
don't.
A
We
didn't
have
hiring
activity
in
the
past
months,
but
the
adjusted
uptick
in
average
location
factor
was
due
to
a
geostone
location
factor
iterations
and
lastly,
our
hiring
hasn't
been
improving,
as
of
yet
we're
still
under
under
target.
I
do
think
that
if
we
can
improve
the
engineering
productivity
job
family
on
this,
we
have
we
are
working
in
the
the
realms
of
the
hiring
priority
sheet.
A
We
could
make
more
progress
in
the
hygiene
across
other
projects
that
given
light
as
well
and
lastly,
as
a
as
a
brief
tag,
our
team
is
driving
raw
overall
and
have
good
news
to
share
that.
As
of
this
this
month,
we
have
hit
a
high
point,
we're
at
16.3
mr
dollars
million
mr
dollars
for
for
this
month,
and
we
we're
tracking
multiple
collaboration
with
customer
success,
community
relations
and
the
community
as
well
to
to
track
this
and
the
terms
that's
it
for
our
preview.