►
From YouTube: Development Metrics Working Group 2019-07-11
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
B
Our
goal
overall
is
try
to
get
back
to
10
M
ours
per
author
reality
is:
is
that
with
our
current
growth
trends,
I
think
it's
gonna
be
really
difficult.
This
month
in
particular,
it
looks
really
positive
in
regards
to
we're
kind
of
trending
towards
that
middle
of
the
month.
Essentially,
if
you
look
at
our
month,
we're
basically
at
22
workdays,
it's
technically
23
weekdays,
but
it's
22
work
days
because
of
July
4th
holiday,
and
you
know,
obviously,
if
you
have
a
major
holiday
in
Europe
or
a
major
holiday
in
the
US
on
that.
B
B
Actually
good,
though,
if
we
had
about
five
at
the
middle
the
month,
it
turns
out
we've
projected
to
roughly
between
hi-hi,
eight
and
nine
and
ninth
is
kind
of
where
we
hit
so,
and
that
just
has
to
do
with
just
kind
of
like
at
the
beginning
in
a
month,
because
the
way
we
calculate
it,
we
don't
have
the
full
number
of
authors.
So
it's
not
like
a
true
growing
curve
from
that
perspective,
because
you
also
add
to
the
denominator
into
the
numerator
cool.
A
B
A
As
well,
I
I
do
have
some
comments
around
there
for
the
time
the
resource
well,
cuz
I,
don't
do
any
sheep
a
number
anytime
soon,
okay,
moving
on
to
throughputs,
it's
looking
really
great
at
the
get
out
there
hitting
strides
here
on
the
last
one,
pinky
635
totals
this
isn't
the
same
same
way.
That's
what
we
discussed
before
it
might
be
that
a
month
correct.
B
Yeah,
so
one
thing
that
we
definitely
want
to
see
is
that
continued
trend
of
your
hiring
twenty
five
percent
of
the
workforce.
You
want
to
see
that
continue
to
trend
of
throughput
going
up,
even
if
your
average
mr
spur
Arthur's,
is
staying
either
constant
or
maybe
going
down
a
little
bit.
You
still
want
to
see
that
really
net.
That
trend
continue
and
it
feels
like
in
that
regard,
we
really
have
done
a
pretty
good
job.
From
that
perspective,
our
goal
for
the
quarter
was
to
get
peak
to
peak
from
1800
to
2100.
B
I,
don't
know
if
we're
gonna
quite
attain
that,
but
this
month's
started
off
pretty
good
in
regards
to
effect,
this
is
the
log
raft
with
the,
including
the
community
contributions
we're
getting
close
to
we're
getting
close
to
900,
basically
for
the
second
half
of
the
month.
Essentially
the
way
to
think
of
this.
We
have
two
extra
business
days,
so
if
we
get
roughly
get
to
1900
and
then
we
roughly
get
200
in
those
last
two
days
of
the
month,
that's
100,
so
we
actually
would
actually
get
if
we
were
intending
from
that
perspective.
C
B
B
Good
morning
lights,
ooh,
yes,
we've
gotten
to
a
flatter
throughput
most
days.
It
seems
to
be
we're
getting
more
consistent.
Since
we
changed
to
the
release
model.
Two
months
ago,
our
Diane's
a
week.
The
weeks
have
changed.
It
used
to
be
that
you
know.
At
least
week
was
a
very
high
week
right,
yeah
mother,
we
saw
or
lower
it
seems
like.
Last
month
we
had
a
much
more
equalization
from
that
perspective,.
A
I
agree:
I've
seen
less
less
people
trying
to
merge
or
rush
things
in
to
the
last
day,
so
the
equilibria
here
is
it's
good
to
see.
Okay,
I'm
moving
on
to
time
to
resolve
bucks
that
I
see
their
numbers
as
stabilizing
or
maybe
training
up
I.
Don't
think
we
can
promise
giving
the
p95
up
e85
down
anytime
soon.
So
I
may
revise
the
exit
criteria
here
as
well
for
s
ones,
customers
there's
still
a
large
number
of
s
twos
and
it's
one
that
needs
to
be
prioritized
so
again
like
this.
A
C
Sure
about
updates
number
eight,
so
I
have
asked
for
I
found
where
the
merger
quest
size
is
in
the
database.
I
asked
for
it
to
be
added
to
the
periscope
export
and
it
looks
like
it's
scheduled
to
happen
this
week,
so
I
don't
actually
have
the
data
and
and
some
more
thoughts
to
the
issue
itself,
but
without
the
size.
I
can't
really
I
can't
finish
hypothesis
date
until
we
actually
have
the
size
you're
in
there
can't
graph
it
out.
C
Looking
at
nine,
so
I
gotta
look
at
the
wording
at
nine
again
developers
yeah,
so
I
took
a
copy
of
the
spreadsheet
that
we
had
and
tried
to
graph
it
out
and
I
can
actually
share
that.
Thank
you.
C
C
C
Comfortable
with
the
process
is
comfortable
at
the
code
comfortable
with
the
team,
and
we
did
see
that
trend
I
didn't
I.
There
was
no
number
that
I
could
extrapolate
from
that.
To
show
that
you
know
here's
the
rule
of
thumb,
but
the
majority
of
the
graph
lines
that
you'd
see
eventually
when
it
shows
up,
is
that
yeah
after
about
month,
two
there
was
a
steady
increase
of
number
of
that
Mars
per
month
per
engineer.
So
it
proved
out
I,
think
hypothesis,
nine
kind
of
proves
out
and
if
these
graphs
ever
show
up
so.
A
A
I
screen
yep,
so
this
is
essentially
the
throughputs
for
a
given
month
and
then
I
thought
it
out
the
ones
that
are
that
do
not
have
the
throughput
labels,
and
these
are
kind
of
like
your,
your
big
chunks
of
them
and
once
they
offenders
publicly
Eliza.
We
need
to
to
need
to
know
to
look
at
them.
I
think
yeah.
It
correlates
with
Christopher's
findings.
If
you
stand
up
there
with
these
tools,
I
give
live
EEOC,
you
still
still
have.
They
were
like
this
is
like
our
internal
tooling,
which
is
the
delivery
team.
A
If
it's
not
part
of
the
development
department,
so
I'm
not
sure
if
we
want
to
asks
them
to
start
labeling
things
or
maybe
you
want
to
remove
them
from
the
from
the
the
throughput
overall
I.
Don't
think!
That's
that's
the
that's
the
direction
here,
but
so
like.
If
these
are.
These
are
the
tail
selectivity,
it's
a
smaller
projects
that
Pune
and
some
hand-holding
very
they're
small
in
Mars.
So
it's
the
educators
like
yeah.
A
B
A
A
B
B
A
A
B
A
Let
me
let.
A
A
A
We're
gonna
tackle
that
afterwards,
but
in
the
immanent
work
to
unbuckle
teams
to
use
the
new
labels,
we're
just
gonna
go
ahead
and
do
a
straight
board
one-to-one
mapping
for
the
ones
that
have
a
single
a
label.
We
have
some
inference
tooling,
that
is
that's
gonna,
determine
the
feature
category
labels
and
then
they
could
correct
that
Bob
stage
play
ball
with
that's
gonna
deal
with
this
edge
cases
and
that's
gonna
come
afterwards.
A
B
A
B
B
A
A
Think
it's
relevant
to
this
room,
no
okay!
Next
one!
This
is
related
to
one
of
the
exit
criteria,
so
we're
not
getting
processed
progress
on
trying
some
of
the
customer
bugs
mainly
managed
I'm
gonna
start
involving
erick
rincon.
This
is
up
the
chain
in
devops
stage
death
and
I
I
think
maybe
Rickman
would
be
the
suitable
question
to
to
set
in
place
from
Jason.
B
A
Okay,
the
last
one
on
my
agenda.
This
the
time
to
resolve
would
not
be
getting
better
and
I
want
to
solicit
feedback
from
this
group.
How
we
want
to
work
the
exit
criteria,
I
think
it's
going
to
be
the
same
or
potentially
have
spikes
of
getting
worse
as
we
tackle
the
backlog
of
bugs
so
I'm
going
to
change
the
exit
code
here
to
to
stabilize
the
trend
instead.
I
feel
bad
about
this,
because
I
don't
have
a
number
per
se
to
call
out
but
yeah
any
feedback
from
the
group
I.
B
Think
that's
I
think
it's
fine,
if
we're
for
sure
to
track
it,
and
we
have
visibility
to
it
and
we're
talking
about
it.
Then
at
least
it
shows
that
aspect
of
it
I
think.
The
main
thing
that
we
have
to
kind
of
make
sure
is
that
it's
not
it's
it's.
If
it's
stabilized
then
were
we're,
basically
in
a
spot
where
we
can
keep
an
eye
on
it.
D
I'm
not
sure
if
the
time
to
resolve
is
a
valid
measure.
Until
we
get
all
of
the
stuff,
that's
already
missed,
SLO
done
and
gone.
It
feels
like
to
me.
Maybe
a
better
focus
would
be
reducing
those
numbers
that
are
passed
SLO
down
to
zero
and
then
at
that
point
we
already
have
the
things
in
place
to
measure
time
to
resolve
and
making
sure
that
that's
either
stable
or
reducing
I'm
curious
to
hear
your
thoughts
on
that.
B
D
A
A
good
call
I
could
say
that
it
would
be
very
long
to
do
it
now.
Innocence
allows
especially
the
P
threes,
I,
think
P,
1
and
P
twos
could
be
doable,
but
again
it
is.
We
can
encourage
and
talk
to
all
the
other
groups,
but
I,
don't
think
this.
This
Congress
wouldn't
go
pass
all
the
effective
levers
to
to
tell
down.
B
As
the
organization
is
currently
defined,
it's
out
of
scope,
that's
the
problem.
We're
wrestling
with
is
is
that
a
products
decision
prohibition
dictates
this
right.
If
you
said
well,
okay,
like
we
changed
that
philosophy,
then
then
this
would
then
it
would
be
a
nurse
cope.
But
that's
that's
not
that's!
In
our
own.
B
A
B
B
That
was
the
main
thing
more
that
we
had
I
know
was
less
on
the
on.
The
throughput
was
just
an
update
to
the
training
associated
with
that
I
need
to
review
it,
and
it
feels
like
the
next
three
weeks
is
original
time,
but
they
didn't
know
for
the
other
stuff
we
felt
like
we
had
a
good
good
closure
timeframe
associated
with
it.
B
A
It
was
two
weeks
ago
and
thanks
to
create
the
recordings
there.
This
gives
an
overview
and
a
chargeback
case,
massage
process
I
think
we
need
one
deep
dive
with
Pradhan
on
like
hey.
How
are
you
superiority,
how
it
affects
it's
time
to
resolve
Anissa
Lowe's
and
if
we
can
close
that
little
actually
one
more
recording
when
the
training
we
should.
C
C
It's
a
little
misleading
at
the
end,
there's
a
lot
of
flat
lines,
but
that's
because
the
the
data
cuts
off
at
325,
so
we're
missing
a
week's
worth
of
data,
so
I
believe
we
would
continue
to
see
more
upward
trend
lines
if
we
got
that
extra
week.
It
dated
but
I
think
this
kind
of
proves
the
hypothesis
number
nine
that
as
folks
get
more
comfortable,
they
will
certainly
continue
to
increase
their
productivity
and
submit
more
M
arms.
So
I
go
ahead.
Christopher.
B
C
Don't
know
to
be
honest
with
you,
I
didn't
I
could
probably
do
a
year
to
see
if
there
are
any
trains
to
folks
that
worked
over
a
year,
because
I
think
the
most
interesting
data
is
gonna,
be
coming
from
folks.
That
started
within
that
timeline
to
see
that
stabilization
I
think
if
we
get
a
snapshot
in
the
middle
of
when
something
I
like
between
year,
like
six
months
and
18
months
of
someone's
time
with
get
lab,
you're
not
gonna,
see
any
of
interesting
information,
so
I
could
change.
I
could
create
another
pivot.
B
If
we
can
get
like,
maybe
through
June,
because
I
think
I
think
you
know
like
since
basically
January
when
we've
since
we
started
the
new
fiscal
year,
we've
got
a
guess
technically
only
five
months,
but
will
they
were
coming
up
quickly
on
six
months
of
data
and
it'd
be
interesting
to
track
that
and
see?
If
we
see
it
like
it,
like
you
know,
is
it
three
months?
Is
it
six
months?
Is
it
nine
months
so
so
going
back
a
year
from
stay
tuned
to
June
would
be
valuable
information,
I.
Think,
okay,.
C
Okay
and
then
Christopher
and
I
talked
about
this
I
think
sometime
last
week
and
he
was
interested
to
see
same
trend
lines
for
when
the
Mr
was
actually
emerged,
and
here
it
is
and
again
same
same
problem
at
the
end.
There's
a
week's
worth
of
missing
data,
which
is
why
I
think
you
see
a
lot
of
the
trend
lines
go
down
over
the
last
month.
C
A
If
we
make
any
progress
on
the
the
cycle
time
at
all,
justice
data
tell
us
dating
asking
because
speed
up
the
test
pipelines
some
of
the
discussions
going
on
organically,
it's
about
remove
apps
and
how
we
have
a
lot
of
people
to
skip
it.
For
now
it
doesn't
affect
your
march
of
status,
but
improving
test
time
in
the
CI
builds
and
and
all
those
work
I
want
to
know.
A
C
B
A
B
B
A
A
B
A
Next
one,
it's
done,
this
I
would
like
to
remain
at
15
because
we
need
treatment
to
come
in
help
us
here
gather
time
to
resolve
as
well
as
to
since
it's
done.
Essentially,
this
is
the
one
we
discussed
earlier
of
average
time
to
resolve,
as
well
as
twos
I'm,
a
big
issue.
We
need
to
a
bit
of
threshold
and
expectations
and
we
need
a
product
stakeholder
back
in
this
meeting.
A
A
This
is
effectively
I'm
going
to
update
this
to
70%.
The
triage
package.
V2
is
going
to
be
rolling
out
sometime
next
week.
Updates
are
in
the
issue
itself,
so
we
are
listening.
Miss
miss
SLO,
zon,
typ
tools,
we're
enlisting
bugs
with
customers
and
feature
requests,
the
customers
and
also
the
heatmap,
so
I
actually
say
this
probably
80%.
A
That's
that
training
for
injury
matches
with
the
help
of
crave.
We
have
one
episode
already.
We
were
waiting
for
another
one,
so
empowering
this
50,
the
next
one
is
training
manuals
on
KP,
ads
and
interventions.
This
was
2%
before,
but
this
was
before
now
they're
linked
as
those
two
links
to
the
handbook.