►
From YouTube: Rob and Dennis discuss iteration in Manage:Compliance
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
So
I
guess
the
answer
to
that
one
is
that
we're
still
ongoing
with
it
like
the
order
event
stuff,
once
we
started
to
realize
that
we
should
be
iterating
on
it
and
we
I
wrote
out
all
the
issues
and
work
with
Shan
to
break
it
all
down
and
get
it,
and
then
we
obviously
got
some
of
it
into
the
next
release.
I
do
so
I
don't
have
an
example.
I,
don't
think.
We've
got
an
example
just
yet
of
a
completed,
successful
iteration
in
regards
to
how
is
this
being
helpful?
B
There's
been
a
lot
more
narrowing
in
terms
of
how
the
team
can
know
how
the
tea
can
focus
on
one
specific
aspects,
rather
than
trying
to
keep
the
whole
scope
in
their
heads
and
also
following
a
million
and
one
different
threads
within
one
massive
issue.
Okay,
it's
a
bit
complicated
and
we've
tried
to
break
these
issues
down
into
pieces
that
can
be
shipped
individually
without
needing.
B
They
may
need
a
proceeding
step
further
down
the
line
to
get
a
completed
but
II,
but
we
can
do
a
lot
of
things
in
parallel
without
needing
one
or
the
other
to
exist.
First,
which
means
that
it
can
be
deploys
if
we
don't
hit
it
it.
The
deployment
deadline
on
something
it
shouldn't
be
a
problem
with
the
rest
of
it
still
works
and
still
functions.
It
may
not
entirely
meet
the
users
needs
just
yet,
but
at
least
it's
not
completely
broken
yeah.
A
I
mean
definitely
in
my
training
at
the
definition
of
ABC
in
the
whole
kind
of
spirit
of
iteration
there's
not
to
ship
incomplete
features,
a
broken
features,
I
mean,
if
there's
honest,
we
continue
user
value
or
at
least
maintaining
it.
While
we
kind
of
get
towards
a
point
of
view,
so
I
know
for
filtering
out
of
events.
There's
a
lot
of
backstage
work.
Excuse
me
to
get
us
to
the
point
where
we
could
use
these
new
components
then,
like
that's,
that's
I,
think
those
are
good.
B
That
that
one
was
one
of
the
first
ones,
I
did
if
I
remember
correctly,
that
one
was
again
that
so
in
that
instance,
it
was
more
or
less
scope
creep
more
than
anything,
realizing
that
what
we
thought
initially
would
have
could
happen
turns
out.
That's
not
entirely
the
case,
so
there's
a
bit
quite
a
bit
more
to
do,
and
the
same
was
with
the
compliance
framework
stuff
as
well.
There's
a
lot
of
scope
creep,
I
feel
like
we
are
getting
a
lot
better.
B
B
The
one
thing
I've
found
that
quite
difficult
he's
trying
to
come
up
is
easy
enough
to
come
up
with
piecemeal
breaking
down
in
terms
of
the
technical
aspect,
especially
in
regards
to
what
can
we
do
to
maintain?
What's
already
there
and
not
ship
anything,
that's
completely
broken
unless
it's
behind
a
feature
flag
or
some
other
mechanism
to
say
this.
It
won't
be
available
I'm,
like
great
user
experience,
but
in
terms
of
coming
up
with
ways
of
breaking
things
down
in
a
way
that
improves
the
user
experience.
A
A
That's
that
we're
trying
to
deliver,
which
can
then
affect
how
we
break
things
out
from
a
technical
perspective,
but
I
think
we're
getting
in
a
good
habit
of
that,
especially
as
we
do
use
this
on
Dec
or
next
up,
whatever
that
label
will
be
to
just
kind
of
start,
having
discussions
beforehand
and
kind
of
discuss
these.
We
schedule
things
as
the
milestone
so
we're
getting
into
like
a
good
place
to
continue
to
do
better
at
this
practices.
A
B
A
A
So
it's
a
kind
of
a
context.
Break
versus
like
do
people
need
a
like
a
time
block
to
actually
go
and
just
spend
an
hour
you're,
just
digging
into
an
issue
and
doing
that
or
mix
and
then
hopefully
try
to
come
up
with
some
idea
of
okay.
Maybe
we
need
to
be
accounting
for,
like
5
or
10%
of
someone's
milestone
just
to
like
dedicate
towards
issue
refinement.
A
If
that
one
gets
us
better
in
terms
like
helps
better
build
the
habit
of
breaking
things
down
and
kind
of
seeing
possible
signals
for
scope
creep
things
at
that,
as
opposed
to
like
how
things
were
months
ago,
where
what
kind
of
us
going
mid
milestone
and
we're
not
able
to
notice
it
as
much
because
we're
kind
of
juggling
a
bit
too
much,
because
we
don't
we're
not
really
appropriating
time
effectively,
it
makes
sense.
Yeah.
B
I
feel
like
I
mean
firstly
in
terms
of
breaking
down
issues.
It's
some.
It
can
be
sometimes
quite
hard
from
a
front-end
point
of
view
to
think
about
how
we
might
do
something,
especially
for
me
not
having
a
design
and
bone
in
my
body
and
thinking
conceptually
about
how
is
this
going
to
fit
into
stuff?
Without
someone
telling
me
this
is
from
a
user
experience,
point
of
view,
but
a
good
way
that
we
could
implement
this,
followed
by
me,
going
right
from
a
technical
point
of
view.
This
would
work
this
wouldn't
work.
B
So
that's
been
a
bit
of
a
struggle
in
terms
of
time
management
I
feel,
like
you
know,
you've
got
the
old
adage
of
the
old
thing
that
happens
in
there.
Every
company
I've
worked
with
means
when
you
in
terms
of
defining,
what's
most
important,
you
know,
is
working
on
the
issues
within
your
current
milestone,
more
important
than
the
work
for
planning
the
next
one,
especially
if
you're
you
know,
you're
having
a
bit
of
trouble
trying
to
meet
all
the
demands
within
that
time
frame
for
one
reason
or
another.
B
So
there's
a
concept
of
making
sure
everyone's
so
clear
that
doing
the
the
the
the
next
what's
happening,
figuring
out,
what's
happening
for
the
next
Doc
Martin
is
as
important
as
that.
So
if
you're
not
able
to
complete
something
in
thirteen
point,
oh
because
you
need
to
do
some
planning
work
for
the
next
iteration,
then
that's
a
conversation
that
should
be
had
I
guess.
That's
then
round
two
math
as
to
which
one's
more
important
right.
Should
we
be
delaying?
Oh,
you
know.
B
Is
it
because
we've
put
too
much
in
this
milestone
in
the
first
place
or
you
know,
is
it
just
something
out?
The
blue
came
up
and
that's
why?
Obviously,
when
we
start
a
mask,
then
we
have
an
expectation
of
the
weight
that
we
think
we
should
be
able
to
get
through
and
things
happen.
Things
change,
obviously
for
some
things
and
then
there
were
some
better
but
yeah.
A
And
we're
out
of
time,
but
I
just
want
to
wrap,
wrap
things
up
a
little
bit,
but
I
I
mean
that's
something
that
can
be
adjusted
from
both
sides
right.
If
we
find
that
priorities
have
changed
or
scope
is
creeped
in
the
current
milestone,
and
then
we
can
see
and
have
that
conversation
of
how
to
remove
prioritize
everything.
A
Yeah.
So
to
me
in
terms
of
establishing
a
consistent
rhythm
and
that's
that's
the
first
part
and
then
to
ask:
how
can
we
iterate
even
better,
be
I?
Have
a
higher
throughput
I?
Think
it's
really
important
that
we
make
breakdown
work
as
important
as
the
future
work.
Otherwise,
I
don't
see
how
we
can
be
more
iterative
without
like
gaming,
the
system
in
terms
of
just
trying
to
over
optimize,
for
how
much
more
we
can
break
this
down
the
terms
in
terms
of
the
smallest
request
and
I.
B
Exactly
I,
just
like
you
know,
it's
a
it's
a
case
of
trend,
our
transparency
value,
making
people
absolutely
clear
that
you
know
let's
talk
about
this,
but
it's
not
something
to
be
ashamed
of.
If
you
can't
hit
these
lofty
goals
we've
set,
we
just
want
to
frank
and
honest
conversation
at
all
times.
Yep.