►
From YouTube: Quality Group Conversation Prep Jan 2022
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'd
like
to
go
over
our
okrs
and
then
a
key
update
on
some
of
our
metrics,
some
key
initiatives
and
then,
lastly,
closing
out,
with
an
overview
of
our
work,
detail
work
within
each
teams
and
top
departments.
A
Well,
let's
start
off
with
okrs
for
increasing
quality
of
our
product,
we're
making
great
progress
on
boosting
our
deployment
confidence
new
staging
environments
is
captured
here,
we'll
be
providing
more
updates
later
in
the
call
guru
progress
there.
We
are
making
incremental
updates
and
progress
in
reducing
our
time
to
first
failure,
which
is
tiff.
A
A
Onto
delivering
engineering
efficiencies,
we're
making
good
progress
on
adding
test
coverage,
documentation
for
our
reference,
architectures
and
probation
tools,
which
is
get
we
are
doing,
experiments
making
good
progress
on
increasing
community
contributors,
with
the
highlight
of
this
quarter
being
recognizing
contributors
that
keep
coming
back
to
us.
More
updates
here,
also
as
well,
jihu
and
ailment
is
doing
well.
We
have
the
thule
in
place.
They
are
migrating
over
to
their
assassins
since
this
quarter,
and
so
far
progress
is
continuing.
A
A
We
also
have
a
lot
of
qe
team
members,
our
software
engineers
and
tests
doing
ride-alongs
interacting
with
our
customers
and
increasing
customer
empathy.
However,
there's
a
risk
in
meeting
our
hiring
plans.
Our
recruiting
team
is
doing
the
best
that
they
can
we,
but
we
do
have
a
large
backlog
of
positions
to
backfill.
This
is
also
a
key
key
focus
for
us
for
the
remainder
of
the
quarter.
We
will
prioritize
the
most
impactful
positions.
A
First,
a
brief
key
highlight
on
our
metrics
contributors
per
month
has
increased,
let's
apply
for
it
later,
but,
however,
is
still
under
target.
We
are
going
to
renew
more
focus
in
quarter,
one
there's
a
potential
opportunity
for
a
customer,
tooling
contribution
back
to
us,
and
then
we
will
be
providing
more
updates
here.
A
Master
pipelines
ability
dipped
a
little
bit
due
to
making
it
more
accurate.
It
was
I
I
gave
this
update
before
it
was
measuring
some
of
the
vanity
mechanisms
with
test
retries
right
now
we
get,
we
have
removed
those
retries
to
measure
them
more
accurately.
Hence
the
dip,
but
the
metric
is
more
accurate.
Now
ryu
app
is
getting
more
stable.
I
think
it's
at
97
percent,
now
kudos
to
the
engineering
productivity
team
and
tiff
is,
has
been
decreasing.
We
expect
some
volatility
here.
A
There
are
more
experience,
experiments
coming
so
please
stay
tuned
to
that
on
box
s1.
It
has
gone
up,
and
this
is
because
we
have
closed
the
medium
age
ones.
The
remaining
population
is
now
one
of
the
oldest
bugs
oldest
s1
bucks,
and
we
we
will
continue
to
march
on
progress
here
in
closing
them
and
reevaluating
their
severity
s2
over,
because
the
whole
team
is
calibrated
on
scheduling,
newer
s2
over
so
age
is
increasing.
However,
we
do
see
the
backlog
is,
is
decreasing.
A
Next
up
is
increasing
contributors
really
exciting.
Here,
we're
collaborating
with
marketing
the
community
relations
team
key
highlights.
We
have
refined
and
then
polished
our
strategy
further.
We
now
have
a
clear
line
of
site
and
on
the
strategy,
how
more
contributions
should
work.
We've
identified
four
pillars
improve
the
velocity
of
the
contributions
scaling
out
the
community,
expanding
the
outreach
and
then
increasing
the
community.
The
contribution
value,
more
updates
in
the
strategy
doc
link
below
I
do
want
to
highlight
that
contributors
have
increased
last
quarter
within
the
past
three
months.
A
We
now
have
visibility
into
mura,
who
add
more
focus
here
in
q1
with
the
customer,
tooling,
contributions
back
to
us
and
we
shipped
a
hands-on
tutorial,
which
is
a
formal
recorded
video
walkthrough
for
the
gdk,
thanks
to
matthew
who
just
joined
our
community
success
team.
Thank
you.
Matthia.
A
Next,
up
we're
gonna
continue
on
with
experiments
to
recognize
contributors
focused
on
the
contributors
that
keep
coming
back
to
us
in
the
past
three
months.
This
is
so
that
we
sustain
the
progress
and
then
once
that
is
stable,
we
can
focus
on
new
contributors
coming
in
monthly
going
forward.
I
mentioned
customer
environment
check
tool
contribution
already.
This
is
a
an
enterprise
customer
wanting
to
contribute
back
to
us
super
excited
here.
This
also
help
with
reference
architectures
and
then
making
sure
environments
audits
are
audit
audit.
Accordingly,
community
mrh
decreases
still
a
priority.
A
We
will
deliver
the
joint
strategy
with
the
community
relations
team
and
then
also
in
q1,
look
forward
to
more
more
hackathons
an
update
on
new
staging.
This
has
been
a
a
big
rock
project
between
quality
and
infrastructure.
I
want
to
call
out
leaders
there,
steve
mary
and
amy,
for
for
their
support
key
highlights.
We
now
have
two
environments
up
and
running.
We
have
improved
the
existing
one.
The
we've
added
incompatible
version
validation.
This
is
70
complete.
A
A
new
environment
has
now
been
set
up
around
60
companies.
This
is
where
all
the
engineers
can
go
in
and
test
admin
roles,
more
paid
tiers
and
it
has
the
exact
same
deployment
category
staging.
So
I
think
of
two
pair
two
environments.
Now,
in
parallel
with
the
same
deployments,
more
testing
is
being
democratized
and
we
plan
to
add
more
test
data
around
this
area.
A
We
also
shipped
more
documentation
and
a
video
overview
as
well
a
an
overview
of
the
environments
how
they
play
with
each
other
is
down
below
a
highlight
that
the
ones
in
in
in
white
and
green.
That's
it's
the
new
environment.
This
is
built
on
our
10k
reference
architecture
and
also
right
now,
it's
in
the
same
parallel
workflow
as
our
existing
or
legacy
staging.
A
Lastly,
other
initiatives
contribution
efficiency
going
on.
Well,
we
have
a
new
working
group
coming
up
soon,
which
is
called
the
demo
and
test
data
work
group.
This
aims
to
improve
our
sample
data,
set
to
make
it
more
usable,
more
customer-facing
and
then
realize
efficiencies
into
our
test
data
as
well
and
learnings
from
there
going
into
engineering
analytics.
We
have
some
some
team
changes,
so
we
are
with
a
low
level
of
stream
lagging
behind
this
quarter.
A
However,
we
are
first
focusing
on
the
two
key
most
important
areas,
which
is
the
completing
the
ci
cost
dashboard
for
a
week
for
user
strategy
and
also
making
sure
we
ship
the
backlog
security
pis
from
last
quarter.
This
is
ngrc
we're
doing
well
with
the
psychological
safety
training,
we're
continuing
to
make
progress
on
engineer
locations,
dashboards
for
contacts
for
people
who
have
just
heard
of
it
this
that
dashboard
is
aimed
to
provide
better
visibility.
A
How
work
in
engineering
that
is
being
requested
from
each
departments
is
being
worked
on
and
how
they're
being
prioritized?
We
just
discovered
that
we
do
need
to
include
the
ux
department
going
forward
to
help
outline
provide
visibility
into
sus
impacting
work.
The
top
level
views
by
producer
has
been
refined
this
past
this
past
month.
We're
going
to
continue
to
make
progress
here,
moving
on
to
engineering
productivity,
great
progress
on
oklahoma.
A
Overall,
you
want
to
highlight
the
experiments
in
reducing
tiff
and
also
the
three
experiments
that
we're
doing
to
reduce
community
contribution
age:
okay,
deep
dive
on
the
metrics
from
the
engineering
productivity
side.
As
I
said
before,
review
app
stability
has
been
increasing.
Super
proud
of
the
team
here
for
context
it
did
here
was
because
we
expanded
testing,
we
increased
the
number
of
tests
and
we
did
communicate
out
that
it
was.
A
It
was
going
to
take
a
dip,
and
now
we
are
we
in,
in
spite
of
all
the
increased
testing,
we
have
now
repaired
the
stability,
so
overall
net
gain
and
increase
ability
really
really
really
cool
massive
pipeline
success
rate.
This
was
this
is
an
area
of
focus.
We
do
have
some
iterations
coming
in
to
move
this
back
up
higher.
A
A
A
I
mentioned
oba
s1
s2
before,
even
though
the
age
is
increasing,
you
can
see
that
the
backlog
is
decreasing
and
with
the
s1.
This
is
not
the
hardest
ones
that
we
are
focusing
on.
These
are
the
legacy,
as
ones
that's
been
around
for
a
long
time.
We
aim
to
re-evaluate
severity,
whether
it's
it's
still
true
or
not,
and
then
aim
to
make
sure
that
there
are
no
outliers
in
age
for
us
is
currently
where
the
team
is
focusing
on
the
newer
s2s.
A
Once
the
backlog
is
clear,
we
anticipate
the
h
to
come
back
down
again.
We
do
have
eyes
on
deck
here,
to
reduce
over
overall
great
new
pis
for
the
age
of
quarantine
tests
and
then
the
duration
of
tests.
A
key
call
out
that
we
realized
that
the
mr
rate
for
our
department
has
been
lower
this
past
month,
we'll
be
focused
on
the
mr
rates
in
q1
and
and
q.
The
kiwi
sub
department
will
be
helping
to
drive
the
progress
here.