►
From YouTube: Engineering Productivity OKR & KPI update 2022 06 06
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
kyle
here
with
the
engineering
productivity
team.
I
wanted
to
take
some
time
to
talk
through
our
okrs
and
key
performance
indicators
now
that
we're
entering
a
new
month
and
have
some
new
team
members
joining
so
we're
looking
at
here
is
ally
and
our
q2
okrs.
For
this
quarter.
We
have
three
objective
themes:
growing
the
team,
expanding
review,
controls
and
increased
awareness
of
team
work
and
then
increasing
engineering,
productivity,
team
efficiency,
the
one
and
three
the
improving
the
team
is
focused
on
the
team
growth.
So
we
have
two
team.
A
Two
new
team
members
joining
us
this
quarter,
as
well
as
some
training
and
and
say
like
and
people
ops
process
things
to
do
so.
I'm
gonna
go
through
and
talk
through
notable
updates
from
recent
weeks,
so
hiring
one
engine,
one
ep
team
member:
we've
hired
and
onboarded
the
team
member
who
accepted
an
offer
here
in
q2,
which
has
been
really
exciting.
A
We
have
a
team
member
who
started
last
week.
The
team
members
started
this
week
really
excited
for
them
to
join
the
team
and,
let's
start
contributing.
Next,
we
have
the
engineering
productivity,
mid-year,
talent
assessment.
This
is
a
pass
through
kr
from
the
department
and
what
that
means
is
our
results:
roll
up
to
overall
department
care
results.
A
What
this
is
so
this
actually
starts
wednesday.
The
mid-year
review
process
starts
wednesday
and
it's
team
member
led.
I
have
some
updates
on
that
in
our
weekly
team
meeting
last
week
and
I'm
gonna
be
talking
about
some
changes
from
last
week
to
this
week
in
this
week's
team
meeting
so
catch
that
for
more
information.
A
Hopefully
we'll
see
progress
on
this
in
the
coming
the
next
two
to
three
weeks
and
then
for
security
awareness
training.
We
have
all
the
team
members
in
engineering
productivity
completed
this
and
confirmed
last
week,
which
is
great.
It
is
important
from
a
compliance
perspective
for
us
to
keep
our
different
security
compliance
certifications.
So
it's
great
that
we're
supportive
of
that.
This
is
also
passed
through
kr,
all
right,
moving
into
expanding
review
controls
and
and
increasing
awareness
of
of
work
output.
A
We
have
expanding
the
required
code
owner
approvals,
high
impact
for
high
impact
areas
from
one
to
four,
so
we're
currently
a
two
and
we've
gone
back
and
forth
between
three
and
four
areas.
On
this,
throughout
the
quarter,
we're
going
to
settle
in
on
four,
where
we're
at
on
this
specific
kr
is
that
we
are
trying
to
make
sure
we
unify
the
visibility
of
review
requests,
because
right
now,
they're
in
between
the
mr
widget
and
reviewer
roulette,
which
has
back
end
and
front
end
and
database
suggestions.
A
We
want
to
make
sure
that
the
visibility
of
suggestions
in
the
that
are
required.
Mr
approvals,
are
also
in
reviewer
roulette
until
we
can
migrate
all
approvals
over
to
coder
rules
once
we
get
that
we
will
start
working
with
the
database
team
and
pipeline
engineering
for
them
to
identify
the
areas
of
high
impact
and
roll
out
code
owner
approvals
for
their
areas
as
well.
A
This
quarter.
Our
team
is
focused
on
adding
automation,
to
help
encourage
team
members
to
apply
this.
On.
Mrs
that
are
in
progress.
A
And
lastly,
one
of
the
things
we
want
to
do
this
quarter
within
the
team
is
create
regular
channels
for
engineering
feedback.
A
There's
an
issue
linked
in
this
kr
and
ally
and
we're
hoping
to
make
some
progress
in
the
later
half
of
this
month,
so
that
current
team
members
can
give
us
feedback
on
the
tools,
their
their
pain
points.
A
This
will
help
us
ensure
that
we
can
diagnose
technical
problems
quickly
within
the
team
that
fall
under
our
span
of
control,
as
well
as
equip
everyone
to
kind
of
be
comfortable
when,
when
problems
with
review
apps
or
with
pipeline
stability
or
specific
jobs
in
the
pipe
in
the
get
lab
rails
pipeline,
come
up
to
make
sure
everyone's
equipped
to
answer
those
questions
and
then
and
then
next
looking
to
update
the
team
handbook
content.
So
we
already
have
some
of
this
going
organically.
This
quarter.
A
Lastly,
updating
our
triage
operations
handbook
content
david-
has
started
on
on
a
proof
of
concept
to
add
documentation
to
our
code
so
that
we
can
start
to
leverage
that
to
build
our
to
build
the
page
that
we
often
refer
to
when
people
are
asking
about
different
automations
and
what
what
is
what
automations
do
we
have
within
triage
ops
and
how
often
do
they
run
and
all
of
that
we're
hoping
to
work
towards
a
more
programmatically
built
page
for
that.
A
So
for
now
we're
a
bit
behind,
but
I
still
think
we're
making
great
progress
on
that
considering
work.
That
is
not
reflected
in
the
in
the
kr's
here.
Lastly,
I
want
to
focus
in
on
a
few
kpis,
because
we
have
had
a
lot
of
attention
on
improving
kpis,
which
falls
outside
of
our
okr
work.
A
This
quarter,
one
of
the
main
things
that
we
focused
on
is
increasing
master
stability.
So
we've
had
a
few
issues
on
I'll
say
like
upstream
challenges
and
fleeky
tests
that
have
really
broadened
down
our
get
lab
rails
project
master
stability
rate
which
manifests
in
lower
productivity
for
the
overall
company,
because
when
master
is
failing,
all
mr
pipelines
are
failing,
because
we
use
merge,
results
pipelines
which
merge
that
mr
into
current
master,
so
any
failure,
that's
happening.
Current
master
will
be
reflected
in
every
pipeline
and
essentially
block
all
work.
A
So
what
we?
What
we're
looking
to
do
is
make
sure
we're
capturing.
What
we're
going
to
be
working
towards,
I
should
say,
is
capturing
the
data
in
a
more
timely
fashion,
on
what
tests
are
failing,
so
that
we
can
intercept
and
act
on
those
quicker.
Those
failures
quicker
as
well
as
start
to
use
some
automation,
automated
approaches
to
take
automated
to
take
action
on
flaky
specks
when
they
manifest
instead
of
having
it
be
a
manual
reactive
effort
like
it
is
today
next
review,
app
deployment.
Success
rate
has
also
gone
down.
A
A
Today,
you
see
we're
improving
in
june,
but
we've
had
a
number
of
up
similar
upstream
challenges
where
the
gitlab
charts
project
had
a
broken
master
that
affected
the
get
lab
rails
deployment
process,
and
then
there
was
some
bitnami
and
overall
infrastructure
issues
which
caused
problems
way
beyond
git
lab,
but
the
distribution
team
helped
provide
a
temporary
fix
and
where
we've
been
in
the
process
of
of
making
sure
that
review
apps
are
able
to
take
advantage
of
that
fix
then.
Lastly,
the
third
item
that
I
want
to
call
attention
to
is
our
pipeline
duration.
A
A
We
are
making
some
progress
in
june.
It
is
still
really
early
to
tell,
but
you
can
see
here,
we've
we've
increased
from
where
we
were
around
50.,
going
back
to
q4
q1
to
about
60..
A
lot
of
this
has
had
to
do
with
review
app
expansion,
but
there
are
also
I'll
say
there
are
also
our
spec
job
like
our
critical
path,
jobs,
which
is
primarily
our
testing.
A
A
Beyond
that
those
are
the
items
I
wanted
to
cover.
I
appreciated
everybody,
giving
us
a
watch
and
we'll
do
a
check
in
here
in
another
two
or
three
weeks.
Thanks.