►
From YouTube: Quality Department Group Conversation Preview 2021-04-05
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
Hey
everyone:
this
is
mack.
I
am
the
director
of
quality
in
engineering,
and
this
is
the
video
preview
of
our
upcoming
group
conversation.
A
First
off
I'd
like
to
welcome
andre
he's.
A
newly
added
team
member
in
dev
he'll
be
the
counterpart
for
our
import
group.
We've
been
lacking
a
software
engineering
test
in
this
area
for
a
while
with
testing
of
imports
into
our
integrations
and
third
party
tooling.
So
this
is
a
very
welcome
addition.
Indeed
welcome
to
the
team
andre
moving
up
next
to
our
okrs,
we're
making
really
good
progress
overall
for
the
department.
A
The
the
highlights
would
be
more,
which
I'll
touch
on
later
in
down
in
the
later
slides,
we're
tracking
overall
above
50
percent
in
general,
there's
a
slight
attention
that
we
need
to
give
to
increasing
the
mr
coaches
and
specialties.
These
are
the
ones
that
are
weighing
down
the
overall
score
and
we
also
have
a
career
metric
survey
for
all
jobs
in
the
in
the
department.
A
Overall,
I
think
we'll
be
tracking
this
pretty
well
ending
at
around
70
percent
on
average
for
all
the
okrs
at
the
end
of
the
quarter,
we
still
have
one
month
left.
So
great
job
to
the
team.
Thank
you
very
much.
Moving
on
to
the
top
of
mind,
as
always
top
is
always
raw
and
our
three-year
strategy.
I
think
that's
our
goal
of
being
an
open
core
company,
making
sure
that
we
are
always
working
well
with
our
contributors
in
the
wider
community,
wider
community.
A
We
have
great
updates
here,
so
please
hold
on
to
to
the
screen
for
a
bit
we'll
touch
on
that
number.
Two
is
engineering
metrics,
we're
always
improving.
A
You
can
see
that
we
shift
a
lot
of
improvements
in
the
last
month
or
so,
and
making
sure
that
all
departments
in
engineering
are
productive
and
measuring
what
matters
and
communicating
that
to
the
wider
team
pipeline
efficiency,
we're
always
high
on
reducing
expense,
while
still
keeping
things
fast
and
stable
community
efficiency,
and
then
other
efficiency
pushes
we'll
go
down
in
detail
the
things
that
change
this
time
around
is
number
six.
We
move
this
up.
The
gearing
ratio
is
now
an
area
that
we
want
to
improve.
A
A
Up
next
is
seven
career
growth
of
our
team
members.
This
was
a
top
action
item
from
our
engagement
survey
and
this
quarter,
I'm
very
proud
to
say
that
we're
tracking
not
only
having
career
conversations
with
with
your
manager.
We
also
enabling
team
members
to
complete
one
career
growth,
development
skills,
training
as
well
a
learning
activity
and
we're
tracking
really
well
really
really
well
in
that
issue
as
well.
A
The
last
one
on
on
the
list
is,
I
would
like
to
have
more
performance
indicators
for
all
the
job
families,
so
the
sct
job
family
is
the
the
one
that
we're
gonna
work
on
next
on
duration
and
efficiency
of
tests
overall
kpis,
a
brief
update
here,
raw
continues
to
increase.
I
believe
we
have
a
site
that
touched
on
the
the
latest
number
mtcc
mean
time
to
close
s1
s2s
we
are
on
on,
we
are
healthy.
Overall
s1
is
stable.
A
There
was
a
recent
spike
in
s2s
and
it's
not
because
of
a
bad
thing.
It's
because
we
found
out
that
teams
kudos
to
you
are
going
in
and
cleaning
out
old
old
issues,
one
year
plus
old
issues,
which
is
great.
We
are
an
open
core
company
and
that
spiked
up
the
number
it's
a
good
behavior.
We
want
to
encourage
overall,
so
we
will
be
revisiting
how
how
this
metric
will
play
into
the
overall
in
the
future.
A
It's
it's
very
likely
that
this
would
be
not
a
kpi
and
it
will
be
deprecated
to
focus
on
age.
Instead.
Duration
went
up
slightly.
I
think
this
is
60,
plus
it's
above
60
minutes.
Now
we're
not
happy
about
that.
The
engineering
productivity
team
is
also
helping
out
with
gu
and
other
contribution
processes.
So
we
need
to
do
more
things
around
here.
A
A
new
metric
came
in,
which
is
mean
time
to
failure,
and
this
is
at
15
minutes.
This
is
the
first
failure
in
the
in
all
the
pipelines.
If
you
want
to
shorten
this
down
to
30
minutes,
tightening
that
feedback
loop
for
the
overall
team
and
review
app
success
rate
dips
slightly,
but
still
above
90
percent,
which
is
a
a
good
thing.
A
Okay
ron,
so
let's
dive
in
we
ended
the
month
of
march
at
18.5
million
mr
dollars
kudos
to
the
team.
We
have
great
progress
in
collaboration
across
the
board.
We
are
now
working
well
with
customer
success.
Sherrod.
Thank
you
very
much
for
your
invitation
to
involvement.
We
are
very,
very
proud
to
work
with
you
on
that.
We
added
daily
tracking
of
mrs
and
also
the
organizations
that
are
contributing
to
us
are
also
a
reminder
that
we're
not
going
to
vocalize
customers
on
this
call.
A
We
have
a
moral
week
in
review
now
and
ra
wins
in
slack.
Next
up
we're
going
to
continue
to
iterate
on
the
playbook
we
have
created
or
invented
this
four-step
playbook
that
that
gitlab
can
leverage
when,
when
you're
talking
to
the
customers,
we're
gonna
improve
on
recognition.
That's
like
there's
a
proposal
to
have
more
awards
quarterly
on
teams
that
have
merged
the
most
mars
and
the
tams
that
helped
us
enable
the
most
raw
arr
for
for
that
quarter,
and
the
last
thing
is
implementing
a
mr
coach
specialties.
A
I
I
truly
believe
that
we
have
coaches
assigned
to
specific
domains,
test,
automation,
technical
writing
and
and
and
other
things
we
will
get
more
involved
in
that
way,
because
there's
a
wide
bucket
and
having
having
specialties
and
socialization
helps
when,
when
you
want
to
increase
a
momentum
overall
bug
indicators,
so
I
told
you
before,
mttc
is
less
of
importance.
Now
we're
gonna
key
on
average
age
instead
and
the
goal
is
to
lower
the
average
age
of
open
bucks
overall.
So
a
low
level
of
shame.
A
This
would
be
a
really
high
number
high
number
of
days
into
the
multiple
hundreds,
but
we
will
continue
to
improve,
as
shown
by
the
the
spike
in
mtdc
s2.
You
can
see
that
even
though
the
the
the
number
of
buck
counts
for
s2
is
increasing,
the
average
age
is
still
stable,
which
is
a
an
acceptable
trend,
but
we
want
to
be
better
here.
A
Next
up
is,
as
I
told
before,
we're
going
to
make
average
age
a
kpi
instead,
while
mttc
is
going
to
going
to
go
away
and
then
we're
gonna
work
with
the
team
to
to
bring
this
down
and
continue
to
improve
the
severity
charge
overall
in
geometrics,
the
team
shipped
25
plus
iterations,
since
we
last
talked
very
proud
of
the
team,
major
polish
of
our
engineering
divisions,
kpis,
we
added
tracking
of
additions,
enhancement
and
maintenance
in
mars.
A
This
is
important
as
we
continue
to
work
on
existing
features,
making
them
better
and
balancing
that
with
the
new
features
coming
in,
we
deprecated
throughput,
it's
now
mr8
going
forward
and
the
specialization
the
data
classification
of
those
data.
We
also
add
a
percent
of
mrs
from
the
community
overall
lilly.
Thank
you
very
much
for
that.
Next,
up
we're
gonna.
We
have
a
new
metrics
engineering
engineering
landing
page.
We
can
improve
on
that
and
we're
gonna
simplify
the
the
mra
terminology.
A
A
We
now
have
a
weekly
merge
request
status
report
coming
out
every
week
and
it
shows
merge
requests
being
created
by
by
the
team
into
the
fork
and
also
the
main
repo.
The
end
goal
is
to
make
sure
that
the
merge
request
coming
into
our
main
repo
gets
reviewed
merged
in
a
timely
fashion
and
reduce
any
code
disks,
because
we
were
gonna,
we're
gonna
work
towards
enabling
code
sync
and
then
mirroring
a
constants
and
cadence
going
forward
shenzhen.
Thank
you
very
much.
A
You
helped
with
the
13.10
release,
that's
awesome
and
we
also
got
the
gu
team
to
work
on,
get
and
use
it
for
the
sas
deployment.
Thank
you
grant.
I
I
didn't
link
it
here.
If
you
click
on
the
issue
we
link
to
mrs,
I
believe
that
ali
cloud
support
is
now
in
get
we're
gonna
work
towards
bringing
that
into
the
main
repo.
Currently
it's
in
the
fork
and
also
tencent
cloud
support
is
coming
in
as
well,
so
very,
very
much
excited
about
that.
Next
up
is
we're.
A
Gonna
improve
the
security
testing
of
community
contributions.
Overall,
we're
getting
feedback
from
the
broader
maintainer
pool
on
on
the
code
structure
called
we're
dubbing
it
the
jh
edition
of
gitlab
and
then,
as
I
said
before,
we
want
to
use
the
same
folder
structure
for
all
the
other
projects.
We
start
with,
get
which
is
the
gitlab
environment
toolkit
and
that
will
mirror
the
same
code
structure
in
the
main
repo
as
well.
A
We
have
we
have
an
engineering
handbook
for
the
jh
team
linked
below
so
feel
free
to
take
a
look,
and,
lastly,
we
have
collaborations
across
the
board
within
the
department
we
are
looking
to
use
stan's
work,
which
is
the
the
gitlab
machine
learning
issue
charger.
We
are
at
70
percent,
accurate,
accurate
right
now
and
we
would
like
to
replace
our
manual
triage
in
in
the
department.
If
you
were
not
aware,
the
quality
department
team
members
are
the
ones
looking
at
new
issues
being
created
every
every
day.
A
We
want
to
reduce
that
manual
manual
work
there.
Secondly,
we
want
to
even
have
more
consolidation
of
tooling
we're
going
to
work
on
enabling
and
review
apps
for
all
mrs
and
have
smoke
tests
running
against
it
as
the
baseline
and
get
rid
of
the
legacy
package
and
qa
the
package
and
qa
job.
The
goal
here
is:
let's
reduce
fragmentation
of
tooling,
let's
put
on
people
put
it
on
one
infrastructure:
let's
just
pay
it
down
and
then
make
it
as
efficient
and
as
solid
as
possible.
A
I'm
very
excited
for
this,
because
this
also
helps
us
dock
food
home
shards
and
making
sure
that
review
apps
are
working
and
kubernetes
installs
are
working
off
the
gate
in
our
mrs
across
gitlab
we're
driving
corrective
actions.
We
have
now
a
label.
Thank
you,
tanya,
upgrading,
this
to
track
corrective
actions
from
quality,
going
forward
to
improve
ops
quality
working
group.
Thank
you
joanna
for
linking
the
slide
here,
I'll
I'll.
Let
the
audience
dive
through
on
the
backlog
is
developer
certification.
A
I
think
this
will
also
help
add
the
to
the
raw
momentum
and
then
the
demo
sample
data
efficiency,
that's
still
on
on
the
backlog
and
then
we'll
also
look
to
consolidate
that
as
well.
So
I
hope
that
this
preview
is
is
useful.
As
always,
the
agenda
is
the
source
of
truth
for
questions.
So
please
put
your
questions
there
ahead
of
time,
and
we
look
forward
to
seeing
you
in
the
group
conversation.