►
From YouTube: Verify CI - UX/PM Grooming meeting 2019-12-03
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
We
have
two
meetings,
one
is
for
now
weekly,
but
eventually
it
will
be
bi-weekly
and
I
believe
it's
been
set
up
later
this
week.
Thursday
was
the
original
meeting
time
for
this
meeting,
but
this
is
now
the
Kufa
to
Tuesday
and
the
other
one
is
now
set
up
Thursday.
If
we
want
to
switch
around
or
do
all
the
editing
don't
be
afraid
to
edit
the
calendar
appointment-
and
you
know
we
can
go
from
there,
but
I
tried
my
best
to
find
that
spot
which
works
for
us.
Sorry,
Laurie.
A
A
Think
it's
how
and
also
to
see
if
we
can
squeeze
in
some
of
the
lower
hanging
fruit
issues
from
the
scorecard
laid
out
issues
which
I
think
are
most
worthwhile
and
also
the
most
easy
to
implement,
which
have
a
significant
improvement,
which
will
make
a
significant
improvement
towards
the
CI
station
below,
like
in
this
low-hanging
fruit
section.
The
exploration
which
you
will
mostly
be
my
own
responsibility
will
be
set
up
later
today
and
will
kind
of
be
part
of
this
effort,
as
well
as
to
you
know,
running
up
to
12
at
7:00.
A
But
that
is
less
about
this
meeting
and
more
about
the
thing
beta
I
would
say,
but
it's
it's
especially
these
glowing
improve
issues
that
I
want
to
discuss
and
see
how
you
think
about.
If
we
are
able
to
squeeze
in
these
these
issues,
they
the
build
issues
need
to
be
created
and
need
to
be
reviewed
by
engineering.
Obviously,
but
I
think
the
scope
for
all
of
them
can
be
pretty.
C
A
B
C
B
So
I
was
talking
to
Jason
yesterday
and
and
then
afterwards,
with
crystal
by
the
way,
just
you
know,
I
think
from
from
from
our
agenda
when
you
link
to
the
build
track
board,
it's
the
same
as
what
I
have
bookmarked
for
myself,
but
just
so
you're
aware,
there's
the
CI
build
track
board
out
there.
I
don't
know
who
created
it
and
crystal
was
sending
the
impression.
B
I'm
sorry
crystal
created
that
well,
the
engineers
and
her
are
using
that,
but
she
and
I
are
trying
to
it.
Has
fewer
columns
for
workflow
labels,
then
the
milestone
tracking
board,
but
she
and
I
are
trying
to
marry
that
up,
just
so
that
she
also
thought
CI.
Workflow
was
something
that
we
were
using.
I
know
Krista
credit
the
build
track
one,
but
the
CI
workflow
I,
don't
know
who
created
that
okay.
B
D
B
What
Jason
I
agreed
is
I'm
going
to
I,
haven't
a
chance
to
do
it,
I'm
I'm,
going
to
when,
when
I
unfilter
on
the
group.
Well,
when
I
unfiltered
on
the
direction
label,
there's
there's
actually
a
lot
more
I'm
gonna
group,
all
the
ones
that
are
buzzed
together
at
the
top,
the
s2
and
then
the
next
group.
It
would
be
all
the
direction
items
in
my
rank
order.
B
B
So
that's
the
reason
why
some
of
these
are
in
this
state,
but
crystal
and
I
are
going
to
try
to
work
through
whether
or
not
during
this
week,
whether
or
not
they
should
remain
in
12.7
or
and
blocked,
or
just
back
to
the
backlog,
because
we
don't
want
to
start
1207
with
things
already
in
black
state.
So
those
four
will
probably
get
cleared
out
this
week.
B
So
regarding
the
direction
items,
I
I
was
glad
to
learn
that
Jason
and
I
are
in
agreement
that,
although
there's
a
teen
direction,
items
for
12.7,
there's
no
expectation
that
engineering
will
commit
to
all
of
them.
But
we
do
want
them
to
groom
them
and
give
them
a
weight
and
then
give
me
an
idea
which
ones
which
ones
I
want
to
negotiate
with.
B
For
example,
Jason
says
if
this
one
that's
currently
ranked
at
the
top
is
going
to
be
a
weight
of
five,
but
the
three
after
it
is
a
weight
of
one
they're,
just
hypothetical,
but
I
may
want
to
rank
the
three
that
are
ones
to
get
them
all
in
above
this
five
and
I
think
five
is
their
maximum
weight.
So
so
crystal
agreed
that
she
wants
to
go
through
the
exercise
with
her
team.
B
Actually
they
have
their
grooming
on
Wednesdays,
and
so,
although
our
normal
production
timeline
has
it
that
by
the
fourth
of
the
month,
I
would
have
a
draft
of
the
issues
for
to
start.
The
capacity
and
techno
discussion
of
engineering,
UX
I'm
actually
going
to
try
to
finish
that
today
on
the
third,
so
that
the
regularly
scheduled
grooming
session
for
engineering
and
the
on
Wednesday
can
look
at
them.
With
my
granddaughter
a
couple
things
Jason's
gonna
help
me
do
is
I'm
gonna
take
my
best
guess
on
the
ranking
of
these.
B
B
He's
gonna
take
a
glance
at
it
and
then
UX
and
engineering
we'll
start
with
your
grooming
as
early
as
tomorrow,
instead
of
instead
of
the
fifth
I
think
I
think
this
is
a
guideline,
but
I
don't
want
them
to
miss
the
opportunity
this
week
and
their
regular
grooming
to
consider
the
issues
already.
So
that's
my
plan
for
today's
meeting
I'm,
actually
not
prepared
to
walk
through
exactly
the
in
rank
order,
all
of
the
direction
items
and
I
think
okay.
B
So
a
lot
of
these
I
mean
there's
18.
Obviously,
all
18
is
not
going
to
feasibly
fit
in
12.7
and
even
if
they
had
the
full
capacity
to
look
at
18
to
groom.
Their
crystal
did
remind
me
that
in
milestone,
12.7
there's
a
lot
of
team
members
that
will
be
out
due
to
the
holiday
and
we're
gonna
be
even
more
conservative.
What
gets
in
I'm
a
pair
this
down
to
maybe
10
that
I
would
like
to
have
groomed
and
and
waited
so
that
I
can
understand
what
might
eventually
make
it
into
12.8.
Even
and.
A
B
Correct
and,
and-
and
it
also
is
in
line
with
the
category
vision
it
it
drys
what
displays
in
the
issue
lists
and
also
in
the
kickoff
page
I
think
the
the
kickoff,
oh
I,
don't
even
know
if
I
have
that
page,
but
but
that
directionally
does
a
couple
things.
It
dries.
What
displays
in
the
the
handbook
page
for
kickoffs
and
also
I
thought
I
had
that
saved
here
it
is
leader.
B
It's
to
be
done,
but
to
answer
your
question:
what
that
direction
label
does
it
does
call
out
significant
features
that
we
would
write
about
in
the
release
post,
but
also
it
dries.
What
displays
here
on
this
page?
This
page
is
looking
for
everything
that
has
that
direction
label,
regardless
of
milestone,
I,
believe
yeah.
A
B
A
Yeah,
because
the
the
issues
then
I'll
be
creating
today
that
document
I
would
say
a
few
of
them
certainly
have
those
requirements
included
into
them.
They
are
worthwhile
to
be
discussed
inside
a
released
blog
post
and
they
do
provide
considerable
value
towards
the
user,
I'm
a
little
bit
less
sure
about
how
that
their
CI
Direction
page
how
it
should
align
with
that
I
think
it
does,
but
I'm
less
familiar
with
that
purpose.
I
think
it
has
changed
and
it
is
more
of
a
CI
CD
direction.
Instead
of
specifically,
CI
relate
right.
No.
B
This
one
is
specific
to
CI
this
one
is
specific,
yeah
and-
and
this
page
is
maintained
by
the
PM
I
mean
the
the
latest
revisions
were
done
by
Jason.
I
haven't
started
editing
these.
He
has
asked
every
PM
to
update
these
on
a
monthly
basis.
You'll
see
yeah,
so
so
there
is,
there
is
the
general
CI
vision
page,
which
is
I,
mean
see,
ICD
vision,
page,
which
is
this,
but
the
one
I'm
talking
about
is
specific
to
our
area.
Ci.
Only
oh
yeah.
B
A
B
I,
it's
so
in
this
timeline.
You'll
see
as
of
last
week
where
it
says
product
page
our
update
to
reflect
previous
current
releases,
including
category
epics
and
Direction
page.
This
was
actually
due
last
week
when
I
was
out
for
the
holiday
for
the
US
Thanksgiving
holiday,
and
so
he
said
it's
fine.
If
I
come,
you
know
come
back
and
edit
this
later,
but
this
section
here
is
what
I,
as
a
p.m.
B
You
know
facilitating
the
the
onboarding
of
new
users
to
the
pipeline,
creating
and
using
the
pipeline
more
effectively.
So
this
this
will
be
edited.
Obviously,
in
the
past
it
shows
that
we
were
going
to
focus
on
the
the
dag
pipelines,
but
I
think
we're
gonna
get
I
have
to
reconsider.
This
I
think
we're
gonna
get
more
about
you
pursuing
the
the
work
that
we
talked
about
yesterday,
yeah.
B
A
A
They
should
be
Direction
issues
as
mentioned
and
label
them
tentatively
as
good
as
possible,
and
then
I
would
love
for
them
to
be
included
in
your
grooming
that
you
are
doing
today,
like
the
stack
rank
for
current
milestone
for
engineering
to
review,
because
I
think
with
that
that
we
will
be
just
on
time
to
give
engineering
a
fair
chance
to
really
jump
into
it.
Right.
Yeah.
B
B
C
A
Are
looking
for
these
kind
of
improvements?
It's
not
just
on
the
way
it's
like
they
are
a
problem
founded,
I,
think
that
speaks
for
itself
and
yeah.
I
think
it
looks
good
and
I
think
it's
all
it's
worth
well,
regardless
to
you,
know,
review
those
fossil,
because
that
has
been
a
practice
for
as
long
as
I
can
remember
to
just
Park
them
later
and
later
into
certain
milestones,
and
then
you
know
review
them
as
that
milestone
comes
up
and
see
if
actually
still
works
out
as
intended.
Yeah.
B
B
So
if
you
send
me
the
issues
that
you're
proposing
for
12.7
I
might
try
to
sync
with
you
early
early
tomorrow
morning,
like
midday,
your
time
just
to
make
sure
we're
on
the
same
page,
so
that
when
I
come
to
this,
this
meeting
for
the
CI
team
grooming
I
can
give
them
just
a
quick
overview
of
what
you
and
I
were
thinking
proposing
for
12.7.
It.
A
E
A
I
will
so
the
issues
I
will
be
creating
will
have
an
initial
proposal.
I'll
try
to
prepare,
as
best
as
possible,
to
give
some
visuals
at
the
very
least.
It
may
be
so
that
you
know
engineering
has
a
little
bit
of
a
better
look
at
what
the
problem
space
is
because
they
have
to
wait.
Wait
the
issues
right.
Yes,.
B
A
B
A
It's
a
I
have
been
in
contact
in
the
past
with
QA
to
see
like
if
we
can
more
closely
work
together
that
had
like.
We
figured
out
some
things,
but
it
kind
of
water
down
at
some
point
because
different
things
to
priority
for
both
me
and
is
that
Morgan.
But
it
might
be
an
interesting
thing
to
look
into.
A
A
B
I
don't
know,
I
do
know
that
they're
there
they're
not
they're
shared
across
a
lot
of
teams
and
so
they're
not
necessarily
available
at
the
individual
team
level.
Planning
sessions,
yeah
I
think
when
the
team
grows
and
we
have
a
dedicated
one.
It
would
be
easier
to
include
that
person.
That's
dedicated
to
CI.
A
B
Yeah
verify
so
yeah,
so
I'm
I'm
waiting
to
find
out
more
about
that.
So
right
now,
they're
not
included
in
these
sessions,
so
I'm
looking
at
the
agenda
for
this
meeting,
so
one
there's
two
ones,
but
one
be
makes
sense.
Oops.
B
F
A
Yeah
from
my
side,
I've
been
preparing
a
little
for
the
thing
big
session
on
the
highlighting
it's
right
now.
This
is
what
I
have,
but
I
think
it
would
be
valuable
to
have
input
from
any
of
you
in
terms
of
like
what
your
expectations
from
these
meetings
are,
and
perhaps
also
a
press,
for
example,
for
Laurie
like
hey.
How
are
you
thinking
from
a
US
research
perspective?
A
That's
do
you
know
the
cadence
we
are
going
because
I
was
I
was
actually
doing
some
calculations
for
myself
as
to
like
what
is
the
cadence
of
efforts
we
have
and
you
mix
research,
I
kind
of
like
I,
compress
it
as
much
as
possible,
but
setting
it
up
and
working
it
out
until
the
end.
It
still
takes
one
and
a
half
months.
So
it's
like
it's
a
rhythmic
cadence
versus
our
release
and
development
cadence,
so
it
kind
of
like,
like
it's
always.
E
Just
why
we
are
trying
to
do
it
ahead
of
time
yeah
we
are
trying
to
do
it
ahead
of
time.
Did
you
can?
If
you
push
it
hard
enough,
you
could
do
it
in
a
month.
You
can
do
it
in
a
milestone.
If,
if
you
knew
what
you
needed
to
do,
often
we
don't
and
that's
where
those
extra
two
weeks
come
in
to
try
to
talk
about
and
identify
to
figure
out
what
it
is
that
we
need
to
learn
and
then
we
get
started
and
then
there's
that
month
milestone.
E
A
C
A
Are
some
valuable
points
which
I
think
we
both
are?
We
all
can
take
into
mind
when
doing
these
meetings.
They've
been
like
the
the
the
points
on
it
down,
basically
are
for
us
to
consider
they're,
not
you
know,
set
in
stone
or
anything
like
that,
but
I
think
it's
worthwhile
to
like
hey.
What
do
you
think
about
this?
Does
this
help
you,
or
this
helps
me
in
a
certain
way?
A
For
example,
it
was
a
little
bit
influenced
by
the
package
thing
basically
and
so
Myers,
but
it's
I
think
there's
some
good
food
practices
in
there,
but
yeah
absolutely
Lori,
focusing
on
twelve
of
eight
twelve
mine
through
tooth
research.
I.
Think
now
is
the
time.
So
we
have
the
inspiration
for
twelve
seven
to
elevate.
We
got
this.
You
know
we
also
need
to
think
about
the
research
from
12-day
1209
I
think
that
is
that's
the
good
thing
to
do,
and
especially
a
good
topic
of
discussion
for
the
next
session.
F
I
think
this
is
a
very
good
point
that
you
both
are
highlighting.
I
see
the
package
are
discussing
there,
two
milestones
ahead,
the
issues,
the
topics,
the
ideas
and
they
kind
of
like
they,
what
they
do,
I'm,
not
sure,
if
any
of
you
seen
they
kind
of
like
maintain
a
list
of
ideas
that
can
come
from
anybody.
You,
engineering,
UX,
research
p.m.
whatever
and
I
think
they
kind
of
like
voting.
What
are
they
commit?
What
is
the
one
thing
that
they're
gonna
discuss
during
this
thing?
F
B
For
my
part,
I
think
from
the
the
product
management
I.
Think
I
need
to
think
there
this
week
and
we
chase
is
help
to
figure
out
what
we're
gonna
focus
on
for
12.8
and
dot
nine
and
then
maybe
by
this
meeting
next
week
or
I'm.
Sorry
do
we
do
we
want
to
cover
that
as
early
as
this
week's
session
yeah.
A
Preferably
we
would
but
I
think
you
can
take
that
information
along
into
your
meeting
with
Jason,
and
you
know
consider
it
with
him
to
say.
Okay
is
this:
this
is
aligned
with
our
thinking
and
direction
and
strategy,
because,
if
not,
then
we
perhaps
we
need
to
you
know
slightly
diverge
and
and
adjusted
a
little
bit.
So
it's
Co
aligned
with
product
management
thinking.
B
Okay,
alright,
so
I'll
try
to
get
to
Jason
before
our
thing
big
session,
this
Thursday
and-
and
so
you
know,
he's
helping
me
a
lot
as
I'm
still
on
morning
and
then
it'll
as
I
get
more
familiar
and
comfortable
with
it.
I
won't
need
to.
He
won't
be
a
bottleneck
for
me
for
forgetting
the
stuff
that
you
guys
need.
B
A
F
E
Yes,
that's
part
of
it,
so
product
vision
is
the
map
as
I.
Think
of
it
as
a
map
like
you're
telling
me,
were
you
on
this
product
to
go
then
for
the
research
piece
of
it.
I
need
a
little
bit
more
detail
of.
What
is
it
that
you
need
know?
What
are
the
questions
you
have
answer?
You
need
answers
to
in
order
to
move
that
vision
on
that
roadmap
that
you
need
to
for
it
to
go.
So
it's
it's
a
kind
of
both
of
those
things.
Yeah,
okay,.
E
Or
what
have
we
done
in
the
past
since
everybody's,
so
new,
the
older,
the
person
you
can
find
the
better
in
in
so
that's
kind
of
a
good
cadre
of
people
to
have
together
in
in
a
synchronous
meeting
to
start
the
opportunity
canvass
for
something
so
like
with
Daren
one
and
I
were
in
a
meeting
with
him
a
week
or
two
ago
and
Darren's
like
I.
Don't
know
what
to
do,
and
this
is
what
I've
got
one
sided
before
I
could
and
he's
like
yeah
you're
gonna
meet
for
opportunity
campuses
for
this.
B
Gotcha,
okay
and
so
so,
Nadia
I'm
gonna
show
you
what
I'm
looking
at
that
is
on
point
for
what
Lori
and
I
are
talking
about,
so
I'm
going
to
take
a
stab.
So
this
is
the
flow
of
our
product
development
with
work
which
is
different
than
the
product
development
timeline,
but
from
the
opportunity
canvas,
then
it
kind
of
drives
the
next
thing,
which
is
that
validation
phase
one
having
that
backlog,
which
is
in
line
with
the
vision
and
then
problem
validation,
is
this
correct
Lori
that
this
is
really
when
the
UX
research
is
heavily
involved?
B
B
F
Tower
no
worries
seriously
I
see
this
all
of
the
stages.
It
really
takes
time
you
know,
and
for
myself
as
well,
it's
like
my
side
is
less
deliverable,
so
you
know,
like
I,
have
a
little
bit
time
to
look
into
that.
If
you
will
need
any
help
with
figuring
out
the
problem,
validation
and
solution,
validation,
processes
or
stages
feel
free
to
get
in
touch.
We
can
do
this
together.
You
know,
if
there's
anything
that
I
can
help
you
with
just
let
me
know
as
well.
Yeah.
B
F
Let
us
know,
let
me
see
this,
let
us
know
if
you
think
the
thing
big
session,
if
we
are
ready
for
this
this
week
or
you
kind
of
like
need
a
little
bit
of
time,
and
we
should
have
our
first,
maybe
then
next
week.
So
if
you
like,
you
know,
you
can
have
some
time
to
catch
up,
collect
the
information
from
Jason
etc.
Let
us
know
like
don't
feel
too
rushed
as
well.
Yes,.
B
B
This
has
such
a
bias
towards
action,
and
so
it
may
be
ugly,
the
first
one,
but
this
is
my
first
iteration
we
might
as
well
get
it
started
because
I'll
learn
during
this
week's
think
big,
really
how
we're
gonna
do
those
I'll
get
the
most
value
on
that
and
then
I
have
as
much
as
I
can
for
us
to
go
over
and
then
I
get
better.
It's
just
I,
just
otherwise.
If
I
wait,
till
I
am
completely
comfortable,
we'll
miss
women
so
much
time.
E
B
Good,
but
you
know
what
Nadia
it
may
be
new
for
maybe
all
of
us,
but
but
dimitri
mention
something
about
the
package
team
I
think
they've
been
doing,
think
big
sessions
for
a
while
now
granted.
That
p.m.
has
been
around
a
lot
longer
than
I
have,
but
is.
F
Been
yes
antara
recordings,
there
are
video
recordings
and
there
are
notes
off
there
such
chance
and
I.
Think
if
you
will
look
through
them,
if
you
like
it
would
be
so
much
easier.
So
let
me
actually
well,
as
we
talked
I,
think
I
pasted
it
in
the
past
some
of
the
recordings
here.
Let
me
just
place
them
again
to
the
top,
as
we
talk
just
watch
through
that
I
feel
this
will
be
helpful.
You
know:
okay,
you're.
E
A
Been
talking
with
Ian
a
lot,
though
about
it
as
to
how
they
do
it
like,
because
I
had
a
coercion
to
get
Nadia
and
Ian
in
Rotterdam,
so
I
was
actually
like
Ian
and
me
were
no
hear
each
other
out
how
we
do
certain
processes.
You
know
you
have
a
little
bit
of
a
dick
going
back
and
forth
as
to
you
know
why
you
do
certain
things.
What
was
the
intent?
What
was
the
origin?
A
So
I
have
not
watched
the
recordings
yet,
but
I
do
a
little
bit
know
why
they
did
certain
things
a
certain
way
and
I
think
that
helps
to
lock
them
in
one
of
our
previous
sessions.
I
think
I
proposed
Mike,
hey.
You
know
this
recordings
actually
the
same
thing,
but
otherwise
here
out,
for
example,
that
product
manager
package
that
would
be
like
a
similar
peer
to
peer
back
and
forth
discussion
as
I
would
have
had
I,
as
I
have
had
with
you.
Okay,.
B
F
F
B
C
F
C
B
So
you
know
what
Dimitri
so
I
know
that
we
talked
about
inviting
engineering
to
the
think
big
sessions.
What
we
can
ask
at
the
the
CI
engineering
teams
back
logarithm
tomorrow,
if
there
are
things
that
are
questions
that
maybe
we
can
also
answer
for
the
newest
issues
that
you're
creating
based
on
the
work
to
improve
pipeline
creation.
B
A
F
Well,
I,
don't
even
tell
who
attends
then
it's
VM,
perhaps
fronting
and
back
in
engineers,
I'm,
actually
amazed
by
how
much
participation
is
from
engineering
there
I
was
saying
to
Ian.
It's
like,
oh,
my
god,
I,
don't
know
how
they
initially
came
to
that.
But-
and
everyone
is
pretty
active.
I
can
imagine
this
crap.
It
will
take
some
time,
but
yeah
I
would
kind
of
like
say
that
we
try
to
invite
like
engineering,
UX,
research
and
p.m.
like
this
plus
venue,
and
not
every
one
of
the
engineering
should
be
but
yeah.
B
So
that's
so
that
makes
me
think
then
Dimitri
that
maybe
to
to
start
this
recurring
cycle
off
on
it,
honey
on
the
correct
flow
that
we
want
is
we
don't
introduce
the
items
that
you're
creating
for
them
to
groom
tomorrow,
we
invite
them
to
come
to
the
thing
next
session,
where
we
talk
through
this
new
chunk
of
work,
we're
doing
for
improving
pipeline
creation
and
we
cover
it
at
the
think.
Big
session
talk
it
through
with
engineering
in
the
room
and
then
they
room
those
actual
issues
the
following
week.
B
It
would
be
December
11th
the
following
week,
but
I
think.
Let
me
see
December
11th,
based
on
the
engineering
based
on
the
development
time
line
they
left
by
the
13th
of
every
month.
The
issues
are
groomed,
so
they
so
there's
a
there's
time
for
them
to
do
it.
That
way,
because
I
think
normally
the
flow
is
they
participate
in
a
think
big
session.
B
A
Needed
just
to
make
sure
we're
alive,
because
I
feel
word
we
might
be
mixing
the
intent
of
the
meaning
of
the
thing
babe.
The
grooming
session.
Some
grooming
session
is
for
upcoming,
milestone
right.
Anything
related
to
that
should
be
in
the
grooming
session
or
a
weekly
engineering
meeting
that
we
already
have
I.
Think
it's
perfectly
fine
to
discuss
things
like
that.
The
thing
big
session
should
be
dedicated
to
what's
know
the
milestones
after
that
looks
like
12:00
at
8:12
at
9:00
those
things
like
I.
A
B
Yeah
thanks
for
that
reminder
that
makes
sense,
in
which
case
Nadia
I'm
not
going
to
have
engineering
joined
this
week,
because
there
crystal
tones,
Nate,
they're,
so
new
there
she's
just
wanting
them
to
nail
down.
Let
me
show
you
this
to
get
comfortable
with
this
whole
flow
for
the
engineering
cycle
before
we
start
involving
them
in
the
validation
cycle
of
I,
don't
know
where
it
went.
It's.
A
A
good
idea,
and
also
like
as
if
we
think
about
it,
iteratively
it
might
make
sense
to,
for
example,
first
start
out
with
only
you're
fighting
the
engineering
manager
and
then
the
next
iteration.
After
that
infighting,
you
know
engineers
themselves,
you
know
work
our
way
upwards
and
also
the
next
one
is
going
to
be
our
first
thing
big
session
anyway.
So
I
think
it's
nice
for
us
to
align.
First,
then,
okay,
five
engineering,
slowly
and
then
try
to
rest
as
we
feel
is
appropriate.
It's.
F
Everyone
together,
however,
and
I
understand
the
fact
that
you
are
saying
that
they're
new,
and
probably
they
have
other
things
to
focus
in
the
engineering
involvement
into
the
sessions,
is
more
like
for
listening
to
their
input
as
well
and
their
ideas,
so
to
make
sure
that
no,
but
no
one
is
excluded
and
I
am
afraid
that
the
risk
with
the
fact,
including
them
after,
is
that
they
kind
of
feel
like
yeah.
This
is
more
pmu
acts
meeting
we
don't
really.
We
are
not
really
necessary
here.
However,
let's.
B
Yeah,
let's,
let's
maybe
target
in
January,
we
start,
including
the
engineering
manager
and
then
as
she
in
they
think
big
sessions
and
then,
as
she
gets
familiar
with
the
content
of
what
we
cover
there,
then
she
can
guide
us.
You
know
on
which
you
know
when
to
start
involving
the
actual
CI
engineers,
yes,
that
sound
good,
yeah,
okay,
so
yeah,
so
so
you're
right
Jimmy
treat
the
that
I'm
I
was
mixing
those
up
because
of
the
way
I
did
it
in
my
last
my
last
company
but
you're
right.
B
A
This
sounds
good
by
the
way
to
me.
It
goes
away
we
now
discussed.
So
tomorrow
will
still
you
know.
The
engineering
will
have
the
opportunity
to
go
over
the
meetings
that
will
be
included
in
the
milestone
today.
I'll
be
creating,
and
you
know
messaging
to
you
a
little
later
today
on
slacks
we,
you
will
get
an
immediate
pain
set
up.
That
is
one
of
the
many
two
things
that
you
get
and
I
think
we're
on
timing
with
that.
So
that's
that's
good
and
then
Thursday
will
be
the
think
big
session,
and
we
we
go.
A
C
B
A
We
covered
this,
but
this
is
basically
the
issues
that
that
I
will
be
creating
and
communicating
back
to
you.
We
had
a
little
bit
of
a
chaotic
way
of
documenting
what
has
been
said.
This
meeting
and
the
thing
big
I
will
be
copying
towards
the
next
CI
unit,
so
that
will
be
it's
basically,
the
part
in
the
hand
quickly
I'll
do
that
immediately.
So
it's
no
longer
confusing
us.
F
Yeah
I'm,
sorry,
everyone
I
have
to
drop
I,
have
another
meeting
in
five
minutes.
I
need
to
take
a
small
break,
but
yeah
the
planning
sounds
good.
So
looking
forward
to
the
thing
being
big
and
to
meet
you,
let
us
know
if
there
is
anything
I
can
do
at
all.
Let
me
know
if
I
need,
if
you
need
any
of
my
help.
Okay,.
C
A
A
E
Was
just
to
talk
about
twelve,
eight
and
twelve
nine,
so
I
know
tell
you're
hard
at
work
and
don't
you
worry
I'm
very
patient
I.
Just
don't
want
to
miss
anything
for
you.
So
you,
whenever
you
have
a
chance
to
look
at
everything.
Let
us
know
and
we
can
have
another
chat
about
twelve
eight
twelve
nine
I'm
happy
to
chat
about
it
in
another
meeting
that's
already
set,
but
if
the
meeting
already
has
an
agenda
that
we
need
to
talk
about,
then
we
need
to
create
another
one
to
talk
about
agent.