►
From YouTube: Development Metrics Working Group 2019-07-18
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
we
have
completed
12
workdays.
The
report
runs
that
almost
12:00
UTC
it's
it's
a
little
bit
a
little
bit
easier
to
figure
out,
but
we've
gone
through
12
workday,
so
we
have
9
left
in
the
month.
So
we
technically
past
the
turn.
We're
trending
to
roughly
between
2000
and
2100
it'll,
be
interesting
to
see
the
second
half
of
the
months,
a
little
slower,
so
it
might
be,
you
know,
might
be
in
that
1900,
like
I'd,
put
my
ear
bars
between
1900
and
2100.
B
Essentially
at
this
point,
which
actually
would
be
a
you
know,
our
goal
is
to
basically
hit
2160,
so
you
might
not
hit
exactly
our
goal,
but
we're
trimming
pretty
positively
as
far
as
number
of
ours
that
restrictive
and
permits,
including
contrary
to
many
contributions
by
the
way
and
then
for
average
em
ours
per
author
at
the
turn.
We
were
at
a
little
bit
above
five.
The
one
aspect
is:
is
that
yesterday's
numbers
got
pulled,
I,
think
about
10:00
a.m.
B
there
was
some
really
significant
variance
yesterday
and
when
they
got
the
report
coupled
so
when
we've,
when
we've
hit
five
at
the
middle
of
the
month,
we
effectively
have
gone
to
around
nine
Amar's,
so
were
roughly
in
that.
That
range,
probably
not
gonna,
hit
ten,
but
but
it's
positively
trending
as
well.
B
This
is
hate
to
say,
I'm
lying
through
statistics,
because
that's
not
my
intent
here.
If
you
want
to
really
look
at
the
development
organization,
we
just
pull
what's
been
done
by
the
mrs
done
by
the
development
organization
divided
by
that.
So
it's
not
like,
like
that's
price
of
a
sure,
you're
looking
for
okay,
especially
becomes
as
what
its
development
organization.
B
And
then
he
looks
through
the
author
lists
and
then
based
on
that
so
like
as
an
example
Docs
as
an
author,
and
we
don't
necessarily
push
all
teams
to
push
at
the
same
rate
as
development,
but
that's
how
we're
using
it.
So,
in
fact,
in
fact,
in
theory,
if
I
really
want
to
push
development,
they
should
be
going
to
much
higher
rates
from
that
particular.
We.
B
C
C
B
B
A
So
I
want
to
go
on
record
that
this
requirement
was
the
original
requirement
and
I
know
has
been
honed
in
our
maturity.
I
think
we
need
to
slice
by
organizations
later,
but
we
don't
have
the
capacity
to
do
it
in
this
iteration.
So
that
would
be
something
in
periscope
where
you
have
better
map
being
with
engineers,
and
we
can
talk
about
it
later,
but
right
now.
This
is
the
best
metric
that
we
have
ya.
C
A
And
that
everybody
can
contribute
that's
how
yeah,
okay
with
that
I'll
move
on
to
the
next,
the
the
time
to
resolve
isn't
going
down,
as
we
know
that
we
have
a
long
tail
abuzz,
but
some
slight
uptick
in
actually
the
time
to
resolve
customer
clubs
of
s2
went
up
this
month
and
that
I
think
that's
something
we
need
to
call
out
here.
Jonathan
you're,
joining
this
working
group
and
I
think
we
should
discuss
more
in
the
agenda
on
what
are
the
next
steps.
We
made
some
progress.
We
have
some
data
thinking.
A
I
was
like
empowering
each
groups
mark
Fletcher's
working
hard
on
migrating
labels,
and
we
could
just
wish
to
group
and
say
gee
I
hope,
since
that
was
right.
Now
it's
we're
kinda
in
a
limbo
state
and
I
appreciate
allocations
and
mark
is
going
out
on
vacation
next
week
as
well.
So
it's
graciously
speeding
his
up
while
Rene
is
out.
I
want
to
give
him
kudos
for
that
as
well
with
that,
I
will
stop
sharing
my
screen
and
we
can
go
through
the
agenda.
B
I'm
up
but
I
was
trying
to
cut
and
paste
two
items
and
they're
just
too
quickly.
One
is
a
shout
out
to
Lucas.
Basically,
he
made
a
page
where
he
has
the
big
undefined,
which
is
a
way
for
managers
to
go,
look
at
their
area
and
see
who
are
the
people
who
are
currently
not
labeled
from
that
perspective,
so
I
think
that's
something
that
we
need
to
probably
think
about
is
if
there's
something
good
way
to
codify
it
in
some
fashion,
I
know
that
there
was
also
a
script
by.
B
Rachel,
but
this
this
looked
like
a
kind
of
a
convenient
way
for
us
kind
of
go,
look
at
so
like
maybe
you
and
I
can
talk
about
whether
we
there's
a
good
home
to
find
this
or
if
we
just
came
to
do
this
in
a
rag
tech
fashion,
or
you
know
like
what
we
think
is
right
a
way
to
think
about
this,
but
the
other
thing
is
is
with
our
new
labels
coming
up.
We
probably
make
more
that
just
so
that
you
know
it,
hopefully
is
a
easy
change
for
hims.
From
that
perspective,
we.
A
Have
new
automation
coming
and
that's
gonna
help
neck
folks
I
see
business
like
it's
a
clear
action
item,
so
I
I
do
like
it,
but
I
think
we
need
to
kind
of
hone
in
on
and
if
it's
gonna
be
a
temporary
thing,
when
we
get
everything
cleaned
up
and
then
going
forward,
it's
just
less
of
these
but
yeah
I
I
agree.
We
can
talk.
B
Later
yeah
I
think
I
think
the
challenge
I've
got
more.
Anything
else
is
like
I
like
the
report.
The
question
is
so
you
want
to
be
proactive
on
it.
You
know,
should
we
have
a
Status
page
around
it
and
the
answer
maybe,
is
that
when
you
both,
but
let's
talk
about
it,
offline
and
kind
of
figure
out
because
yeah,
if
it
feels
like
it,
feels
like
those
are
the
different
ways
you
could
potentially
attack
at
the
other
thing
is
at
the
end
of
the
month,
I
also
send
out.
D
B
A
One
thing
I
would
call
out
here
so
that
everybody
knows
I,
don't
think
every
groups
are
using
the
acing
retrospective
and
I
see
that
kind
of
evolving
being
like
the
official
structure.
But
you
have
managed
to
whatever
groups
and
they
have
they
don't
respect
us.
That's
kind
of
gonna
be
the
single
salute,
and
if
we
wanted
cool
mapping
up
engineers,
that
might
be
our
our
way
out
and
I
think
an
effective
one
as
well
cuz.
They
are
participating
every
every
year.
A
retrospective
okay.
B
B
Ours,
apparently,
is
not
up
to
snuff,
so
we
need
to
me
pull
you
and
Tanya
at
some
point,
maybe
to
either
give
them
advice
or
or
her
potentially
out,
though
they
I
think
they
had
that
issue
and
the
other
one
is
is
I
think
it
was
more
around
the
fact
that
they
have
basically
when
they
were
pulling
stuff
and
they
they
had
basically
done
treated
things
as
they
didn't
have.
Am
and
PM
so
been
treated
as
a
24
hour
daily
treated
as
everything
was
in
the
first
12
hours
of
the
day.
B
B
A
I'm
supportive
of
this,
because
I
know
our
execs
won
everything
in
one
place
and
keep
the
eyes
and
everything.
So
we
really
did
in
periscope.
One
thing
I
will
call
out
as
CSV
export.
It's
not
enter.
Periscope
and
I
did
some
ground
truth
there
that
basically
the
it's
not
there
and
we
need
to
construct
our
own
macadam
to
have
that
I
would
suggest
using
that
legacy.
Quality,
dashboard
for
CSV
export
and
and
finally,
to
reconcile
this
going
forward
that
we
missing
compare
scope
is.
A
A
Same
data
that
has
to
be
built
out
for
every
every
chart
needs
a
query
that
will
allow
us
to
explore
the
CSV
and
Absalom
fancy
filters
on
outside,
where
we
call
out.
If
something
is
missing,
a
throughput
label
there's
a
special
column
for
us
and
that
needs
to
be
parity
in
her
scope.
You
go
you
wanna,
Mike,
okay,
folks,
over
there
can.
A
Okay,
the
next
one
is
a
big
one,
kudos
to
mark.
We
are
dealing
with
two
cases
with
the
migration.
The
easy
one
is
sick,
the
one
to
one
where
there's
only
one,
because
the
team
label
create
the
other
cases,
there's
both
create
and
manage,
and
I
think
this.
This
will
affect,
mr
this
much
it's
probably
like
5%
or
less
for
merged.
Mr,
so
I
don't
see
that
as
an
issue,
so
we
move
move
forward
with
the
mapping.
A
A
B
C
So
team,
always
being
like
that
plan
play
plan,
Creed,
marriage,
okay,
verify
yeah,
I.
Think
people
were
using
this
in
some
cases
when,
like
one
team
was
built
like
there's
this
this
case
a
Gila
where
teams
are
empowered
to
go
fix
other
areas
that
they
need
and
so
I
think
yeah.
This
case,
were
you
know,
like
yeah,
the
secure
team
might
go
at
a
feature
and
plan,
and
it
gets
both
labels,
for
example,
because
both
like
plan
team
should
be
aware.
The
security
was
working
on
its
in
their
backlog,
so
they
it.
A
We
have
a
fixed,
you
see
you
scope,
labels
for
groups
and
it's
gonna
be
fixed
for
the
future.
This
is
me
letting
everybody
know
like
first
historical
data.
There
will
be
some
Mars
going
into
the
rock
group
and
I
think
we
should
be
okay
with
that.
If
not,
let
me
know
we
can't
go
by
author
as
well,
because
those
may
be
all
the
Mars
that
person
may
be
in
a
different
team
right
and
I
would
say.
A
D
B
A
B
A
B
A
B
A
B
Rather
than
the
other
way
around,
so
me
too,
but
let's
let's
go
ahead
and
go
with
it
and
we'll
see
if
it
comes
a
problem
like
if
I
start
hearing
a
number
of
folks
saying
you
know,
I,
don't
feel
like
I'm
getting
my
work
adequately
represented.
Then
that's,
that's
you
know,
that's
that's
a
problem
so.
B
A
Gonna,
so
if
you
would
watching
some
of
the
conversation
before,
please
don't
delete
the
labels,
we
delete
it
enablement
before
every
last
data.
In
so
we're
gonna
do
the
same
thing
we
need
for
platform
is
just
add:
a
duplicate,
prefix
left
work
at
him
and
then
in
another
six
months
everything
I
couldn't
done
good
to
beat
them,
but
by
now
we
need
them
for
reference.
Yep,
okay,
gotcha
and
I
saw
the
fact
that
my
fans
I
asked
I
was
gonna,
be
fine
but
yeah.
That's
that's
my
answer
today.
A
The
same
rate
I
see
a
sauce
backup
for
somebody's
two
customers
coming
in
current
plans
to
equipped
Yemen
PM's
with
more
tooling
more
data,
and
the
group
based
trash
package
is
coming
in
we're
bluffed
on
my
grading
labels.
So
my
labels
in
to
be
migrated
at
first
and
we
can
unleash
all
the
equipment
staged
fine-tuning
at
the
at
the
ground
fruits
level.
What
else
do
you
want
to
see?
A
C
So
I
will,
as
you
know,
one
thing
we're
doing
is
the
product
team
call.
We
asked
the
PMS
to
sort
of
go
back
and
look
at
their
individual
stages
and
groups
just
just
understand.
What's
going
on
there
I
think
you
know
each
each
stage
is
in
a
very
different
position.
Plan
manage
create,
are
very
different
than
secure.
C
You
know,
monitor
and
other
areas,
and
so
they're
very
different
problems,
so
I
wanted
to
try
and
have
them.
Take
a
look
understand
like
what
is
the
ground
truth
and
what's
the
problem
that
they're
facing
and
so
I
think
that'll
be
interesting
to
see
the
results
of
that.
The
other
thing
we're
going
to
do
is
that
we
don't
have
good
dashboards
or
all
of
the
data
I
think
that
we
need
for
the
stage
dashboards.
C
C
I
think
it'd
be
I
think
to
be
helpful
to
trying
to
understand
like
their
their
backlog,
I
guess
someone's
already
okay,
so
we
have
the
buzz
of
a
per
month,
which
is
the
bugs
created
per
month
right,
and
that
is
yeah.
So
that's
there
and
I'd
be
curious
about
the
bugs
clothes
but
I.
It's
there.
You
can't
like
do
the
math
yourself
a
little
bit,
which
is
fine.
A
C
C
A
C
So
I
think
it's
sort
of
is
that
right,
because
the
total
bugs
which
is
in
theory
I'd
like
based
on
my
priority,
it
should
is
their
best
the
Polish
could
have
per
month.
Well,
that's
not
cumulative,
though
so
that
yes,
so
that's
the
one.
That's
one
accumulative
I
think
I
think
that
may
also
be
an
important
one
to
know
something
if
I
had
to
pick
one
that
was
one
I
would
try
and
choose
that
way.
Pms
can
understand.
C
Like
what's
the
trend
line
here
are
we
you
know
falling
further
and
further
behind
or
are
we
trading
water
or
what
the
deal
is
and
I
think
another
ask
would
be
to
try
and
triage
p2,
p3
or
I
think
a
bit
of
a
lost
cause
right
now,
because
we
just
can't
even
get
our
hands
on
v2
s,
and
so
let's
try
and
let's
try
and
make
sure
those
are
groomed.
I
spot
checked
a
few
and
if
you
didn't
see
me
they're,
probably
p2
zai
actually
blow
them,
they
actually
removed
Pt
label
and
so.
C
We
did,
it
was
even
though
it
was
like
hey.
This
is
actually
a
p2,
it's
like
no,
actually
it's
not,
and
so
they
did
like
it
like.
One
of
them
was
an
intra
and
like
it,
hadn't
moved
for
like
six
months.
It's
like,
let's
really
get
P
it's
like
oops,
but
I,
think
the
other
thing
is
yeah
just
just
room
and
then
the
other
question
kind
of
a
think
later
on
is.
A
C
And
so
it's
sort
of
like
I've
two
concerns
I
fit
feels
wrong
to
be
transparent
company,
and
so
our
butter
just
open,
and
we
say
it's
a
p2,
we'll
try
and
deliver
it
some
90
days
and
we
just
it's
two
years
old
right
and
I.
Think
that
frustrates
people.
So
it's
like
what
the
heck
is
going
on
here
and
so
I
think
the
one
challenge
I
have.
Is
we
absolutely
go
back
and
read
R
in
them?
We
pushed
them
all.
C
A
We
talked
about
this
on
the
side
before
where
what
about
introducing
p5
and
p6,
with
like
a
six
month
and
a
year
like
so
like,
sounds
like
we
need
more
levels
here
right
and
the
areas
that
I'm
mature
like
create
plan
manage
they
should
they,
they
will
have
p5
p6
because
they
have
a
bigger
backlog,
but
I
got
a
new
team
like
that
comes
up
like
they
shouldn't
have
a
p5
and
p6
like
they
should
have
like
p2p
threes.
I.
A
C
B
B
In
a
defective
fourth
one,
which
is
no
current
plans,
you
know
for
this
activity
because,
if
we're
talking
about
anything
more
than
six
months
out,
like
you
know,
most
companies
are
going
to
say
you
know.
Who
knows
what
that's
gonna
happen
right
and
we
just
got
it
like
I,
don't
wanna
like
feel
like
that's
a
that's
a
better
story.
Yeah.
C
The
prioritization,
so
if
we
push
everything
to
p4
and
then
you
may
have
to
go
back
and
reread
remit
all
and
like
if
we
went
back
to
wiki
I
have
a
team
for
wiki.
Now,
let's
go
back
to
her
and
refigure
out
like
we're
all
the
different
like
partitions
of
the
bugs
are
like
I
think
the
es
labels
could
solve
could
still
serve
as
that
purpose.
And
so
maybe
that's
not
a
problem.
Yeah.
B
But
you
have
to
go
back
and
room
that
anyways
because,
like
you
know
anything,
that's
two
years
old,
the
first
thing
I'm
gonna
ask
is
you
know
the
first
thing
this
is
this
is
this?
Is
the
classic
whi
software
bugs
take
so
much
more
effort
to
fix
later
on,
which
is
versing?
You
gotta
go
figure
out.
Is
it
even
still
bug?
B
A
So
it
sounds
like
we
need
a
bucket
for
I'll,
take
a
look
later
and
it's
either
remove
the
priority
or
put
it
in
a
p4
and
then
just
move
those
bucket
and,
as
time
goes
through.
One
call
I
would
say
that
we
do
not
have
the
ability
to
filter
by
the
absence
of
a
label.
So
we
need
this
in
the
product
like
if
you
want
to
look
at
say
bugs
with
no
pee
labels,
there's
no
way
around
it
other
than
the
insights
dashboard
and
make
some
API
calls
no
I.
C
But
I
think
the
conversations
I
think
one
autumn
of
hoping
from
the
teams
is
that
some
of
them
will
be
like
we
need
to
play
more
or
how
they
prioritize,
bugs
all
right,
I
think
once
they're
once
they
can
present
information
and
ask
them
like
what
are
you
gonna
do
about
this
I
think
hope.
It's
an
outcome
and
they've
been
out
conversations
around,
resulting
velocity
of
features
afterwards,
I
think
another
good
currency
like.
Why
is
our
bug
trend
going
up
faster
than
our
merger?
Crests
are
like
test
coverage,
and
things
like
that.
C
Should
we
invest
more
in
automation
or
test
coverage
for
a
visual
teams?
I
got
hoping.
We
have
a
lot
of
some
of
those,
it's
an
idea
coming
back,
but,
unfortunately
the
drop
line.
Sorry
I
was
a
late.
Add
to
this
call,
so
I
have
a
commitment,
but
I
love.
They
keep
discussing
like
what
to
do
about
these
bugs
that
are
just
long-standing
and
might
not
make
it
addressed.
Okay,
how
do
we
HEA
trans
cleared
about
that
and
not
yeah?
So,
okay?
Well,
thanks
for
your
time,
Josh
yeah
thanks.
So.
D
When
I
worked
at
puppet,
we
actually
had
a
script
and
kind
of
a
guideline
that
we
had
for
issues
that
were
super
old
and
even
like
prompts
that
we
could
put
into
the
issues
that
were
community
contributions
that
you
know
may
not
be
reproducible
anymore,
maybe
on
an
older
version,
maybe
just
giving
them
guidelines.
Saying:
hey
we're
gonna
close
this
out,
because
we
don't
think
this
is
an
issue
anymore.
Please
reopen.
D
A
A
D
C
A
A
A
Think
I
added
this
in
regards
to
driving
and
using
priority
labels.
I'll
tackle,
is
Jeff
I,
think
we
need
product
and
also
maybe
Lao
as
well.
Is
there
anyone
interested
in
joining
me
for
a
recorded
discussion
I'm
talking
about
priority?
This
is
a
for
the
training.
Second
part
of
training.
Video,
ok
I'll,
set
this
up
for
next
week.
A
Okay,
last
one
fYI
I'm
people
involved
finance
on
there
ask
for
historical
data,
I'm
trying
I'm
trying
my
best
to
shoot.
This
is
working
group,
so
we're
not
distracted.
We
can
do
that
for
now
home
come
quality
thanks
to
our
attention
to
mark
one
ask
from
from
R
allies
for
future
cleanups
I
think
we
should
take
a
screenshot
before
the
magical
in
and
and
start
cleaning
up.
So
we
know
what
the
difference
is.
Christopher.
A
B
B
But
I'm
trying
to
think
how
to
say
this:
we
need
to
make
sure
they
understand
this,
isn't
scientific
/.
B
B
Okay,
I
can
almost
rather
push
back
and
say
we're
not
recording
that
at
this
point,
because
we
don't
view
it
as
important
and
then
you
know
tell
us
what
what
you
know
what's
what
from
a
financial
perspective
is
gonna
be
broken
and
it
was
asking
for,
but
I
would
love
to
understand
what
what
what
it
is
about,
the
our
labeling
habits
and
hygiene
that
they
need
to
understand.
Okay,.
A
A
B
It's
like
go
ahead,
be
severe.
Let's
plan
to
do
it.
Maybe
we
do
it
at
the
beginning
of
next
week's
meeting,
though
before
topics
just
make
sure,
because
a
week
to
cut
at
a
half
an
hour
that
I'll
make
sure
that
we're
focused
on
it,
because
we
want
to
try
to
clean
this
up
in
the
first
two
weeks
of
August
right
so
or
get
to
closure
on
the
first
two
weeks
of
August,
okay,.
A
D
I
showed
y'all
the
graph
last
week
slowly
because
they
loaded
I
linked
him
out
to
a
doc
to
make
it
easier
than
you
six
months,
Trent
the
six-month
grass
go
a
trend
of
growth
over
time,
which
is
good,
and
then
Christopher
asked
me
during
last
meeting
to
show
a
12-month
trend
to
see
if
there
was
like
a
plateau,
a
leveling
out
when
they
kind
of
stabilized
I
didn't
see
any
evidence
of
stabilization
had
just
gotten
Blacky.
The
further
out
you
went
so
I
mean
I.