►
From YouTube: Development Metrics Working Group 2019-08-15
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
We
likely
scale
it
down
soon
looks
like
a
lot
of
things
are
being
clear
now
to
the
rest
of
the
team
cool.
So
awesome,
it's
a
first
year
so
we'll
come
everybody
for
the
Deaf
metrics
working
group,
I,
believe
we
don't
have
a
p.m.
stakeholder
this
time
around,
but
they'll
follow
up
with
Josh
afterwards.
As
always,
I
will
start
with
sharing
my
screen
and
we
can
go
over
the
metrics.
A
C
Ten
business
days,
I
should
say
of
a
22
business
day
working
a
month.
So
what
I've
noticed
is
we're
a
little
bit
behind
what
I've
been
so
far.
Able
to
tribute
to
this,
too
is
is
it's
August
and
folks
are
taking
vacations,
so
we're
seeing
a
lot
more
people
out
for
a
week
or
in
two
weeks
in
a
lot
of
cases.
B
Would
add
actually
from
from
ops
what
we're
noticing,
where
we're
spending,
quite
a
bit
of
being
with
on
escalations
and
looking
at
debugging
infrastructure
and
incidents,
and
so
on
so
I
think
that
might
also
be
sons
leading
to
other
teams,
depending
on
their
level
of
involvement.
That's
a
new
thing
that
started
to
take
from
our
capacity
as
well.
B
Will
need
to
come
back
for
you
on
the
data
on
like
bug
fixes
specifically,
but
you
look
at
like
the
issue.
We,
you
had
tagged
some
folks
in
so
a
number
of
engineers
are
in
debugging,
it's
not
really
translating
into
code
changes,
but
a
lot
of
you
know
spending
hours
looking
at
code
and
trying
to
figure
out
where
the
issues
coming
from.
So
that's
a
bit
different
to
track
from
you
know,
em
ours
that
we
can
capture
in
throughput,
yeah.
C
It'd
be
curious
to
hear
about
the
other
escalations
that
one
was
a
fairly
straightforward
one,
relatively
speaking,
you
know
relative
to
any
folks.
You
know
three
people
should
statistically
it
all
statistically
affect
things,
obviously,
but
not
be
statistically
significant,
so
beakers
here
about
the
other
escalations
and
kind
of
understand
that
they're,
cool,
good
observation
and
what's.
A
The
next
one
mech
that's
right,
I
did
I
was
a
selecting
car
I
think
we
need
to
start
writing
things
down
what
we
talked
about.
So
it's
it's
there
for
the
folks
at
mister
meeting.
The
next
one
is
in
Mars
for
Arthur
and
I
know,
there's
some
discussions
later,
as
well
as
all
the
Chewie
Christopher
and
how
yeah.
C
So
this
is
kind
of
a
similar
story.
If
you
got
people
tickets
or
escalations
that
are
tilts,
London
Mr,
throughput
you're
gonna
see
an
add
drop
in
the
average.
This
is
the
other
problem
that
problem,
but
one
of
the
things
you
got
to
keep
really
keep
an
eye
on
from
an
average
respect.
Those
is
ideally
tomorrow
would
be
the
middle
of
our
month.
We'd
be
about
five
and
we're
tracking
behind
that
at
this
point,
based
on
that,
so
so
it
kind
of
meshes
with
the
other
one.
C
Now
the
one
aspect
that
is
interesting
years
for
doing
this
per
author-
and
we
got
a
decision
made
in
basically
the
PM
and
engineering
to
basically
recalibrate
on
this,
so
we're
gonna,
basically
go
to
looking
at
her
staff.
I
think
it's
gonna
be
staff
of
development,
plus
quality
plus
UX
and
p.m.
NPM
is
a
p.m.
as
well
okay,
so
it's
gonna,
it's
gonna
change
or
it's
gonna
change
or
our
goal
from
that
perspective.
So
we'll
have
to
figure
out
help
us
to
kind
of
measure
that
and
understand
that
okay.
A
And
I
just
got
an
issue
created
just
before
this
meeting
I'll
tag,
everybody
there
as
well
I'm
moving
on
to
the
next
chart.
No
big
updates
for
me
we're
still
monitoring
this
I
think
this
may
not
make
it
into
pearls.
Go
if
you
want
to
start
measuring
time
to
resolve
P,
P,
1
and
P
2,
because
that's
what
the
alignment
from
product
is
and
Josh
in
China
went
when
he
comes
back
next
week.
A
So
to
me
the
trend
is
getting
stable,
it's
not
increasing,
but
we
have
a
long
tail
that
we
need
to
improve
on
especially
a
response
yeah
with
that
I
will
go
back
to
the
agenda
and
I
think
we're
done
with
hypotheses
as
well
correct,
since
they
are
coded
awesome.
So
that's
right!
We're
not
done
8
is
still
open.
Oh
my
bad
Martha
working
on
okay
but
I
was
gonna.
C
Ask
if
we
should
keep
that
open.
It
seems
like
from
what
I'm
seeing
on
the
issue
there's
a
lot
of
work
that
would
need
to
take
place
to
get
the
emerge
sizes
in
there,
because
we
did
the
did
the
line
count
right,
but
then
there's
going
to
be
some
extra
work
to
get
the
size
of
the
differences
into
some
consumable
fashion,
and
do
we
want
to
invest
that
much
time
to
further
refine
on
this
hypothesis
or
not?
And
that's
probably,
a
Kristopher
call
yeah
the
way.
I
remember
this
was,
as
we
had
invalidated
the
hypothesis.
C
So
if
we
want
to
mark
it
red
and
then
we
want
to
say
that
if
we
want
to
change
that
and
that
hypothesis
at
some
later
date,
based
on
line
counts,
we
could
do
that.
I
think
we
should
probably
push
forward
and
open
an
issue
to
basically
request
that,
because
I
think
it's
still
valuable
information
but
I,
wouldn't
I,
wouldn't
hold
up
from
this
working
group.
For
that
investigation.
It's
more
just
normal
business
course
issue.
A
A
A
D
D
You
hear
me
now:
yes,
okay,
cool,
thank
you
and
yeah.
So
I
was
looking
for.
We
had
a
discrepancy
between
the
air,
Mars
merged,
Claremont
and
periscope
in
the
quality.
Dashboard
and
I
did
notice
that
it
pretty
evenly
matched
their
security
Emma's,
which
were
coming
from
death.
But
there
was
a
lot
of
security,
Emma's
and
I'm,
not
sure.
Well,
I
had
a
look
into
the
source
of
those
security,
murder
quests,
and
it
is
mostly
EE
dev
and
Cee
dev
and
couple
in
maybe
workhorse
I
think
it
was.
D
But
there
is
also
an
error
in
the
list
of
projects
for
periscope,
which
is
accounting
for
that
as
well.
So
there's
two
things
which
a
tribute
to
a
slight
discrepancy
there,
which
I
think
Christopher
asked
about
in
slack
a
while
ago,
and
one
of
them
being
the
security
moat,
requests
that
we
don't
import
a
periscope
and
the
other
being
a
slight
error
in
the
project
list
which
doesn't
match
up
with
the
quality
dashboard.
A
A
D
A
D
All
or
do
you
think
the
day
is
that
I
think
the
day
is
there
it's
just
the
the
query
does,
and
it
doesn't
add
that
that
month,
yeah
I
can't.
B
C
C
C
D
C
D
C
Because
if
both
of
those
changes
are
fairly
easy
to
make,
one
is
to
add
the
less
than
equal
and
then
the
other
one
is
to
basically
remove
the
contributor
line.
It's
just
what
I
don't
know
is
if
I
click
Save
that's
going
to
save
it
there,
but
if
somebody
over
writes
it,
so
maybe
maybe
this.
What
we
need
to
do
is
ask
the
data
team
just
to
confirm
that
you
know
if
we
do
it
on
that
page,
that's
sufficient!
In
our
perspective,
it.
A
C
Think
so,
I
think
the
one
question
that's
kind
of
outstanding.
In
my
mind,
it's
not
for
this
working
group,
but
probably
for
something
you
know
the
autonomic
is,
as
we
look
to
potentially
retire,
the
quality
dashboards
is
you
know
you
have
to
build
it
up
for
team
and
those
kinds
of
things
and
how?
How
do
we
best
work
to
address
that.
A
I
think
there,
if
this
to
approach
here,
there's
an
issue
already
from
Josh
to
replicate
everything
in
periscope
I.
Do
think
that
if
everything
goes
into
the
good
lab
org
project
right,
it's
it's
probably
easier
to
doubt
food
and
put
it
in
sites,
because
everything
is
in
one
one
place
so,
depending
on
what
the
level
of
visibility
you
want.
If
you
want
the
the
the
metric
to
be
at
the
exact
level,
then
it
should
be
in
periscope,
and
then
you
can
worry
about
double
work
at
the
it's
its
course.
A
You
do
double
work,
but
if
it's
ground
level
execution
approach,
team
I
would
like
to
try
to
dog
food
as
much
as
we
can
and
potentially
put
pressure
on
getting
CSV
export
in
the
product
itself
and
also
more
usable
issue
attract
of
future.
So
you
can
just
go
in
the
issue
tracker
itself
and
not
not
having
a
CSV
export
to
work
around
things,
so
that
would
be
my
take
on
it
happy
to
hear
your
your
feedback
or
I.
Think.
C
B
C
B
Do
you
have
a
sense
of
how
close
we
are
to
getting
this
in
the
product
because,
because
the
other
part
is
it,
what
we
get
was
with
insight
is
the
aggregation
of
all
these
projects.
So
when
we
look
at
a
team
contribution,
it's
it's
not
just
oversee
or
EE,
and
we
are
not
have
to
mentally
bring
it
all
together
and
that's
it
extremely
valuable,
so
I'd
like
before
we
leave
insight
I'd
like
to
see.
Where
can
we
get
that
data
in
whether
it's
in
our
product
or
in
periscope?
What.
A
If
we
can
can
help
me
add
more
color
to
this
as
well.
I
think,
there's
a
less
less
of
an
urgency
to
track
security
work
for
now,
and
we
want
folks
would
incentivize
them
to
move
into
get
level
or
so
having
mer
and
and
dates
for
marriages.
I.
Think
it's
like
end
of
August
we're
gonna
start
having
security
and
March
in
Keela
become
and
then
they're
gonna
retire
there
by
December.
A
The
reason
for
Deb
is
that
we
need
to
support
the
tale
of
three
back
ports
so,
like
the
project
is
there
but
I
think
we're
accelerating
on
getting
security
Amar's
inside
clapperboard?
So
when
that's
done,
you
could
potentially
use
the
native
insights
because
we're
working
on
features
to
exclude
and
exclude
projects.
So
it's
not
like
everything,
so
you
can
just
narrow
it
down
to
each
team's
edge
where
you
can
be
a
bit
more
selective
in
the
projects
that
you
have.
C
Just
wanted
a
thing
which
is:
we
are
trying
to
keep
it
down
to
anything
under
see
from
a
repo
perspective,
which
means
we
may
start
having
some
debates
about
that.
But
if
we
decide
to
expand
it
and
the
next
year,
let's
say,
for
instance,
but
I
think
that
a
key
aspect
here
is:
is
the
theory
Isis
that's
going
to
drive
us
more
to
put
stuff
in
the
product
as
opposed
to
have
software
work
outside
of
it.
C
B
But
more
of
my
concern
is,
if
you
look
at
insight
and
look
at
the
number
of
projects
that
we're
tracking
it
it's
not
just
and
see,
and
and
it
depends
on
which
repos
each
team
is-
might
be
contributing
to
that's
more
of
I'd
like
to
make
sure
that
we
are
encompassing
the
full
capacity
of
the
team
and
not
only
looking
at
seee
and
engaging
that,
because
the
conversation
may
be
different
from
team
to
team.
Depending
on
what
other
repos
they
contribute
to
which.
C
A
Can
you
folks
hear
me
uh-huh?
Okay,
my
assumed
is
frozen,
I'm
not
going
to
touch
anything
here.
The
lists
right
now
it's
on
parity
with
whatever
is
in
periscope.
So
you
look
at
the
list.
That's
in
the
next
point
below
where
we
highlighted
the
bug
in
the
import
that
should
be
100%,
things
that
are
in
depth.
So
the
list
is
there.
I
I
think
I
I
channel
a
Christopher
here
where
I
think
we
need
to
focus
on
the
customer
facing
numbers
right
so
like
the
new
way
of
accounting,
we
can
discuss
in
detail
below.
A
A
D
A
D
A
Awesome
thanks
for
taking
us
on
next
one
is
the
short
one,
so
the
legacy
team
levels
are
being
deprecated
next
week
things
my
team
and
I
are
gonna,
take
on
lava
communication,
but
if
you
have,
if
you
have
extra
time,
please
you
ready
to
array
that
again,
I
think
we're
gonna
add
duplicating
all
the
team,
because
he
team
labels
now
and
then
next
week
we
should
be
full
on
the
new
labels
permanently.
A
I
have
the
next
one
as
well
so
I
think
we
should
aim
to
close
out
this
working
group
next
week.
If
we
can
any
any
thoughts,
everybody
else
so
anything
else
that
we
need
to
make
sure
we
close
out
before
we,
the
disband
this
group
and
I've
listed
a
few
here
outstanding
ones.
So
I'll
pause
there
for
discussions.
A
A
C
A
C
A
C
C
A
It:
okay,
that's
a--that's,
a
good,
been
a
chisel
cut
as
well.
A
And
I
have
a
few
others.
Do
we
want
to
discuss
any
of
the
accounting
method
data?
You
have
any
questions
like,
please
repeat
it,
to
click
on
the
Lincoln
and
look:
that's
the
new
proposed
way
of
counting
things.
I
don't
want
to
I
want
to
be
sensitive
to
on
how
we've
come
here
before
and
make
sure
that
we
capture
and
address
the
needs
and
concerns
as
well
moving
forward.
A
A
Okay,
moving
on
to
the
the
periscope
import
part,
so
this
is
going
to
be
tackled
by
by
by
mark
it's
a
summary
report
on
customer
bucks
clothes
out
to
a
week
that
supports
like
it
would
like
to
see.
So
this
is
a
another
ongoing
together
will
close
out
after
closing,
either
working
group
and
detecting,
send
SMS
of
links
and
add
a
customer
label
is
my
improvements
we
trying
to
dog
food
Stovall
is
here:
that's
why
it's
taking
a
long
time
and
is
there
anything
else
that
I'm
haven't
captured
here
for
future
action
items.
C
A
One
could
be
closed
out,
I
think,
and
we
have
to
YouTube
recordings
already
and
we
have
been
with
the
help
and
judge
being
engaged.
I
have
another
action
from
the
product
meeting
last
week.
To
put
a
few
more
guidelines
on
like
severity
should
not
change.
The
party
can
change
and
all
that's
all
those
guidelines.
I
think
that
that
should
be
enough
to
close
this
out
by
by
next
week,
so
yeah.
We
can
consider
this
almost
done.
Connect.
C
Cool
and
then
training
for
engineering
managers
on
KPIs,
so
I
went
back
and
looked
at
the
pre-existing
video
which
Dahlia
and
Eric
great
Thank,
You,
Dalia
and
I
think
that's
sufficient
for
now,
mainly
because
if
we
created
trade
to
create
a
video
right
now,
we'd
be
in
this
transition
between
periscope
and
the
product.
That
feels
like.
C
A
B
A
I
will
open
an
mr
after
this
meeting.
I
assume
is
totally
bonkers
right
now,
by
the
way
I'm
flying
flight
flying
blind
I
cannot
see
his
facial
expressions
so
I'm
being
extra
sensitive
here
to
feedback,
so
I'll
open,
NMR
and
add
an
issue
that
Christopher's
active
support
at
the
KPIs
and
I
will
tag
everybody
on
issue,
one
three:
four:
that
is
the
main
way
of
doing
accounting
going
forward,
and
if
you
have
any
comments,
please
put
it
in
there
and
we
will
do
pre-planning
before
moving
into
the
quality
project.