►
From YouTube: Secure & Protect 14.2 milestone planning
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
A
So
this
is
our
team
planning
issue,
and
this
is
where
we
try
to
capture
everything
that
we
expect
ux
to
be
working
on
for
14
2..
A
So
what
we'd
like
to
do
today
is
go
through
this
list,
make
sure
it
captures
everything
that
we're
expecting
that
we
all
understand
what
everything
means
and
that
we
can
assign
designers
to
anything
that
has
the
100
percent,
which
refers
to
a
need,
as
opposed
to
a
nice
to
have
so,
let's
start
off
with
composition.
Analysis.
A
Nicole
last
thing
you
mentioned
in
the
comment
below
I
think,
was
that
these
are
things
that
are
right
with
work
in
progress.
I
know
last
milestone
or
current
milestone.
I
guess
14
1
camellia
took
this
one
on
last
I
saw
it
was
experiencing
some
something
blocking
it.
B
We
have
a
design
that
was
never
verified
by
non-team
member
humanoids,
and
so
we
do
need
to
make
changes
to
put
the
data
somewhere,
but
how
much
data
and
what
data
you
know
we're
just
throwing
darts
at
the
wall,
so
I
got
cam
to
work
with
me
to
come
up
with
really
she
made
awesome
mocks
and
I
came
up
with
some
question
tweaks,
so
we're
gonna
basically
ask
people
what
data
is
it
actually
that
you
care
to
see,
and
then
this
way
we
have
a
target
for
mvc
of
you
know.
A
That's
the
research
issue
that
she
just
launched
this
morning.
I
think
she
said
okay
cool,
what's
happening
with
this.
B
One
so
until
dependency
path
is
done.
Okay,
we
can't
redo
the
maturity
scorecard,
but
my
hope
is
that
we
can
just
literally
take
the
exact
same
test.
We
did
before
if
dependency
path,
depending
how
much
it
changes
the
screen,
we
may
need
to
alter
one
of
the
images,
but
we
should
just
be
able
to
re-release
the
same
questions
again
with
a
new
image.
Once
dependency
path
finishes.
B
A
B
B
A
So
basically,
there's
there's
not
a
lot
needed
for
you
beyond
the
research.
That's
going
on
right
now,
yet,
okay,
cool
container
security
is,
I
should
probably
have
checked
to
see
who's
on
the
call.
A
A
I
should
also
point
out
that
in
lieu
of
the
org
change,
it's
supposed
to
be
100
effective
on
14
3,
that
we
need
to
consider
14
2
as
our
transitional
milestone,
where
anyone
that's
going
to
be
trading
places
with
anyone
else.
They
need
to
be
working
together
during
14.2
to
make
sure
everything's
caught
up
to
speed.
So
camellia
is
essentially
going
to
be
moving
over
here.
So
it
might
make
sense
that
this
is
sort
of
an
annabelle,
slash
camellia,
where
annabelle
you're,
the
dri,
but
camellia
is
paying
attention
and
watching
and
that
sort
of
thing.
A
So,
when
you're
thinking
about
how
much
weight
and
capacity
you
for
the
person
that's
collaborating
or
watching,
that
might
be
more
like
a
one
or
two
that
you
might
want
to
consider,
adding
on
or
subtracting.
I
should
say
from
your
overall
capacity,
so
we
can
probably
make
those
updates
afterwards,
but
I
just
want
everyone
to
be
cognizant
of
that,
while
we're
going
through
this.
A
A
D
Sorry,
the
cms
has
been
dragged
through
a
few
milestones.
If
it,
it
might
not
happen
next
milestone.
If
it
happens,
this
milestone
we're
just
waiting
on
the
testing
environment.
I've
been
meaning
to
reach
out
to
derek
on
that,
but
if
it
takes
longer,
then
I'm
guessing
it
will
be
purely
up
to
michael,
and
if
it
you
know
if
it
gets
pushed
again.
A
Okay,
so
maybe
maybe
we
could
spend
some
time
just
getting
him
up
to
speed
on
this
one
good.
There.
E
Yeah
we
could
move
forward
with
the
ci
cd
pipeline
scans.
Those
are
ready,
it's
really
just
the
validation
for
the
on-demand
scans.
That
is
not
completely
set
up
so
we'll
just
I
talked
to
seth
about
it.
It
just
hasn't
been
set
up
yet
they're
they're
low
capacity
right
now
in
engineering,
because
we
just
had
audio
move
off
to
verify.
D
Yeah
yeah,
it's
a
it's
a
complicated
setup
and
that's
unfortunate
because
I
feel
like
we
can't
do
the
cms
until
we
have
everything
I
don't
want
to
just
test
one
section
of
it,
so
I
think
it's
worth
waiting
until
it's
all
ready.
A
All
right
well,
in
the
meantime,
let's
at
least
get
michael
caught
up
in
case.
He
needs
to
take
it
over
entirely
forever.
C
A
We'll
probably
come
back
to
this,
depending
on
what
we
see
below
to
see
if
anyone
wants
to
put
their
name
on
it,
but
I
was
going
to
say
this
has
issue
coming
or
it
should
come
who's
gonna.
Be
writing
that.
E
So
I
think
that
I
wrote
up
the
issue.
I
told
michael
that
I
would
find
it
and
I
have
not
yet
so
I
either
need
to
write
a
new
one
or
find
that
issue.
I'm
pretty
sure
I
wrote
it
but
okay,
I
can't
find
now
cool.
A
Moving
on
fuzz,
let's
see
yeah,
we
got
two
needs
and
two
nice
to
haves.
E
E
A
Yeah,
I
think
that
makes
sense
for
the
next
planning,
which
would
be
for
14
3,
which
is
when
everything
is
supposed
to
essentially
merge.
So
I'll,
take
a
note
to
update
the
template
for
next
time,
good
call,
which
is
also
an
interesting
point,
because
technically
michael
will
also
be
taking
over
sast.
A
F
Yeah,
I
think
you
just
depend
on
your
research.
I
hope
I
can
finish
like
the
problem.
Validation
research,
this
milestone,
but
the
recruiting
doesn't
go
as
fast
as
expected,
so
the
research
might
sleep.
So
I
wouldn't
do
those
two
designs
at
all.
So
I'll
just
continue
with
the
research.
So
that's
not
possible.
F
A
F
E
A
Only
because,
in
a
way
it
help
if
we
know
that
so
each
of
these
columns
kind
of
feed
back
on
themselves,
so
we
can
be
able
to
prioritize
anyone
else's
needs.
So
if
this
turns
out
that
it's
not
going
to
be
ready
for
build
for
four
milestones,
then
it's
a
need,
but
it's
not
maybe
a
need
for
14
too.
You
know
that
kind
of
thing.
F
E
Like
yeah,
I
was
thinking
the
same
thing
that
it's
really
a
need
to
have
the
research
done
more
than
it
is
to
get
the
design
done.
We
need
to
know
what
users
want
and
then,
as
soon
as
the
research
is
done,
we
can
start
on
the
design
which
you'll
probably
take
a
milestone
or
two,
and
then
we
can.
E
By
that
point
we
might
be
ready
to
build.
I
don't
know.
G
A
So
I
think
we
still
need
to
add
the
mr
work,
because
it's
important
to
point
out
that
the
framework
for
the
mr
updates
should
be
done
relatively
soon,
which
means
the
expectation
is
on
us
to
take
that
framework.
Translate
it
translate
our
designs
to
utilize
it
or
our
widgets
to
utilize
it,
which
means
that
we
then
need
to
figure
out
a
plan
for
the
next
quarter,
which
will
be
the
build
phase,
and
I
my
understanding
is
that
there
will
be
product
and
engineering
okrs
that
will
support
the
construction
or
the
development
of
those
updates.
A
So
that
can't
happen
if
we're
not
at
least
planning
for
the
designs
to
take
place.
I
know
becca's
been
pretty
deep
on
this
working
with
pedro
and
his
team,
so
I
don't
think
it's
a
surprise,
but
I'll
just
make
sure
to
add
this
in
another
thing:
that
we
just
need
to
be
aware
of:
that's
something
that
will
take
up
time
for
designers.
A
That
is
pretty
much
everything.
Are
there
any
other
open
questions
about
any
issues
or
anything
that
anyone
else
talked
about.
B
I
mean,
I
think
we
need
to
start
figuring
out
now
what
we're
going
to
do
once.
It's
all
of
us,
pm's
rock
paper,
scissoring
it
out
for
what
gets
worked
on
next.
G
A
A
A
You
know-
and
maybe
derrick
will
come
back
and
say
well
we're
not
gonna
be
able
to
build
this
for
four
milestones
anyway.
So
that
means
to
me
it's
actually
a
lower
priority
to
get
it
designed
in
the
milestone,
we're
planning
and
then
maybe
sam
will
say,
yeah.
Well.
We
need
to
get
this
built
in
14-4.
A
I
also
wanted
to
do
a
retro
after
we
did
finish
this
planning
just
so
we
can
start
to
talk
about.
What's
working,
what's
not
working,
what
should
we?
What
can
we
maybe
change
and
make
it
better
that
sort
of
thing?
So,
ultimately,
I
guess
we
could
have
this
discussion
in
that
retro
plus
I'll.
Have
the
added
benefit
that
andy
will
be
back
in
17
days?
I
guess
so
he
can
help
too,
but
to
at
a
sort
of
general
level.
Does
that
help
at
all
nicole?
B
I
mean
maybe,
but
not
really,
because
like
right
now,
we're
planning
I've
been
trying
to
like.
If
you
look
at
mine,
I'm
talking
about
like
the
next
three
to
four
releases
and
I
sort
of
think
that's
where
we
need
to
be
going
because
yeah
my,
for
example,
spdx
export.
Let's
say
it
was
a
need
instead
of
something
I
could
pull
on
my
butt.
If
I
needed
that
in
14
4,
we
may
need
to
do
some
research
for
that,
for
example.
B
B
What
we
call
mr
approval
stuff
so
hopefully
I'll
be
able
to
start
borrowing
sooner
once
we
get
those
done,
but
I
think
just
being
able
to
look
slightly
further
out,
so
we
can
as
we're
discussing
them.
Like
you
said
sorry
table
cells,
you
know
just
being
able
to
say
well,
this
is,
you
know
not
a
priority
one
right
now,
but
maybe
we
should
make
sure
an
hour
or
two
of
putting
a
survey
together
happens
so
that
in
a
release
or
two,
we
have
the
data
to
make
decisions.
A
Yeah
my
my
thought
was
that
not
to
tell
you
how
to
do
your
job,
of
course,
but
ux
tries
to
get
at
least
we
like
to
say
we
want
to
be
at
least
two
milestones
ahead.
Really
it
should
be
three.
That's
really
difficult
for
a
lot
of
pm's
to
plan
that
far
out,
because
I
don't
think
I
think
I've
rarely
seen
that
happen
that
we
get
that
far
out.
A
But
if,
if
each
of
you
were
to
have
a
prioritized
backlog
that
went
as
far
out
as
you
possibly
could
that
might
help
that
conversation,
because
then
you
could
work
with
each
other
initially,
maybe
to
discuss
some
of
this
potential
overlap.
And
then,
when
you
get
with
the
designers
they
can
help.
You
determine
what
type
of
research
a
idea
might
need,
and
then
we
can
start
to
prioritize
those
and
get
them
in.
A
It's
really
squishy,
though
you
know
like
I
don't
know
how
to
solidify
that
stuff,
to
make
it
happen
like
technically.
The
way
that
I
wrote
up
this
process
is
that
the
first
two
weeks,
those
types
of
discussions
could
happen,
and
then
we
get
to
this
meeting
where
we
we
should
be
prepared
to
just
sort
of
walk
through
and
then
maybe
solidify.
Whatever
was
talked
about.
You
know
that
whole
really.
I
need
this
done.
A
This
is
a
higher
priority
one
than
your
priority,
one
that
kind
of
thing,
but
I
don't
I
don't
want
to
get
too
prescriptive.
I
guess
on
on
how
everyone
should
work,
but
that's
that
was
my
sort
of
general
thinking
with
these
first
two
weeks
of
milestone,
planning.
A
Yeah,
I
mean
that's,
that's
everyone's
complaint
right,
all
the
department
level,
other
git
labview
stuff
that
we
need
to
do
that.
We
forgot
about
that's
why
I'm
hoping
that
the
more
we
do
this,
the
more
being
aware
of
this
stuff.
You
know
we
added
this
table
being
aware
of
this
table.
I
really
hope
that
will
come
into
play
and
I
think
that
it
during
those
two
that
two
weeks
of
discussion
the
designers
will
hopefully
remember
these
types
of
things
that
we
have
them
working
on,
so
they
can
bring
it
up
during
your
all
discussions.
A
But
that's
the
thing
it's
a
lot
of
pulling
out
from.
What's
in
the
back
of
your
mind,
to
bring
it
up
in
the
discussion,
so
everyone
can
be
aware
of
it.
Maybe
it's
a
I
mean
we're
already
planning
a
month
ahead
for
the
future
milestone,
but
maybe
it
needs
to
start
sooner.
Maybe
the
last
week
of
a
milestone.
B
A
Just
you
don't
know
what
it
is
so
hold
it
back,
and
I
don't
know
what
else
to
do
after
that.
Except
you
know,
super
gumby
always
be
flexible,
but
you
know,
like
I
said,
I'm
going
to
create
a
retro
when
this
one's
done
and
we
can
continue
the
discussion
anything
else.
Anyone
wants
to
talk
about.
I
guess
technically
we're
at
time.
A
All
right
cool!
Well,
thank
you
all
for
coming.
I
apologize
for
the
meeting
thing.
I
was
hoping
to
give
us
a
little
more
time
if
we
needed
it,
but
it
turns
out
we
didn't
so
it
worked
out
in
the
end,
but
thanks
for
dealing
with
my
meeting
flip-flops
all
right,
everyone.
Thank
you.