►
From YouTube: Plan group weekly meeting 2019-07-24
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
B
Hey
my
name
is
Gabe
before
I.
Even
talk
to
you,
I'm
going
to
I
think
I
have
called
or
have
a
schedule
with
everybody
else.
If
I
haven't
and
I
miss
somebody,
please
let
me
know,
but
I
tried
to
be
diligent
about
doing
that.
I'm
excited
to
be
here,
I've
been
at
lab
for
I
guess.
This
is
my
seventh
business
day
so
second
week
in
ramping
up
on
plan,
I
appreciate
patience
and
graciousness
as
I
do
and
I'm
really
excited
to
be
here.
I'm.
A
Very
excited
to
have
you
yeah
I
was
actually
late,
because
I
was
interviewing
as
well,
but
I
currently
say
how
that
went
because
I've
just
gone
straight
from
this
mat
call
into
this
one.
Another
thing
the
this
just
a
name
change.
We
were
going
to
split
plan
group
into
a
sorry
con
stage
into
team
planning
and
price
planning
and
eventually
certify.
Now
it's
team
planning,
portfolio
management
and
certify.
A
We
want
all
wanna
start
using
the
group
labels,
which
should
already
be
being
applied
to
a
bunch
of
issues
once
the
new
engineering
manager
starts,
which
is
on
the
5th
of
August,
but
also
if
we
get
new
p.m.
starting
soon,
which
is
hopefully
hopefully
going
to
happen,
then
no
we'll
have
that
as
well,
because
we'll
have
Gabe
and
another
p.m.
and
they
don't
they'll
be
focusing
on
different
things.
Basically,
wow
I've
got
everything
on
the
agenda.
A
Okay
next
thing,
so
Eric
took
me
through
the
process
of
getting
a
Doc's
link
for
an
issue
for
the
release,
post
and
I,
wish
I'd
been
able
to
say
I
could
think
of
a
more
efficient
process
for
him,
but
I
couldn't
so.
This
is
this.
Is
what
happens
right
now,
so
when
we
create
the
release
post,
one
of
the
things
that's
a
sort
of
required
field
for
a
feature
that
we
highlight
is
a
link
to
the
documentation
where
we
describe
how
that
feature
works.
A
A
C
Well,
my
question
was:
basically:
how
do
we
actually
do
it
like
post
the
link
in
the
ticket
once
it's
actually
been
deployed?
Where
do
we
do
we
like
posts
in
the
chicken
the
issue
the
link
to
they
actually
made
requests
to
the
part
where
the
doc
doc
documentation
has
been
added
because,
like
I,
don't
know
that
there
is
a
delay
between
having
the
measure
pressed
closed,
the
time
when
this
actually
gets
public
or
on
production?
So
how.
C
A
Say
Alexandra
was
like
there
should
be
a
review
app
for
the
docs
a
lot
of
the
time,
and
you
can
take
that
link
and,
like
you
know,
obviously
replace
the
domain
with
like
dogs.
Don't
get
lab
calm
and
then
you'll
have
a
link
that
should
work
once
the
Doc's
are
deployed
is
another
way
you
could
do
it
and
I
think
even
having
the
link
to
the
docs
see
in
the
review
app
like,
if
that's
the
translation,
step,
I
think
that's
easier
for
a
PM
than
like.
A
D
The
thing
I
was
gonna,
say:
Alexandre
was
I,
think
I
care
a
lot
less
like.
If
you
threw
like
a
review
app
link
up
there,
I
mean
we
could
easily
replace
the
first
part
of
the
URL
to
get
the
you
know,
production
Doc's,
link,
I'll,
be
fine,
and
the
time
between
you
know,
NMR
is,
is
merged
and,
like
the
actual
deployed
state
of
it
like
I,
don't
really
care
and
I.
D
Don't
think
PM's
really
care,
because
we're
really
only
doing
this
at
the
kind
of
tail
end
of
a
release
or
right
before
the
release
actually
goes
public
and
you
know
for
the
release
post,
which
typically
most
of
that
work
happens
between
the
15th
and
the
21st
of
the
month.
So
the
short
amount
of
time
between
your
em
are
being
closed
in
it
not
being
deployed
I,
think
yeah.
Maybe
we
would
catch
one
or
two
of
those,
but
it's
not
gonna
be
a
big
deal
in
the
long
run.
It's.
C
D
C
A
I
think
one
thing
that
helps
there
is
that
the
idea
is
that
mr
issue,
sorry
now
how
this
work
Rovere,
ofin
step
where
you
verify
it
like
once
it's
deployed
on
staging.
So
if,
if
you're
going
back
to
the
issue
at
that
point,
close
it
anyway,
that's
also
sort
of
a
good
time
to
add
the
docs
link,
because
you're
you're
touching
the
issue
at
that
point
anyway,
like
I
said
so,
and
by
that
the
dog
should
be
deployed
so
I
think
that
might
solve
all
of
the
problems.
A
D
Where
you
know
we
were
removed
that
feature
flag
turned
on
the
feature,
player,
I,
guess
and
a
bunch
of
product
managers
who
have
the
canary
deployments,
enabled
kind
of
gave
us
a
bunch
of
feedback
and
I
think
it
was
like
super
valuable
feedback.
And
it's
just
one
of
those
things
that
like
if
we
would
have
maybe
taken
like
an
interactive
mock-up
or
something
I
got
into
the
into
the
product
team
meeting
like
two
months
ago.
D
B
This
guy
I'm
still
like
getting
up
speed
with
the
UX
process
and
wanting
to
integrate
in
with
that.
But
what
I've
done
before
I've
come
across
the
same
issue,
a
lot
of
times
like
wanting
to
get
feedback
sooner,
but
also
be
as
close
as
possible.
B
What
the
end
product
will
be
and
I
think
as
we
continue
to
refine
our
design
system
and
pajamas,
and
we
have
like
a
component
library
that
we
can
quickly
prototype
with
I,
have
been
pretty
successful
like
whipping
something
together,
pretty
quick
and
then
stubbing
out
data
and
and
using
that
is
like
the
starting
point
to
iterate
on
the
user
experience.
Because
then
you
can
take
that
with
you
into
like
your
final
build
in
production.
B
It's
not
like
a
piece
of
like
an
artifact,
that's
wasteful,
so
I
think
it's
trying
to
strike
the
balance
between
like
what
can
we
produce
that
isn't
wasteful,
that
we
can
then
iterate
on
into
the
real
like
product
and
I.
Think
a
lot
of
that
starts
with
the
design
system.
So,
like
I
I'm
glad
it's
there,
I
want
to
see
it
further
along,
but
I
think
we
might
have
to
figure
out
something
interim
until
it's
like
fully
ready
to
go.
F
With
rpms,
especially
I,
know,
I've
scheduled
calls
with
PMS
just
to
talk
about
like
just
validating
ideas
before
and
that's
been
a
great
help,
I'm
curious
how
we
could
just
get
people
to
jump
in
on
the
issue
and
contribute
their
and
design
also
has
weekly
reviews
that
we're
trying
to
ramp
up
attendance
there,
but
maybe
that's
something.
We
could
start
inviting
interested
PM's
into
those
or
at
least
sharing
those
to
maybe
the
product
channel
or
something
like
that.
But
in
this
particular
case
yeah
I
mean
I
think
even
just
like
lo-fi.
F
It
doesn't
really
have
to
even
be
an
expensive
prototype.
You
know
we
could
do
click
throughs,
there's
lots
of
options
there
to
just
you
know,
throw
that
up,
throw
that
together
really
quickly
and
understand
people's
expectations.
I
think
there
is
a
lot
yeah
that
we
could
do
there
I,
don't
think
it
really
has
to
be
any
kind
of
crazy
prototype
Eric
it.
You
know
we
could
think
about.
Maybe
the
level
of
fidelity
needed
for
different
things
before
showing
that
to
you
know
larger
group
yeah.
D
D
Please
read
that
this
is
something
that
Scott
has
introduced
and
asked
the
PM's
to
kind
of
collaborate
on
as
a
new
as
a
way
of
kind
of
making
sure
that
we're
building
the
right
things
and
that
those
things
are
adhering
to
a
broader
strategy
in
this
case,
like
I,
think
the
feedback
was
basically
like.
Hey,
don't
make
me
click
into
a
separate
tab,
so
that
I
can
see
my
like
my
list
of
related
issues
and
epics
and
I
think
like
that
feedback.
D
A
F
A
Are
there
any
issues
that
we
are
working
on
at
the
moment
where
we
should
look
at
this
new
product
development
flow
and
see
like
if
we
need
to
get
this
sort
of
thing
out
in
front
of
people,
because
one
of
the
great
things
about
working
on
this
stage
is
like
literally
every
piano
get
loud
uses
this
stage,
like
I,
think
every
person
that
get
live
uses
this
stage
like
which
we
can
get
feedback
really
easily
like?
If
you
want
to
find
someone
who
uses
this
stuff
so
yeah?
Is
there
anything
in
flight
at
the
moment?
D
See
the
one
that
comes
to
monitor
me
is
the
the
web
limits
and
I'm,
not
sure
Alexis.
If
you
were
thinking
about
that
one,
but
we
recently
closed
down
like
very
old
seee
issue
about
whip
limits
and
I
pointed
everyone
here
and
I.
Don't
know
if
you
saw
her.
There
was
a
comment
today
from
her
I'm,
not
sure
if
it's
a
customer
or
a
community
member
who
doesn't
pay
us
any
money.
D
I
really
have
no
idea,
but
he
made
a
comment
like
hey
I,
see
that
you
closed
my
CD
issue
in
favor
of
this
one
with
limits
is
a
very
mature
and
established
thing
and
you're
taking
a
new
approach
on
it
like.
Why
would
you
do
that?
Stop
reinventing
the
wheel
so
anyway,
this
whip
limits
can
be
a
good
one
to
to
throw
like
a
quick
prototype
in
front
of
a
bunch
of
users.
Yeah.
A
I
think
I
I
don't
know
if
they
are
a
customer.
I've
got
a
feeling.
They
are
a
customer,
but
I
know
that
they
are
definitely
a
sort
of
reasonably
prolific,
commenter
and
issue
creator
and
a
pretty
engaged
user
in
general
so
definitely
worth
getting
back
in
touch
with
them
and
talking
to
them
as
well
and
so
yeah.
A
Just
to
know
on
that
issue
as
well,
this
is
like
a
procedural
thing,
but
I
noticed
today
that
it
didn't
have
the
front
end
label
on
it,
but
obviously
a
neat
front-end
work,
so
I've
added
that
now,
but
that's
probably
like
changed
Donald's
capacity.
Calculations
for
this
release.
Cuz
just
drop
this
issue
in
there
yeah.
E
A
A
Think
I,
don't
know,
I,
think
my
mental
model
of
how
we
are
doing
stuff
is
hopefully
moving
towards
more
of
this,
like
Kanban
style,
like
you
know,
ranked
backlog
and
I
think
when
you
move
something
from
one
milestone
to
another,
it
can
sort
of
like
it
can
get
lost
and
it
means
that
you're
definitely
not
going
to
work
on
it
until
you
start
work
on
the
next
milestone,
whereas
I
think
it's
possible,
we
could
start
the
backend
work
on
it
because
we
already
had
planned
that.
So
that
might
change.
B
Dig
in
on
that
issue,
because
that's
one
thing
that
I
actually
talked
to
somebody
on
the
plan
team
a
couple
days
ago,
I
hadn't
seen
his
ticket
or
this
issue
yet,
but
why
we
didn't,
have
working
progress
limits
and
like
the
value
of
using
them
and
help
force
constraints
and
force
working
on
the
most
valuable
things.
So,
like
I
have
a
lot
of
experience
there
and
I'll
dig
in
and
see.
If,
there's
anything
I
can't
review,
it
looks
like
there's
a
ton
of
work
or
you
done,
which
is
awesome,
but
yeah
yeah.
D
There's
a
it's
been
this
I
think.
Actually,
though,
it's
it
is
something
that,
like
I,
think
Alexis
has
brought
a
ton
of
a
structure
to,
and
this
is
one
of
those
ones
where,
like
you
know,
we
asked
Eric
Johnson
like
what
do
you
wish?
You
could
dog
food
in
the
product
that
you
can't
dog
food
now
and
he
showed
us
like
this
poor
man's
whip
line
on
one
of
the
boards
that
he
uses
the
track.
D
The
problem,
which
I
think
is
is
like
Alexis's
point
throughout
that
common
thread,
so
that
there's
this
tension
and
I
think
it's
a
healthy
tension
between.
Do
we
iterate
and
make
something
better
or
do
we?
You
know
take
two
two
months
where
we
might
need
to
get
like
all
of
the
use
of
research
to
understand
like
the
right
way
to
solve
the
problem,
and
so,
like
I'm
aware
of
that
tension,
it
there's
a
little
bit
of
cognitive
dissonance
there.
It's
like
a
p.m.
D
to
like
move
quickly,
but
also
like
make
sure
you're
doing
the
right
thing,
but
in
this
case,
like
I,
think
that
we
maybe
should
align
a
little
bit
better
to
like
the
the
new
product
flow
and
game,
is
you're
coming
on
board.
There's,
probably
something
good
for
you
to
pair
up
with
Alexis
and
making
sure
that
we
have.
We
do
have
the
right
solution.
Yeah.
F
And
I
think
the
cool
thing
is,
you
know
with
this
new
flow?
It
won't
like
right
now.
It
feels
like
it's
taking
it's
a
bottleneck
right
because
it
is
right
because
it's
a
new
thing,
but
in
the
future
I'll
be
doing
this
ahead
of
the
team
and
y'all
won't
feel
this
tension,
and
hopefully,
by
the
time
we
get
to
y'all,
to
build,
will
already
have
this
all
researched
and
validated
and
it'll
all
be
happy
exactly.
D
I
just
got
goosebumps
thinking
about,
like
you
know,
two
months
from
now
what
it'll,
what
it'll
be
like
we're
gonna,
be
in
a
really
good
spot,
because
we're
gonna
have
a
bunch
of
validated
solutions,
pulled
off
the
shelf
to
go
to
going
into
the
minute.
It's
gonna
be
really
cool
so
anyway,
thanks
Alexis,
for
we
push
back
in
on
that
yeah.
B
B
Let
me,
but
also
to
have
an
engineer
chairman,
because,
as
we're
designing
these
things,
throwing
over
defense
like
engineering
to
say
like
here
here,
just
tell
us
how
long
this
is
gonna
build
and
go
build
it,
whereas,
like
if
they're
involved
earlier
in
the
process,
they
can
say
it'll
be
three
times
more
expensive
to
add
this
button
here.
The
way
you
want,
but
this
is
in
a
percent
solution
that
will
cost
like
a
fraction
of
that.
It's
just
like
I,
want
to
make
sure
as
we're
designing.
B
A
So
something
that
sort
of
ties
into
that
I-
don't
remember
if
I
mentioned
this
in
any
of
the
threads,
because
they
were
all
fairly
really
long
on
this
issue
and
the
related
issues
and
the
enforcement
is
a
little
bit
tricky
just
because
of
how
boards
work
like
a
board
can
represent
a
milestone
and
a
board
can
represent
sorry,
a
list
gonna
represent
a
milestone
list
can
represent
a
label.
A
list
can
represents
a
assignee,
it
can
be
scoped
like
if
we're
enforcing
it.
A
A
E
F
F
It's
in
the
way
issues
add
you
know
from
the
top
to
the
bottom
automatically
it's
it's
a
really
hard
thing
to
right
now
and
that's
kind
of
where
we
landed
and
that's
why
we
did
end
up
with
that
line
for
MBC,
just
because
it
isn't
in
her
own
words
as
bossy.
It's
a
little
more
flexible
and
a
little
bit
more
forgiving,
but
then
it
starts
getting
into
like.
Is
that
even
useful
from
with
limit?
You
know
standpoint
so
that
that
research
issue
is
a
little
crazy
if
y'all
want
to
look
at
it,
awesome.
E
Yes,
you
and
Alexis
should
definitely
get
engineering
involved
as
early
as
possible
in
the
issue
to
like,
throughout
the
ideation
phase,
so
yeah
whenever
you're
starting
to
think
through
that
stuff
ping,
myself
and
Jonathan
speaking
for
you,
but
me
and
Sean.
So
we
because
we
definitely
want
to
have
our.
We
would
definitely
want
to
provide
our
input
and
help
out
early
as
early
as
as
possible.
With
these
larger
issues,
awesome.
B
F
A
We
have
done
demos
in
the
past,
but
normally
on
specific
projects.
I
know
crew
shelled
a
lot
of
demos
for,
like
you,
know,
epic
stuff.
In
the
past
either
and
meetings
are
recorded
and
like
fun
things
I
think
it's
a
good
practice
to
get
into
is
just
them
know,
there's
a
lot
of
things
that
are
good
to
do
he's
just
picky,
like
which
ones
are
like
where
to
focus
our
time
and
stuff
like
that.
A
Anybody
got
anything
else
on
that
I
think
you
know
from
my
perspective,
it's
great
to
start
with
this
issue
and
like
think
about
that,
in
the
context
of
this
new
process,
but
obviously
like
we're
using
this
new
process
like
everywhere,
going
forward
like
as
we
as
we
were
all
on,
like
Eric,
said
like
two
months
down
the
line.
Hopefully
this
is
just
the
standard,
so
I
don't
want
us
to
treat
it
like
it.
It's
just
this
issue
for
now,
but
it's
not
going
to
be
just
this
issue
in
like
three
weeks
time
necessarily.
A
E
Have
you
all
been?
Are
you,
along
on
the
product
book
club,
on
inspired,
because
a
lot
of
these
concepts
come
from
that
and
if
you
all,
haven't
checked
out
that
book?
It's
it's
a
really
good,
read
I'll
link
to
it
in
the
agenda.
It's
called
inspired,
but
a
lot
of
the
ideas
around
that
is
around
early
experimentation
experiment
as
much
as
possible
or
early
on
prototype
things
out
it.
It's
good
read
how
how
far
you
all
on
that
Arabic.
D
Yeah
we're
talking
through
that
that
book
on
I
think
August
7th
is
when
it's
scheduled
and
so
I
guess
various
people
I'm
sure
there's
people
haven't
started,
it
I'm
sure.
There's
people
were
done
with
it
personally,
I'm
like
250
pages,
and
it's
like
a
350
page
book.
It's
actually
the
third
time
I've
gone
through
that
book,
though,
although
it's
the
first
time
I've
gone
through
the
second
version
and
I
think
the
second
version
is
just
much
much
better
in
terms
of
like
the
writing
structure
and
the
content.
D
It's
more
modern,
like
the
first
version,
came
out
in
2010
and
it
applied
to
kind
of
some
of
the
product
development
principles
that
were
prevalent
than
like.
You
know,
between
2003
and
2010,
and
this
one
is
much
more
modern
in
terms
of
some
of
the
things
he
brings
up,
but
yeah
you're
right,
like
he
highlights
a
lot
of
that
prototype
stuff
and-
and
you
know,
talks
about
it's
funny
because
he's
also
like
you
can't.
You
can't
just
take
everything
in
that
book
and
like
apply
it
because
he's
like
I
hate.
D
Remote
teams,
like
everyone,
should
be
co-located
because
they
perform
like
so
much
better
but
and
then
he
throws
that
like,
and
you
know
modern
solid.
You
know
well
well
how
performing
product
teams
are
doing
like
10
to
20
validations
like
a
week
in
terms
of
in
terms
of
product
and
I.
Don't
know,
there's
a
ton
of
good
nuggets
there.
Actually,
that's
a
really
good
segue
into
I
guess
an
open
invitation
to
the
team.
D
You
all
should
consider
coming
to
the
book
club,
it's
open
to
the
to
the
company,
Sean
I
know
you
had
the
issue
link,
Andy
I,
don't
know
if
you
could
drop
it
into
the
agenda
by
any
chance.
Yeah
well
do
and
then
the
book
club
is
August
7th
at
11:30
central
US
time
and
I.
Don't
it's
mommy's
Brits
way
it's
an
hour
after
the
company
call
so
hour
after
the
company
call
on
Wednesday
at
August,
7th.
D
And
I'm
happy
to
for
that,
to
anyone
who
wants
to
to
come
because
I
think
it
would
be
valuable
and-
and
you
know
harping
on
this
point
of
like
giving
engineering
involved,
the
product
team
is
is
like
a
trifecta
I
mean
it's
reiterated
throughout
the
book,
its
product
management
design
in
engineering.
So
you
are,
you
are
the
product
team
you're,
not
just
the
engineering
team
and
so
I
think
it's
just
important.
It's
a
semantic!
So
it's
important
to
rewrite
anyway.