►
From YouTube: 2020.02.11 - Defend Staff Meeting
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).
B
The
way
to
one
minute
after
and
then
get
started,
the
motor
that
it
looks
like
things
already
set
to
record
so
I
may
be.
The
meeting
is
set
to
automatically
record.
You
see,
Philippe
nodding,
okay,
so
somebody
that
need
to
push
it
over
to
youtube
later:
okay,
cool.
You
know,
I'll
be
scribe
today
and
let's
see
here,
yep
Lindsay's
on
it's
dark
in
Oregon
you
can
save
it.
Lindsey
you've
got
the
floor.
D
Folks,
one
is
to
remind
everyone
that
it's
important,
that
you
know
Nate
your
peers
for
discretionary
bonuses.
That
means
the
most
coming
from
your
peers
and
we've
been
told
in
general
as
an
organization
we're
not
issuing
these
enough,
so
make
sure
you
recognize
people
for
going
above
and
beyond.
The
second
is
around
our
flight
planning
breakdown
meetings.
We
decided
to
make
them
weekly
for
now.
D
You
know,
if
you
need
to
add
you
explicitly
in
case
times
change,
and
that
being
said,
the
container
net
security
meeting
for
next
Monday
has
been
moved
due
to
the
holiday
there's
a
u.s.
holiday
for
Presidents
Day,
so
that'll
be
on
I,
think
Tuesday,
no
Philippe.
We
can
live
stream
to
YouTube.
There's
some
instructions,
I
have
not
done
it
yet.
Yeah.
D
D
E
E
B
With
the
great
planning
breakdown
meeting,
so
you
know
we're
just
getting
started
with
I
think
they're
going
really
well.
So
far
we
were
doing
a
lot
of
planning
breakdown
things
or
like
things
in
this
meeting
and
is
going
across.
The
two
different
teams
wasn't
as
efficient
so
now
that
we're
doing
that
I
think
we
can
move
this
meeting
to
every
other
week,
so
still
alternating
the
time
but
doing
every
every
other
week.
Any
objections,
any
alternate
ideas
thumbs
up
thumbs
down
CT
thumbs
up
some
more
thumbs
up
all
right.
A
So
some
of
the
top
of
mind
this
morning,
I
was
looking
through
the
handbook.
I
didn't
see
anything
specifically
about
how
we
should
move
a
defect
or
a
bug
into
a
milestone.
With
respect
to
the
workflow
labels.
I
know,
we
would
typically
put
it
into
planning
breakdown
first,
if
this
were
an
issue,
we
wanted
the
team
to
look
at
in
size,
I,
guess,
I,
don't
know
if
that's
appropriate
or
not
so
I've
been
sticking
scheduling.
All
them
wanted
to
hear
the
opinions
and
wisdoms
of
people
that
might
know
a
little
bit
better.
A
Think
would
probably
depend
on
the
bug
that's
kind
of
what
I
was
I
was
debating,
but
then
I
also
in
arguing
with
myself
over.
This
was
thinking.
Well,
if
it's
a
p1
s
one,
is
there
really
a
reason
to
do
that
or
wouldn't
it
just
move
straight
to
action
anyway,
regardless
of
sizing?
So
that's
I
was
kind
of
looking
for
some
guidance
on
how
this
was
normally
and
handled.
Didn't,
find
anything
in
the
handbook,
but
I
think.
D
It's
like
you,
said
from
p1
guys
we
wouldn't
even
want
to
wait
till
in
explaining
I
mean
clearly
we
adjust
the
scope
of
our
current
iteration
to
handle
something
that's
customer-facing
and
urgent
and
for
a
small
bug,
that's
like
maybe
UI
defect
or
something
obviously
right
now.
I
want
to
be
necessary,
but
if
its
large
there'd
be
no
reason
for
us
to
not
want
the
benefit
of
the
discussion
early
on
cool.
D
A
There's
the
one
that
I'm
thinking
of
in
particular
it's
hard
to
tell
whether
or
not
the
basically
if
the
back
end
is
already
there
and
we
just
haven't
wired
up
something
on
the
front
end
not
too
concerned
about
it.
In
this
case
it
may
be
a
more
fundamental
structural
change,
so
I
think
I
think
my
answer
is
gonna,
be
I'm.
Gonna
put
this
one
in
planning
breakdown
just
so
we
have
visibility
so.
D
E
D
Part
of
the
release
for
12-8.
Clearly
we
weren't
able
to
get
through
enough
all
of
the
issues
that
Matt
and
Sam
had
hoped
that
we
could
get
through
playing
break
down
prior
to
the
end
of
this
week.
So
there's
going
to
be
a
few
issues
in
the
upcoming
iteration
that
didn't
make
it
to
playing
break
so
they're
gonna
go
through
our
old-school.
D
You
know
individual
grooming
on
their
own,
so
Matt
this
defect
might
be
one
of
those
so
expect
that
over
the
course
of
the
next
few
days
we
might
be
assigning
some
issues
to
you
for
crew
mean
I,
know
that
the
time
is
getting
tighter.
I
mean
I.
Think
we're
supposed
to
start
execution
of
the
next
release
next
week.
Is
that
correct,
Matt
who's
been
with
you
Ben,
there's
quite
a
bit
in
the
last
few
days.
I
think.
A
D
Guess
the
point
is
this:
is
this?
Is
the
process
that
I
believe
is
going
to
help
us
we're
not
going
to
be
able
to
get
coverage
of
all
the
issues?
Are
gonna
be
working
it
up
coming
milestones
in
these
meetings
before
were
supposed
to
start
execution
of
the
medicine?
What
does
that
mean
that
we
can't
keep
talking
about
them?
D
But
the
idea
of
planning
break
down
is
to
make
sure
that
we've
answered
the
big
questions
and
that
we've
broken
things
into
smaller
pieces
and
that
we're
taking
smaller
deliverable
slices
of
technology,
a
smaller
component
size
deliverables,
which
obviously
you
want
to
do
perform
plan
start
before
the
iteration
starts,
so
we'll
get
there
we're
just
not
there
yet
sorry,
it
was
a
lot
of
words.
I.
B
C
To
see
you
alright,
I
think
just
like
one.
One
last
comment
on
the
workflow
labels
thing
now
that
I'm
waking
up
I,
don't
know
if
it's
a
problem
if
we
were
jumping
the
gun
to
scheduling
as
well
anyway,
if
it
seems
like
when
you
break
things
down
more,
we
can
just
shove
it
back
to
planning
breakdown,
but
I
just
want
to
make
sure
that
we're
not
being
like
extremely
rigid
with
our
new
planning
approach.
So
I,
don't
think
that
there's
like
I
agree
with
everything
that
we
just
said.
A
Although
Lucas,
you
brought
up
a
good
point
there,
I
guess
what
I
would
hope
would
not
happen
is
by
skipping
that
step
and
then
evaluating
it.
Realizing
something
was
like
a
five
in
terms
of
the
defect
fix
which
might,
in
the
case
of
something
like
a
p3
s3,
would
influence
whether
I
put
it
in
the
current
milestone
to
the
next
milestone
so
and
I
think
I've
kind
of
talked
myself
into
planning
breakdown,
as
at
least
a
place
for
engineering
to
get
first
eyes
on
it
and
say
yeah.
D
Okay,
so
it
is
a
dress
and
a
hamlet,
give
it
a
read,
I'd
like
to
try
it
for
something:
that's
maybe
a
planning
breakdown
meeting
or
something
that
feels
less
risky
like
we're,
not
gonna,
bring
up
a
team
recruiting
or
anything
like
that,
just
to
get
some
practice
with
it.
I
can
copy
chat
with
you
be
rather
sure.
E
That's
better,
there's
always
you
know
a
tab
that
you
ate
somewhere
of
the
oops.
Oh,
it's
like
one
I've
been
there.
So
that's
why
I'm
a
bit
concerned
about
live-streaming
one
when
we
do
this
kind
of
very
casual
meetings,
I
mean
if,
if
it's
the
CEO
one
on
one
and
one
one
not
seed,
you
know
is
really
trained
for
this
kind
of
exercise,
but
one
out
at
some
point
we
might
mention
some
candidate
or
some
customer,
and
that
would
be
today.
We
still
have
the
ability
to
remove
or.