►
From YouTube: Development Metrics Working Group 2019-08-01
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
So
Christopher-
and
we
talked
a
bit
about
hypothesis
eight
last
week
and
I-
think
there
was
a
correlation
to
the
hiring.
There
was
an
inflection
point
around
the
time
that
we
hit
the
peaks
of
the
average
and
Mars
per
author
per
month,
and
there
was
an
exponential
growth
and
hiring
during
that
time.
So
I
don't
think
we
didn't
come
to
a
conclusion
on
that.
One
I'm
probably
need
to
wait
for
Christopher
to
get
back
to
close
this
one
out,
but
I
think
that's.
B
Sorry
that
was
number
nine
I'm
going
backwards,
they're
developers
with
less
tenure
and
get
lever
still
learning
having
a
negative
impact
on
the
average
on
Mars
per
month.
And
what
we
saw
is
exponential
growth
in
hiring
on
the
between
the
periods
of
it
was
June
first
I'm,
sorry,
January,
1st
2018
through
June
of
2018
or
where
the
peaks
were
in
the
dashboard
graphs.
And
we
saw
that
that's
when
we
had
an
exponential
growth
in
hiring
as
well.
B
B
Think
sorry,
the
IPOP
this
is,
the
developers
come
in
new
developers
come
in
and
they
are
bringing
they
are
used
to
smaller
size,
M,
Mars
and
that
brings
down
and
that
impacts
the
average
mr
per
developer
per
month
and
I
did
not
see
a
correlation
of
that.
If
anything,
actually
the
size
of
the
M
R
gets
smaller
over
time,
based
on
data
that
pull
in.
So
we
couldn't
get
the
data
in
the
periscope
in
time.
B
So
I
ended
up
writing
a
quick
script
to
bring
it
in
and
there
is
a
changes,
count
size
that's
available
in
the
API.
So
for
every
M
R
that
is
submitted
and
closed.
You
can
count
the
number
of
files
that
are
affected
so
pulled
all
that
and
pulled
all
that
in
and
then
graphed
it
out
here.
So
you
can
see
for
someone
that
has
only
been
on
staff
for
a
month.
The
number
of
changes
and
the
files
that
were
affected
by
those
change.
B
What
we're
seeing
was
actually
the
size
of
the
EMR
decreases,
with
tenth
with
tenure,
so
I
think
that
is
that
odds
with
the
statement
of
the
hypothesis
that
developers
actually
come
in
and
the
newer
developers
with
less
tenure
submit
smaller
em
ours
compared
to
those
who
are
longer
tenured
and
more
productive.
We're
seeing
with
the
trends
is
the
actual
size
of
the
mrs
goes
down.
It's
the
longer.
The
person
has
been
with
the
company,
so
I
think
that
disproves
the
hypothesis
okay,
so.
A
A
A
Okay,
I
will
go
to
the
agenda
now,
just
a
follow
up.
We
no
longer
detect
miss
SLO
mp3s
and
we
also
remove
miss
s.
Ellos
on
p3,
so
spelt
is
to
have
a
clean
slate
as
PM's
going
and
we
boom
P
tools
and
P
trees,
again
Thank
You,
Remy
and
and
Kyle
for
this
Josh.
Any
comments
feedback
here.
I
think
we
are
for
that.
We're
done
in
terms
of
SLO
and
pressure
on
P
threes,
yeah.
C
C
There
would
be
less
pressure,
my
concern
there
is
that
then
the
prior
levels
lose
all
meaning
and
how
often
are
people
gonna
actually
set
a
due
date?
There's
my
concern
right,
cuz
I
would,
and
so,
unless
you
have
metrics
that
can
somehow
still
capture
like
how
long
these,
how
long
these
issues
are
open
for
I.
C
I'm,
not
I,
don't
think
make
sense,
because
then
no
one's
using
a
consistent.
What
a
priority
means.
So
then
it's
really
hard
to
actually
judge
anything
right.
As
far
as
how
buggy
stages
are
so
I'm,
just
gonna
try
and
push
nothing
to
to
have
to
regroup
and
have
the
priority.
Labels
largely
mean
that
it
should
get
addressed
within
the
time
frame,
rather
then
mostly
matching
up
to
like
this
severe
labels,
because
otherwise
you
end
up
with
like
a
whole
bunch
of
creatures.
C
Mp3's
I,
just
don't
make
any
sense,
and
then
we
can
use
this
very
labels
to
sort
of
just
see
how
we're
doing
as
far
as
overtime
as
far
as
how
severity
you
know:
humming,
yes,
yeah.
So
that's
what
I'm
pushing
forward
so
so
we're
still
working
through
getting
consensus
on
that.
But
thinking
getting
close
so
and
then
once
that's
done,
then,
then
we
will
hopefully
go
through
and
regroup.
A
I
know
Christopher
s,
answer
I
thought
using
due
dates
and
I
think
due
dates.
It
has
a
slim
low
emergency
and
security
is
using
it.
My
concern
with
you
date
is
that
it's
another
macadam
to
set,
and
it's
very
granular-
it's
like
the
exact
date
on
exact
week
on
the
calendar.
Yeah,
let's
see,
what's
to
read
on
the
consensus.
So
far,
do
you
think
it's
gonna
be
for
re
or
it's
gonna
be
due
dates?
I.
C
Mean
I
I
think
I'd
be
a
priority.
I
think
it's
actually
a
mutual
thing
between
engineering,
product
management
and
so
I
think
I'm
no
I
got
my
work
is
similar
to
years.
I
think
is
that
people
aren't
gonna
use
as
often
and
then
you
have
a
new
losing
income
and
definition
of
what
a
priority
means.
And
so
then
it's
just
like
some
arbitrary
label
that
people
just
put
on
stuff.
C
A
B
A
C
That
would
be
ideal,
I
think
they'd
be
the
one
thing.
That's
that
that's
missing
I
think
we
can
make
do
I,
like
the
other
chart
where
you
have
the
the
open
versus
closed
trend
like
on
the
same
chart,
but
that
I
think
that
if
I
did
pick
one
thing,
I'd
be
the
cumulative
that
way
you
look
at
a
picture
of
like
we
have
the
open
per
month
and
and
that's
helpful,
but
it
I
think
once
you
get
the
cue
it
really
starts
to
like
drive
home
like
what
the
actual
backlog
is
right.
C
B
C
C
A
C
C
A
Yeah,
let
me
dive
into
this
is
this
has
also
been
added
to
each
have
ups
and
groups
view
so
yeah,
so
this
chart
here
when
it
renders
it
should
show
that
if
it's,
if
it
doesn't,
it's
probably
a
file
that
we
need
to
look
into,
but
now
for
for
the
group
level
and
for
every
stage
we
now
have
deliverables
and
what
is
not
delivered
in
in
that
real
other
scope.
That's.
C
Awesome
I,
I,
think
I.
Think
one
thing
and
talk
with
the
PPM's
that
we
want
to
think
about
is
how
to
handle
like
things
that
are
consciously
added
to
the
release
like
midstream
and
not
just
like
yeah
they
weren't
playing
originally,
but
something
comes
up,
a
bug
or
whatever
it
is,
and
you
want
to
get
it
in
hot
it
like
do.
A
C
Thing
we
did
find
out
on
the
PM
call
on
Tuesday
was
that
there
is
no
standard
process
for
deliverables.
Some
teams
aren't
even
using
the
deliverable
label
apparently
and
some
folks,
the
pms
setting
at
some
folks.
The
iam
is
setting
it
so
and
actually
I
buy.
There
was
that
we
wanted
to
fine
the
process.
I'm.
Sorry
I'm
on
my
to-do
list
to
make
an
mr
to
try
and
like
have
a
common
flow
that
would
we
have
a
common
usage
of
these
labels
that
we're
using
from
metrics
I.
A
C
A
It
we'll
be
back
to
the
agenda,
then
next
up
so
we're
gonna
remove
deliverables
with
mouse
toe
and
we
heard
a
mouthful
is
plus
one
I
think
it's
not
still
on
track
to
be
merged
by
you
know
this
week
and
you
can
easily
spot
this
now,
because
there
are
some
issues
mark
as
deliverable
schedule
for
12.7
for
this
particular
stage,
and
you
can
use
this
to
essentially
spotlight
if
things
have
been
added
in
the
future
or
whatnot
when
that
change
goes
in.
If
you
don't
see
1204
and
none
beyond
that,
okay.
A
I
do
want
to
show
this
one.
This
is
probably
the
bugs
that
we
uncovered
thinking
was
a
month
ago,
and
we
just
so
go
back
to
it
now.
So
thanks
to
Remy,
this
is
a
comparison,
because
we
did
not
account
for
non
uniqueness.
It
was
only
unique
issues.
So
if
an
issue
has
mists
alumina,
8
and
also
miss
11.9,
it
only
renders
as
one
of
them,
which
is
the
earliest
one.
The
fix
that
Remy
made
now
renders
non-uniqueness.
A
A
Great
next
one
is
my
as
well
so
I
think
we
have
made
a
bunch
of
progress
this
past
few
weeks.
Tanja
is
being
transition
over
to
focus
on
self
math,
scalability
memory
and
also
performance
and
Kyle
and
Remy
will
be
the
main
stays
here.
I'm
still
hoping
the
team
close
this
working
group
out
soon,
it
looks
like
we
can.
A
A
Next,
one
up
fixing
the
author
calculation.
There
are
model,
not
cool
ways
to
do
this,
but
it
seems
like
the
data
from
bamboo
is
already
in
periscope.
I
know,
Christopher
and
Dragons
should
have
been
looking
at
this
data
as
well,
so
I'm
gonna
propose.
We
do
per
engineer
data
in
periscope
Josh.
Do
you
have
any
feedback
here
versus
doing
it
in
the
current
quality
dashboard,
it
seems,
like
all,
would
work
I.
C
C
Like
long
term
so
I
think
the
main
blocker
on
periscope
was
that
I
couldn't
do
Excel
exports
and
so
I'm
not
sure
if
that's
like
a
hard
stop
or
what
not
but
yeah
I,
think
I.
Think
from
the
PM
standpoint.
I
think.
Let
you
all
figure
out,
like
you
know
where
that,
where
the
best
place
to
put
to
put
these
charts
on
whether
to
continue
investing
in
the
cloud
or
dashboard
or
to
ship
things
in.
A
The
periscope
so
I
the
way
I
see
it.
The
quality
dashboard
is
gonna,
be
kind
of
the
legacy
production
data
into
the
next
quarters.
Until,
like
two
things
are
running
smoothly
right
thing,
we
will
Google
when
I'm
Bill,
periscope
I'm
gonna,
throw
it
out
Excel,
sorry
that
the
CSV
export
is
a
blocker.
Yes,
it's
not
there
yet,
but
data
at
a
high
level.
That
management
is
interested
in
to
just
be
in
periscope
and
I,
see
per
engineer
data
as
one
of
those
high
level
metric
like
we
don't
need.
A
C
I
agree:
I
mean
there's
some
value
having
an
all
in
place
so
that,
like
the
angel
teams,
didn't
see
that
but
I'm
not
sure
they're
that
worried
about
you
know
given
their
own
team's
trend
line
on
Mr
person.
Maybe
the
iam
is
but
yeah
I
think
I.
Think
as
most
this
is
an
all-state
Christopher
instead
thing
so
would
that
make
sense
a
parenthetical
first,
yes,.
A
I
think
the
total
per
the
total
number
per
group
makes
more
sense
because
we
don't
want
to
take
that
to
a
individual
performance
right.
So
I
think
looking
at
the
holistic
view
where
the
team
level
works,
but
then
periscope
and
KPIs
is
another
thing,
and
you
know
what
that's
in
definitely
outside
of
Krista
course.
Also
I
want
to
respect
that.
I
know
that
was
some
investigation
correct.
You
have
any
insights
on
how
the
calculation
is
going.
I
know
you
have
some
prototypes
and
such
maybe
like
to
share
or.
B
Yeah,
just
when
I
was
doing
the
research
on
the
average
M
ours
and
trying
to
figure
out
where
the
trend
lines
were
over
time
and
noticed
that
some
of
the
authors
were
not
in
the
team.
Why
now
and
they
ended
the
importing
team
yml
into
a
local
database,
so
that
I
can
focus
entirely
on
employees
and
then
narrow
it
down
to
titles
as
well.
B
So,
as
Joshua
said,
you
know,
I
don't
care
where
the
ultimate
destination
is
as
long
as
the
data
is
clean
right
and
we
can
do
that
overlap
easily,
so
that
I
didn't
I
had
to
manually
import
all
the
data
into
a
local
database
to
be
able
to
extract
the
data.
I
was
looking
for.
So
if
it's
all
in
in
periscope,
that's
fantastic,
I
won't
have
to
do
it
anymore.
Yep.
A
A
I
did
mark
this
one,
that's
done!
That's
the
diff
here.
Did
the
charge
package
version
two
as
they
roll
out
now
and
to
every
groups
we
should
be
seeing
he
pants
on
him,
etc.
On
my
part,
this
is
80.
Ie
I,
don't
think
we
had
a
venue
for
PMS
to
ask
us
questions
on
what
to
use
or
trash
package
to
use
or
whatnot,
but
I
think
we
could
do
another
due
to
recording
sometime
in
the
next
few
weeks.
A
Once
we
have
alignment
on
Friday
and
then
the
next
one
is
I,
don't
know
there
are
any
updates
on
training
for
EMS
on
kpi's.
This
was
50
before
so.
I
think
these
are
the
long
hauls
are
we
need
to
look
at.
This
is
done.
Oh
I
did
not
have.
It
is
my
apology
so
greater
weight
this
after
the
video,
so
I
think
we
are
really
close
to
done.
A
One
comment
here
and
I:
don't
think
we
can
lower
the
time
to
resolve,
as
well
as
tools
with
the
emphasis
on
on
P
labels
right,
so
I'm
gonna
propose
actually
to
to
remove
this
execute.
It's
it's
not
achievable
and
I
think
we
should
be
capturing
the
improvements
that
we
do
not
detect.
Miss
s,
allows
on
p32
anymore,
we're
doing
good
attitudes
and
going
for
will
be
emphasized,
I'm,
not
using
curry
labels.
C
A
A
A
Right
so
what
I
said
before
is
I'm
gonna
change
this
to
capture
what
we've
changed
on
SLO.
Is
we
emphasize
P
1
and
P
2
s
now
and
that's
in
a
good
state
which
is
good
and
we
are
gonna
emphasize
using
priorities
going
forward.
I
think
that's!
That's
good
enough
for
the
exit
right
here
and
it's
achievable
yeah.