►
From YouTube: Manage:Compliance 13.3 Planning 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
A
B
C
D
D
A
B
See
I
had
Mr
approval,
Settings
column
to
the
compliance
dashboard
yeah
that
wouldn't
was
work
in
progress,
but
I
think
this
I
think
Rob
said
he
had
low
to
medium
confidence
that
this
would
make
13
just
from
some
earlier.
I
guess
challenges
he
had
with
another
feature
so
I'm
expecting
this
one
to
slip,
but
I.
C
A
C
C
So
if
this
doesn't
get
completed,
then
the
mr
approval
settings
column
likely
won't
make
it
all.
B
Right,
okay,
yeah,
I,
think
I've
sort
of
accounted
for
that
in
the
future.
Block
and
I
may
just
push
that
feature
block
to
thirteen
three,
because
it's
such
a
minor
change
and
then
we
have
the
adding
merge
across
author
being
out
of
his
well
so
I
feel
like
we
should
just
talk
about
those
in
the
same
one.
C
Ideally
until
we
can
get
a
point
where
we
can
like
put
them
all
on
the
same
board,
I
don't
know,
perhaps
labels
will
come
to
save
the
day,
maybe
it
again,
but
because
it
cuz.
Obviously,
the
missing
part
of
that
are
not
moving
things
as
OE.
We
don't
know
exactly
without
mentally,
did
calculate
crunching
it
like.
How
are
we
matching
our
previous
velocity
or
not
and
then
to
be
fair?
That's
the
number
is
not
completely
final.
Yet
until
thirteen
to
draft
up
anyhow
there
we
can
look
at
historical
but
yeah.
Okay,.
B
Yeah
I
mean
that's
fine.
For
me,
let's
see
okay,
so
this
is
the
one
we
were
just
talking
about
projects
softly
yeah,
so
this
one
I
think
is
what
I
use
working
on
and
as
a
side
note,
this
is
one
of
the
first
changes
that
she's
gonna
make
to
that
confirmation.
Modal
separate
from
the
redesign
you
got:
okay,
I.
A
D
A
B
And
I
think
she
already
kind
of
gave
the
thumbs
up
on
the
related
feature
block
telling
me
she
had
confidence
in
that
one:
cool,
good
pack
of
requirements,
I,
don't
really
understand
what
this
issue
is.
I
know
it's
related
to
the
instance
level,
Amara
approval
rules
and
like
scoping
it
down.
I
think
but
I
mean
it
has
a
weight
of
five
and
I'm
not
really
clear
on
what
it
is.
It
looks
to
be
primarily
written
for
tan
to
track
on
the
back
end,
yeah.
D
D
A
B
That's
the
one
I'm
expecting
that's
when
I
thought
it
was,
but
the
issue
itself
has
just
written
because
I
think
Daniel
had
promoted
this
for
an
epic
at
some
point.
Okay,
because
like
this,
is
what
I
envisioned
when
I'm
thinking
about
that
feature.
As
far
as
like
the
issue
goes,
but
then
this
one
that
tan
seems
to
be
working
off
of
like
all
of
this
is
just
very
back-end
heavy
in
terms.
D
B
A
A
D
C
B
D
A
A
B
C
A
A
C
C
C
B
B
Yeah,
these
are
all
weights
of
one,
so
I
don't
know
if
we
necessarily
need
to
go
through
every
single
one,
specially
the
refactor
stuff
you're
talking
about
I
was
like
I
suppose
it's
jump
into
thirteen
three,
then,
if
that's
cool
rock
and
roll
yeah,
so
thirteen
three,
the
additional
expiration
job
I,
don't
think
is
gonna.
Take
much
time
at
all.
The
MVC
for
the
chain
of
custody
report
I
think
will
also
be
fairly
quick
work,
I'm
guessing
revoke
tokens.
B
The
AP
I
know
max
was
all
over
this,
as
well
as
the
related
one
to
list
tokens
via
API,
which
I
don't
think
that
one
has
a
mild
szeliga
mine,
because
I
don't
have
a
photographic
memory.
There's
there's
probably
like
three
to
five
issues
that
I
feel
like
we're
talking
about
committing
to
thirteen
three
and
we
just
haven't
yet.
That's
like
I'm,
expecting
maybe
three
to
five
to
show
up
on
here
after
today,
but
yeah,
because
we
still
have
tomorrow,
at
least
before
I'm
out
of
office.
I
sales.
B
This
today,
since
there's
no
meetings,
Fridays
and
then
I
suspect
that
we
could
maybe
squeeze
in
some
additional
work.
The
week
I'm
back,
even
though
we'll
have
already
concluded
planning
just
if
we
find
that
there's
some
straightforward
issues
that
don't
require
additional
refinement
and
given
my
being
out
next
week,
maybe
why
they'll
lag
behind
a
bit.
That's
on
Freddie
all.
C
These
three
to
five
issues
that
might
pop
up.
What's
the
easiest
way
to
find
these
because
I'll
admit
a
little
I'm
back
I'm
getting
cross-eyed
from
the
different
boards
and
the
next
step
is
Sheila's
is
awesome,
I,
don't
know
if
it's
part
of
that
it
seems
like
that's
four
thirteen,
four,
not
thirteen
three,
so
I
guess
I
would
look
at
the
thirteen
yeah.
My.
D
C
B
Those
I
know
I
think
these
two
were
pretty
straightforward.
I
think
there
was
some
back
and
forth
on
this,
so
this
was
just
basically
summarize
the
total
number
of
groups
and
projects
that
a
user
is
part
of
in
the
user
list
itself
and
I
think
max
and
Rob
we're
just
going
back
and
forth
to
agree
on
like
how
many
queries
per
user
it
was
going
to
take,
but
I
feel
like
that's
something
that
we
could
probably
refine
to
a
point
where
we're
ready
to
commit
to
estimation
in
the
next
couple
of
days.
So.
D
To
it
yeah
there
we
go.
Thank
you,
yeah
I
think
we
should
knock
out
what
it
was
like
if
you
actually
scroll
up
to
that
list.
Yeah
the
bullet
points
here,
I
wanted
to
get
down
to
at
least
making
a
language
more
consistent.
So
the
top
three
top
level
bullet
points,
and
then,
after
that
it
gets
more
optional.
D
D
D
A
D
B
D
D
D
D
Why
does
it
have
a
design
label
I
added
that
I?
Don't
know
why?
Because
it
was
two
weeks
ago.
I
can't
actually
remember
why
I
did
workflow
design,
but
it
might
just
be.
Oh,
you
know
what
I
think
it
was
just
because
I
wanted
to
get
sign-off
from
it
like
at
least
from
you
know,
like
you
too,
and
maybe
Mike
could
just
make
sure
it
sounds
good,
so
Mike's
signed
off
and
yeah
I
think
we're
actually
probably
good
to
go
on
this
yeah.
Okay,.
D
A
A
C
A
C
Yeah
close
ones
or
not,
he
can't
it
shouldn't
happen,
then
yeah,
so
the
first
one
is
deleted,
probably
not
get
deleted,
but
I
can't
move
that
to
the
first
item.
Cuz,
it's
hard
even
closed,
so
yeah,
okay.
As
far
as
what's
open.
It's
still
in
this
existing
order,
as
I
was
describing
the
description.
Okay,.
B
D
Yeah
I
I,
don't
know
that
we
actually
needed
design
for
that
I
think
whatever
Austin
designs
in
scarier
modal
should
work.
You
know
when
we
type
in
more
to
include
the
name
space,
so
yeah
I
know
he's
including
that
here
in
his
design,
which
is
great,
so
we
can
just
use
it
for
both,
but
we
won't
actually
add
that
name,
space
checking
functionality
until
that
other
issue.
Until
this
issue
yep.
D
C
Tentatively,
but
put
it
in
worklet,
workflow,
blocked,
okay
or
ordered,
throw
that
but
I
mean
I,
think
once
cuz
cuz
John
will
be
working
on
in
13
and
maybe
if
it
carries
over
there's
some
remaining
scope,
so
I
think
like
we
can
just
set.
If
it's
okay
with
you,
we
can
set
it
up
in
13,
3,
just
as
blocked
and
then
I'll
make
sure
the
dependencies
are
linked.
That's.
B
B
B
D
Looks
like
there's
a
chance.
We're
gonna
hit
all
five
of
the
things
that
we're
trying
to
hit
in
13
2,
and
then
we
kind
of
move
on
to
the
next
big
round
in
13
3,
there's
a
discovery
issue
that
I
need
to
write
about.
Can
we
consolidate
audit
events
into
normal
events
right,
which
is
yeah,
something
you
and
I
have
talked
about?
It
feels
like
we've
all
talked
about
that
I'm
gonna
finally
write
this
discovery
issues,
and
that
might
be
the
next
phase.
Ok,.
D
I
mean
I
think
we're
far
enough
out
of
you
know
like
we're
far
enough
through
the
technical
that
woods
that
we
can
probably
do
this
without
creating
a
mess
so
and
I
know
you
really
have
been
wanting
it.
So
let's
go
ahead
and
pop
it
into
13-3
and
see
what
we
can
get
done
there
and
you
know
what.
If
we
run
into
problems
and
it's
possible,
we
may
you
know
in
terms
of
like
technical
debt
or
whatever,
but
then
we
can
just
defer
it,
but
I
think
we
can
give
it
a
shot.
D
B
Just
conformation,
so
the
last
ever
calls
this
discussion
where
we
talked
about
it
was
basically
ready
and
then,
after
that,
we
felt
that
there
was
because
I
got
ended.
The
proof
of
concept
but
I,
don't
recalls
like
if
I
were
to
schedule,
is
four
thirteen
three.
Is
it
actually
good
to
proceed,
or
do
you
think
that
we
would
need
to
kind
of
circle
back
for
some
minor
refinement
based
on
the
work
that
y'all
have
done,
and
then
follow-up
questions?
D
C
C
D
And
the
other
thing
that
we
hadn't
figured
out
on
the
backend
side
was
you
know,
do
we
go
with
a
streaming
download
or
do
we
do?
You
know
some
sort
of
emailed
link
to
download
after
some
post-processing
I?
Think,
like
the
proof
of
concept
for
the
streaming
download
was
working,
you
know
we're
we're
like
80
or
90
percent.
Sure
that's
gonna
work,
so
I
think
we
can
move
forward.
Okay,.
B
B
B
B
The
P
twos
I
might
do
the
same
on
some
P
3s,
especially
as
we're
approaching
the
end
of
the
milestone,
because
I
suspect
some
of
those
might
be
good
candidates
where
they're,
already
kind
of
straightforward,
where
it's
basically
just
like
move
this
existing
setting
from
project
level
into
group
level
and
I
think
all
we
would
need
to
refine.
Is
you
know
if
it's
like
group
level
push
rules?
D
B
And
then
I
guess
tomorrow
or
whenever
y'all
have
time.
Just
let
me
know
if
there
is
kind
of
a
desired
amount
of
issues
that
we
should
try
to
fill
with.
I
mean
I'm,
just
gonna
keep
plugging
along
cuz.
It
feels
kind
of
like
to
me,
but
also
trying
to
keep
in
mind
the
balance
we
want
to
strike
for
refining
next
up
issues
as
well.
For.
C
B
D
C
B
C
I'm
talking
about
and
that's
why
I
was
about
to
say
I'm
confused
by
your
response
on
the
timeline
for
end
of
my
let's
tone,
or
something
like
that,
because
I'm
specifically
referring
to
cutoff
of
how
many
issues
were
putting
into
13-3
based
on
the
velocity,
we
can
be
able
to
deliver
the
last
three
months.
Gotcha.
A
A
B
I
think
what
I'll
do
is
I'll
just
spend
tomorrow
doing
what
I
said
and
then,
if
we
find
that
we're,
maybe
over
projected
velocity,
then
I'll
just
move
some
of
the
like
p3s
or
something
into
thirteen
four
because
I,
maybe
we
can
just
pull
them
in
last.
Second,
if
we
find
that
we
actually
have
capacity
for
it
and
then
I
guess
real,
quick
before
I,
let
y'all
go
and
overtime,
but
I
put
this
together
just
see
if
I
can.