►
From YouTube: Quality Department Nov 2021 Key Review Prep
A
First
off,
starting
with
community
contributors
per
month,
so
despite
the
challenges
in
the
current
quarter,
I'm
happy
to
say
that
we
have
increased
our
monthly
community
contributors
to
100
in
october,
and
this
is
the
highest
it's
been
in
the
past
six
months,
though
it's
still
under
our
target
of
120..
A
This
is
due
to
multiple
outreach
events.
We
did
two
outreach
events
this
past
quarter.
There
is
a
high
qualifest
and
also
hackathon
our
build
out
of
the
contributor
success.
Team
is
top
priority
and
and
we'll
be
looking
at
product
groups,
stale
community,
emotion,
quests
also
as
well.
This
is
our
top
focus
at
the
moment
in
in
q4,
going
into
ma,
we
haven't
been
focused
on
contributing
organizations.
A
However,
I've
attached
the
screenshot
in
the
agenda
that
shows
a
slight
improvement
in
september
and
october
in
september,
even
though
it's
true
that
this
is
volatile,
we
expect
continued
volatility
as
we
focus
on
the
base
contributors.
We
expect
more
renewed
focus
in
mara
coming
into
q1
next
year,
going
into
a
master
pipeline
stability.
A
This
has
dipped
slightly
at
89
percent,
and
this
is
due
to
us
intentionally
removing
some
retry
mechanisms
to
accurately
measure
flaky
tests,
so
the
retries
were
hiding
some
of
these
flaky
tests,
which
we
were
trying
to
get
to
the
bottom
of.
We
expect
this
to
to
improve
and
the
team
is
continuing
to
continue
on
to
to
fine-tune
and
optimize
our
stability
moving
to
a
rewrap
deployment.
Success
rate
the
recovery
has
been
increasing,
and
this
is
now
above
90,
and
we
expect
more
more
momentum
in
increased,
more
momentum
in
recovery.
A
I
wanted
to
highlight
that
the
dip
earlier
was
due
to
us
expanding
testing
against
rewraps,
so
we
added
more
end-to-end
tests,
which
runs
against
all
deployed
review
apps.
So,
overall,
this
is
a
net
gain
in
profits.
For
us,
we
are
now
running
review
apps
with
more
tests
running
against
it,
in
addition
to
the
recovery
of
momentum
of
stability
going
on
to
time,
first
failure
we're
still
hovering
around
the
target,
though
it
increased
slightly
in
in
the
past
two
months,
and
this
is
due
to
additional
testing
as
well.
A
We
added
more
end-to-end
tests
within
in
the
overall
pipelines,
and
this
caused
some
some
increase
in
in
the
time
to
time
to
failure.
We
will
still
be
looking
at
optimizing,
bottleneck,
jobs
and
then
running
the
right
tests
at
the
right
place
going
into
s1,
oba,
s1
oba
has
been
decreasing,
and
this
100
days
is
also
a
new
target.
Previously
it
was
150
days
so
we
have
hit
our
previous
target
and
also
this
current
target.
We
are
now
under
100
days.
A
I
also
want
to
highlight
that
we
have
been
focusing
not
only
on
the
age
but
also
the
lowering
the
numbers
of
open
s1
as
well.
We
we
have
seen
great
progress
here.
We
will
continue
to
focus
on
s1
over
on
s2.
The
age
has
been
increasing.
However,
I
want
to
point
out
that
the
number
of
issues
has
been
decreasing
and
this
is
because
the
current
focus
is,
on
the
recently
closed,
s2s
we're
still
focusing
on
s2o
bus.
A
We
have
a
weekly
refinement
going
on
which
we
are
reviewing
new
iterations
of
the
reports,
and
we
have
changed
some
mechanisms
to
highlight
all
the
s2s
going
forward.
So
we
expect
to
see
some
improvements
here
when
those
mechanisms
land
jumping
forward
to
merge,
request
pipeline
duration.
We
are
seeing
a
sustained
momentum
of
decreased
duration
and
this
is
kudos
to
the
team
on
implementing
selective
test
execution
which
shortens
the
front-end
pipelines
and
then
also
end-to-end,
test,
optimization,
which
also
shortened
the
end-to-end
test
pipeline.
We're
hoping
to
hit
the
target
in
the
future.
A
Hence
the
age
isn't
benefiting
from
the
momentum.
We
are
prioritizing
a
breakout
analysis
of
steel
and
mars
by
product
groups,
and
we
hope
to
have
that
as
an
update
in
the
next
next
review.
I
want
to
take
the
time
to
highlight
two
new
measures
that
we
have
added
for
end-to-end
tests.
One
is
the
average
duration
of
end-to-end
test
suits
this
measures.
The
efficiency
of
our
end-to-end
tests,
we're
still
establishing
a
baseline.
Hence
the
target
and
target
is
cbd
and
health's
unknown
same
here
as
well.
A
A
A
Also
happy
to
report
that
we
have
realized
some
recent
improvements
in
decreasing
location
factor,
and
this
is
due
to
us
hiring
in
efficient
areas
for
new
hires
and
lastly,
the
promotion
rate
is
slightly
above
target,
but
not
worrisome
due
to
the
the
small
department
population
size
going
on
to
a
recap
of
last
quarters.
Okay
I'll
be
highlighting
some
wins
and
also
challenges
and
opportunities.
A
First,
off
increasing
contributors,
we
were
not
able
to
hit
our
target
of
120,
but
we
were
able
to
increase
up
to
100
in
october.
Overall,
it
hasn't
been
increasing
at
the
trajectory
that
we
want.
We
are
doing
many
experiments
in
q4
to
identify
the
most
efficient
way
to
increase
contributions
and
contributors.
A
Another
challenge
here
is:
we
were
not
able
to
increase
in
our
coaches
as
much,
and
this
is
also
due
to
us
or
myself
being
overly
ambitious.
We
did
not
get
the
bandwidth
to
to
improve
in
our
coaches
materials.
We
aim
to
pick
this
up
again
sometime
in
q1
on
to
improve
product
quality,
reducing
time
difference,
failure
tiff.
We
create
this
as
a
zero,
because,
overall,
it
didn't
or
decreased
to
our
internet
target
of
of
10
minutes,
though
the
team
has
been
making
progress.
A
Some
of
the
challenges
includes
new
changes
in
the
pipeline
that
the
team
were
not
aware
of
that
increased
the
duration,
so
it
didn't
net
into
an
overall
decrease
for
the
team,
though
this
has
been
an
area
of
focus
and
we
are
also
doing
experiments
in
q4
to
identify
more
ways
to
further
decrease
tiff
down
to
down
to
12
or
to
10..
A
We
delivered
full
commitments
to
support
project
horse,
so
that's
a
that's
a
big
win
and
then
on
to
the
kosovo
team
members
a
key
highlight
here
is
we
implemented
two
job
family
performance
indicators
for
the
scts,
and
that
was
the
average
age
of
quarantine
tests
and
also
the
duration
of
our
test,
suite
that
wraps
up
the
preview
video.
We
look
forward
to
your
questions
and
to
the
discussions
tomorrow
in
the
key
review.
Thank
you.