►
From YouTube: Quality Department Sept 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
A
First
off,
I
want
to
highlight
our
master
branch
pipeline
success
rate.
This
is
in
the
we'll
go
over
the
highlights
first
and
then
we'll
do
the
low
light.
Afterwards
master
brands
is
stable.
We
have
sustained
at
90
plus
over
the
past
five
months,
so
we're
keeping
this
in
in
the
green
state
for
review
app
in
the
highlights
as
well.
We
have
employed
corrective
actions.
The
stability
has
improved
from
the
last
month.
It
was
84
now
88
this
month,
we're
tracking
going
back
into
the
the
90
territory
again.
A
So
that's
great
news
for
oba
we're
making
good
progress
here
as
well.
We
made
a
significant
progress
in
july
and
august,
we're
still
keeping
it
under
target
now
some
context
here
with
a
focus
on
reliability.
We
have
a
shift
focus
on
closing
out
more
recent
issues.
Hence
you
will
see
the
age
not
going
down,
but
if
you
can
see
the
number
of
backlog
or
issues
are
are
going
down.
A
From
that
perspective,
on
the
highlights
of
the
cost
side
of
things,
we
are
maintaining
the
cost
of
merge
requests
it's
stable
at
seven
percent,
disclaimer
that
we're
not
we're
standing
we're
staying
at
the
line
here,
we're
not
planning
anymore
further
reduction
to
focus
on
reliability,
mr
coaches,
contributors
and
and
those
other
other
venues
of
business
opportunities.
A
Next
is
our
age
of
open
position,
so
we
are.
We
have
sustained
a
better
state
than
than
the
previous
quarters
that
our
open
position
is
reduced
in
october
at
40
days,
and
this
month
is
a
little
bit
of
an
uptick,
but
we
are
hovering
around
the
target.
We
are
maintaining
attention
here
now
on
to
the
the
low
lights
raw.
Unfortunately,
I
can't
give
visibility
in
this
review.
It
is
in
the
safe
dashboard
we're
working
on
providing
visibility.
There,
though,
that
the
health
hasn't
changed.
A
We
kept
this
the
same
as
before.
We
we're
putting
attention
towards
our
community
contribution
and
the
current
and
the
themes
there
open
community
age
atma.
This
is
on
a
slight
increase
in
the
short
term,
but
overall,
it's
on
in
the
same
trend.
It's
at
a
150
days
going
up
to
165.
In
the
last
few
weeks,
we
have
employed
a
stale,
mr
report
and
then
a
a
report
that
shows
really
old,
mrs
and
we
are
working
with
mr
coaches
to
to
fan
out
and
merge.
A
Please
do
keep
in
mind
that
we
do
have
also
focus
on
reliability,
so
their
attention,
the
attention
of
mr
coaches,
may
have
been
diverted
towards
other
improvements,
so
we're
also
giving
giving
headroom
here
as
well.
A
One
thing
to
note
that
the
edge
is
stable,
the
the
number
and
mars
are
seems
to
be
increasing,
so
there
is
a
backlog
that
we
need
to
clear
out
that
the
points
are
the
same
indicator
on
first
time.
The
failure
I
put
this
in
low
lights,
but
it's
not
getting
increasing.
It's
not
it's
not
getting
worse,
but
it's
great
that
the
team
is
staying,
the
line
hovering
at
our
target
at
15
minutes.
A
We
also
discovered
that
static
analysis
and
robocop
are
the
first,
the
most
common
failed
jobs
and
those
are
the
ones
that
are
being
run
first
in
low
lights,
oba
s2,
the
age
is,
is
worsening.
It's
not
great.
Again.
I
mentioned
that
the
team
is
focused
on
the
reliability
effort
so
well.
The
activities
have
been
towards
the
the
recent
issues.
Hence
we
see
the
backlog
is
decreasing.
So
even
though
the
age
is
increasing
that
the
background
issues
is
is
decreasing,
as
you
can
see
here.
So
that's
that's
good
news.
A
Once
we
have
more
headroom
we'll
be
focusing
on
more
of
the
the
age,
and
this
would
be
our
next
focus
on
on
bugs
going
forward.
Next
up
is
the
gearing
ratio
I
put
this
in
in
low
lights
intentionally,
even
though
we
do
have
improvements,
so
we
added
additional
two
more
higher.
Since
the
last
review,
we
have
been
successful
at
hiring
open
rows.
A
The
next
step
is
making
sure
that
the
the
the
graphics
to
the
visualization
maps,
the
prioritization
prioritization
model,
the
line
here-
is
still
doing
the
the
all
groups
we
some
groups
are
not
being
planned
to
have
an
sct,
yet
so
they're
new.
So
we
anticipate
having
showing
a
reduction
of
the
target
here
so
to
show
that
we
are
in
improving
the
state
moving
forward
in
the
the
list
of
the
the
low
lights
coaches
per
month.
It
reduced
down
to
19
earlier
in
the
last
month.
A
It
hasn't
reduced
further,
so
that's
great,
but
we
haven't
been
increasing
this
either
we're
focusing
on
the
contributor
contribution
reviews.
We
haven't,
pushed
push
hard
on
increasing
the
coaches.
Yet
though
this
would
be
another
focus
area
when,
when
the
team
has
has
a
lower
focus
on
improve
the
reliability
activities
and
then
focus
there
going
next
into
contributors,
we
have
a
hackathon
in
place,
though
we're
seeing
a
lower
trend
of
unique
community
contributors
per
month.
A
This
is
the
highest
area
of
focus
at
this
point
in
the
quality
department
and
and
the
marketing
as
well.
We
do
have
a
hackathon
ongoing
right
now
and
we
anticipate
an
increase
in
activities
so
we're
focusing
on
focusing
on
getting
those
those
new
contributors
and
unique
contributors
in
moving
forward
on
the.
I
would
like
to
jump
to
the
handbook,
mr
rate.
It
increased.
A
It
got
a
bit
better
last
month,
so
0.5
that
was,
we
are
still
maintaining
the
message
of
making
sure
things
are
documented,
iterating
it
breaking
it
down
and,
and
lastly
mr8.
This
was
reduced
in
august,
we're
working
on
adding
more
maintainers
in
quality.
A
The
perception
is
that,
with
the
focus
on
making
sure
things
are
working
fine,
a
lot
of
times,
it's
spending
towards
investigating
failures
of
tests
and
making
sure
we
have
clarity
there,
so
that
there's
the
discussions
and
the
issues
and
then
doing
the
on-call
process
and
discussions,
so
it's
not
eventually
captured
in
the
emrs
and,
lastly,
we're
going
to
close
it
off
with
okrs.
A
A
The
first
ocr
is
around
product
contribution
efficiency.
So
this
goes
into
the
line
that
I've
shown
low
light
in
in
mr
coaches
and
also
community
contributions.
We
are
focusing
on
the
number
of
contributors.
A
A
We
do
think
that
we
will
make
some
more
progress
here
on
on
implementing
a
heu
code.
Sync
performance
indicator,
so
this
measures
the
time
when
the
latest
code
on
our
side
lands
in
the
development
environment
of
jihoo,
and
that's
that's
key
on
ensuring
that
the
code
base
are
are
close
together
and
moving
towards
the
same
direction.
A
Next
up
on
the
second
okr,
the
theme
is
improving
product
quality,
making
progress
here
on
on
staging
environments
on
supporting
get
for
project
course.
We
still
need
to
pick
back
on
reducing
the
time.
The
first
failure,
as
you
saw
before
we
are
maintaining
the
line
at
15
minutes
and
then
so
we're
not
scoring
any
any
any
success
here.
A
The
team
is
in
is
going
to
deliver
corrective
actions.
That's
inside
the
real
quality
making
sure
the
tests
are
are
working,
solid
and
stable,
and
that's
still
in
progress.
We
we
do
anticipate
more
progress
here
in
the
end
of
the
quarter
and
engineer
allocation
dashboards,
so
the
labels
have
been
created.
We
need
to
deliver
the
first
iteration
of
the
dashboards
we
will.
We
are.
We
are
anticipating
some
additional
progress
here
for
for
the
dashboards.
A
Lastly,
on
the
growth,
our
team
and
the
hiring
is
doing
well
360
we're
grading
according
to
the
completion
and
also
the
conversation
with
the
team
members,
since
it's
a
bit
low
and
we
are
making
progress
on
implementing
the
the
job
family
performance
indicators,
and
that
is
it
for
a
preview
of
our
key
review.
I
hope
to
see
you
all
and
also
answer
your
questions
talk
soon.
Thank
you.