►
From YouTube: Verify CI - Thinking big planning 2019-12-05
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
B
What
I
can
do
is
for
each
because
these
are
subject
to
change
and
new
things
come,
and
the
think
big
session
with
the
entire
team
will
not
happen
with
the
frequency
that
there's
likely
to
be
new
things
in
between
each
session
that
gets
created.
I
would
probably
just
refer
at
a
glance
that
this
is
the
filtered
list.
Loop
start
getting,
you
can
go
through.
You
can
have
an
idea
of.
B
What's
there
but
I'm
gonna
say
we're
gonna
focus
on
this
one
epoch
I'm,
not
gonna,
review
the
others,
and
then
we
would
go
into
our
session
that
might
be,
and
that
and
then
they
thanks
for
sharing.
Then
they
wouldn't.
We
would
spend
probably
less
than
like
a
minute
displaying
that
these
are
all
the
epics,
and
this
is
a
specific
one.
That's
the
topic
for
for
this.
This
that
particular
think
big
session.
We
can
include
the
link
to
the
filtered
list
of
all
of
the
epics
specific
to
the
CIT.
B
The
CI
group
in
the
meeting
invite
the
invite
that
is
for
the
entire
CI
team,
but
I
it
might
have
been
a
different
video
that
I
listened
to
I
know
Nadia.
Thank
you
for
sharing
three
of
package,
teens,
think
big
session
video
and
if
one
of
those
videos
that
I
didn't
watch
was
the
one
where
he
went
through
all
the
ethics,
it's
the
first
ever
thing
big
day
they
had
right
and
in
every
subsequent
one
they
might
not.
I.
B
Don't
want
to
assume
that
first
session
that
knowledge
carries
over
to
any
team
member
that
comes
to
the
subsequent
ones,
so
I
think
out,
just
in
the
interest
of
time,
just
like
cuz,
the
one
I
listen
to.
He
just
had
a
very
specific
topic
and
they
covered
that
right.
Yeah.
They
kind
of
ran
out
of
time
as
it
was
yeah.
C
D
D
Something
is
going
to
happen
here.
Are
we
still
aligned
on
that
those
kind,
so
I
just
wanted
to
showcase
this,
because
I
feel
like
this?
Is
you
know
if
we
even
push
this
to
like
a
sickness
to
each
other?
It
doesn't
give
us
a
lot
of
context
or
like
hey,
which
ones
are
important.
Do
we
need
to
filter
down
even
further
that
kind
of
thing?
Well,
if
it's
really
at
the
time,
you
can
immediately
see
like
alright.
These
three
epochs,
for
example,
say
that
it's
only
about
three
or
these
three
are
happening
right
now.
D
D
B
D
I
would
say
a
review
of
those
at
the
same
time,
Alex
by
default
are
configured
to
take
up
the
time
that
is
set
in
the
milestones
in
the
issues
that
belong
to
those
ethics
sounds
way
too
complicated.
But
basically,
if
you
put
in
an
issue
where
it's
a
your
milestone,
12
of
nine
and
twelve
and
five
two
issues,
basically
right,
then
the
time
frame
is
automatically
adjusting
towards
those
those
milestones.
And
thus
the
bar
will,
you
know,
begin
somewhere
in
October
and
somewhere
in
March,
just
to
give
an
example.
B
Yes,
except
if
you,
if
you
click,
let's
say
if
you
go
to
the
last
epic
yeah
and
actually
open
up
in
another
tab,
you'll
see
that
on
the
right.
I
mix
this
to
me
that
yeah,
those
are
hard
to
find
dates
which
I
don't
know
where
those
how,
if
even
Jason,
said
those
and
what
those
are
that's
social
media
that
doesn't
allow
the
dates
to
be
dynamically.
Driven
by
the
issues
under
the
epic.
D
So
the
current
few,
like
the
current
epoch,
we're
looking
at
you,
see
inherited
right.
So
these
days
are
inherited
from
the
issues
inside
of
this
epoch.
If
you
don't
want
that
that
you
should
edit
and
put
a
fixed
date,
this
is
manually
setting
a
date
for
an
epoch
and
not
having
it
inherited
so
say,
for
example
17.
D
But
it's
inheriting
from
generally
eighteenth
of
because
of
the
issues
in
here
because
one
has
been
scheduled
for
tala
day
so
see
it
was
February
17
2020,
and
here
we
see
February
17
2020,
the
others
are
in
backlog
and
there's
no
dates
assigned
to
those
milestones.
So
it
cannot
include
or
inherit
any
date,
information
from
that.
But
if
the
value
have
been
set
to
be
inherited,
I
can
specifically
inherit
the
data
from
its
child
issues.
Basically,
okay.
B
So
in
that,
in
that
case,
if
you
go
back
to
the
roadmap
view
of
the
epochs
it's
misleading
to
see
to,
if
I
mean
we
would
in
showing
this,
because
it
wasn't
clear
to
me
looking
at
this,
it
seemed
to
say
that
the
work
for
this
is
that
duration,
but
that
duration
doesn't
account
for
issues
that
haven't
been
given
a
milestone.
That's.
B
D
B
D
Like
it,
it's
an
important
point
and
I
think
the
way
that
you
know
we
have
moved
from
issues
into
epic
territory.
This
was
kind
of
a
way
to
make
epics
a
little
bit
more,
auto
managed,
but
I
would
certainly
say
that
if
we
want
to
have
more
control
over
that,
then
we
should
set
the
fixed
dates,
and
in
that
way
you
know
we
have
more
control
about
what's
happening,
even
though
we
might
adjust
some
of
the
child
issues
inside.
A
D
B
Let
me
let
me
think
about
that,
because
we,
by
the
way
after
I,
give
this
thought
I
do
want
to
go
back
to
what
Nadia
mentioned
in
the
an
hour
zoom
chapter
of
the
agenda
for
this
session,
I'm
I'm
I'm
in
a
little
bit
of
a
conflict
that
I
need
to
work
out
because
of
the
different
input
areas.
D
B
Engineering
side
they
they're,
you
know
Chris
and
I
talked
about
yesterday
as
they're
asked
to
look
to
Kanban
and
they
want
to
because
it's
a
lot
more
agile
and
that
then
they're
not
pre,
defining
issues
for
a
milestone
that
ends
up
showing
it
creates
a
scenario
of
them
missing,
milestones
and
things
being
moved
carry
over
to
successive
milestones
because
it
was
already
predefined
for
them.
What
would
be
I
mean
if,
before
I
start
move
things
they
even
out
of
milestone?
B
12.7
there
were
80
issues
in
12.7,
it's
daunting
for
the
engineering
team,
and
so
I
was
like
okay
I'll
do
team
has
gone
to
Kanban.
All
the
other
engineering
teams
want
to
go
to
Kanban,
but
in
doing
so
it
inflicts
with
the
product
management
kick
offs
of
knowing
exactly
what
issues
are
gonna
get
delivered
because
they
get
pulled
in
dynamically,
an
iteration,
a
milestone
right.
A
Shouldn't
there
be
planning
so
like
I
with
this,
because
I'm
like
I,
was
a
scrum
master
on
my
last
job,
so
I
struggled
with
with
seeing
how
people
approach
trying
to
do
agile,
but
not
do
agile
and
100%
like
they
do
they're,
picking
and
choosing
pieces
of
it.
And
at
some
point
you
have
to
like
plan
right.
A
A
B
B
Commit
to
more
so
yeah
in
that
model.
It
does
not
give
the
p.m.
a
very
distinct
list
of
issues
to
talk
about
that.
Your
father
and
tend
to
label
for
specific,
most
I
mean
we'll
have
a
general
idea
when
I
say
well,
we
will
have
let's
say
the
team
normally
can
finish
points
in
the
waited
when
they
wait.
Something
uh-huh
so
we'll
put
in
15
to
be
conservative
right,
but
we
know
those
15.
D
B
On
the
17th
of
every
month,
I
could
only
mention
those
issues
that
amount
up
to
15
right,
right,
yeah,
and
so
there
is.
There
is
some
planning
that
can
it
defy
the
ones
that
will
definitely
be
committed
to,
but
engineering
wants
to
reserve
the
right
to
add
the
deliverable
label
when
they're
sure
that
they
can
take
on
more
within
the
milestones.
B
B
A
A
D
A
B
Me
too,
okay,
so
na
di
you
were
just
saying
in
the
chat
that
telling
Nicole
for
this
session
yeah.
C
So
maybe
the
first
question:
are
we
taking
this
session
to
discuss
like
questions
like
like
we
have
been
discussing?
You
must
half
an
hour
or
during
three
years
half
an
hour
or
do
we
want
to
actually
like
really
go
ahead
and
start
making
and
epics
or
like
just
looking
into
some
of
the
work?
Some
of
the
milestones
in
future
milestones
work
so.
B
And
so
then
I
had
to
go
through
and
change
the
filter
to
look
at
everything
that
was
DevOps
verify,
and
then
this
morning
I've
been
going
in
and
adding
the
label
to
make
sure,
and
so
the
list
that
I'd
sketch
you
all
the
in
the
link
in
the
chat
has
11
but
there's
more
out
there.
So
I
think
I
need
some
time
to
not
only
find
all
of
them,
and
then
we
could
look
at
the
the
true
list.
B
B
About
when
there
are
a
lot
of
epochs
to
consider
what
is
there
something
that
he
uses
to
I
was
asking
him
what
he
used
as
a
guide
for
think
big
sessions,
and
he
actually
said
he's
never
done
them.
So
he
didn't
have
any
suggestions
on
that.
But
if
someone
can
do
meet
you,
if
you
can
open
that
page
that
I
just
put
in
the
zoom
chat,
he
did
ask
me
to
when
looking
at
the
epics
to
decide
what
we
would
discuss
in
think
big
session
to
go
ahead
and
make
sure
that
were
I.
B
This
hasn't
been
updated,
obviously
because
it
mentions
the
dag
that
has
work
that
we've
kind
of
already
made
a
lot
of
progress
on
so
so
that
was
one
of
his
suggestions
and
then
he
says
if
you
go
up
a
little
further
Demitri
either
under
top
customer
issue
or
under
top
internal
customer
issue.
These
will
also
call
out
epics
that
would
also
feed
into
the
think
big
sessions,
and
he
told
me
I
probably
need
to
go
through
and
update
these
because
it
he
PMS
are
asked
to
keep
this
vision
page
for
their
cat
for
their
category.
B
Updated
I
have
not
updated
this
page
for
them
in
the
month
of
November
I.
Think
the
ask
is
to
do
it
the
last
week
of
November
last
week,
and
the
deadline
was
last
Friday
and
I
was
out
for
the
Thanksgiving
holiday.
So
the
first
step
from
all
of
his
direction
for
me
is
update
this
page
and
let
it
determine
the
topics
for
our
think.
Big
sessions
make
sense,
yeah
yeah,
and
he
also
in
realizing
that
as
I
was
clicked
through
in
filtering,
to
find
all
the
epochs
to
know
which
epochs
to
mention
in
this
session.
B
D
But
please
please
back
up
with
Jason
on
this,
that
there
isn't
too
much
like
their
epics
haven't
been
extensively
used
yet
for
CI.
So
I
think
we
have
an
opportunity
here
to
start
fresh
and
set
the
groundwork
yourself.
Instead
of
you
know,
doing
a
lot
of
research
into
something
that
has
been
not
been
managed
in
the
past
so
much
and
instead
of
we've
relied
emissions.
B
Yeah
I
yeah,
so
we
probably
do
need
some
fresh
epics,
but
I
still
want
to
label
these,
so
that
they're
at
least
discoverable.
For
me
to
to
get
my
mind
wrapped
around.
What
all
is
the
work
that
is
in
the
that
is
in
our
of
existing
epic,
so
I
kidding
an
awareness
of
what's
out
there,
that
we
need
to
be
accounting
for
in
our
both
our
planning
and
our
think
make
sessions
like
if
you
refresh
the
just
before
this
meeting
I
was
going
through
that
activity.
B
If
you
refresh
the
list,
I,
there's
like
two
more
that
I
found
now
there's
thirteen
that
actually
is
about
our
topics
relating
to
continuous
integration,
so
yeah.
So
there's
a
lot
of
cleanup
that
I
need
to
do
and
I
could
see.
You
know:
I
I
heard
that
epics
actually
was
not
mature
in
our
issue
tracker
and
so
until
recently,
a
lot
of
you
know
Jason
and
his
peers
were
avoiding
epics
a
little
bit
like
you
said
like,
for
example,
someone.
B
D
This
this
issue
doesn't
include
any
dynamic
lists
as
far
as
I
can
see.
Perhaps
these,
but
that
might
be
the
only
one
dresses
all
manually
implemented
and
kept
up
to
date.
To
some
extent,
I
didn't
know
that
product
has
always
put
for
a
way
to.
You
know
make
this
as
dynamic
as
possible,
which
they
have
done
and,
for
example,
Direction,
page
I
feel
like.
D
B
Kickoff
page
is
dynamic,
yeah,
okay,
so
so
for
the
first
agenda
item.
What
I'm
gonna
do
is
because
this
meeting
is
every
week
for
now
prior
to
our
next
meeting.
My
goal
would
be
by
Monday
I'm,
going
to
add
to
this
agenda
the
epics
that
I
that
we'll
discuss
a
week
from
today
and
forth.
Our
next
I
would
call
these
sessions
think
big
planning,
because
that's
what
we're
doing
we're
planning
out
what
we
would
be
for
the
entire
team
think
big
sessions
right.
This
is
that
sound,
accurate,
I.
C
D
D
You
know,
which
is
gonna,
have
an
effect
two
or
three
miles
out
from
now
and
the
later
we
start
with.
With
that,
you
know
the
later.
The
results
will
come
in
so
I
would
say
the
sooner
we
can
get
to
something
actionable
with
that.
We
have
at
least
something
even
if
it's
not
going
to
be
perfect
and
then
the
rest
of
the
meeting
is
instead
focused
on
a
process
of
refining
that
and
getting
as
close
to
the
actual
ripening.
B
The
sharing
of
research
results
is
it
intended
that
that
is
normally
done
with
the
entire
team,
because
that
has
not
been
my
practice
and
that
and
I'm
okay,
if
that's
what
we
want
to
do,
but
usually
I
interpret
that
to
mean
we.
We
always
have
a
standing
session
where
p.m.
UX
researcher
and
product
designer
sync
up.
Just
the
three
of
us
to
talk
through
research
results
planned
research.
B
You
know
upcoming
interviews,
things
that
we
wouldn't
normally
need
to
involve
the
engineers
for
and
then
in
a
separate
session
when
we're
actually
looking
ahead
to
a
future
quarter
of
work
like,
for
example,
that's
when
everyone
comes
together
and
that's
after
the
research
has
been
synthesized
and
we're
presenting
to
the
team.
This
is
what
we
found.
This
is
are
some
of
the
proposed
design.
Let's
talk
through
what
makes
sense,
but
those
sessions
with
the
entire
team
I
wouldn't
normally
go
deep
dive
into
research
results
in
planning,
interviews
and
stuff
question.
C
B
C
C
Usually
they
are
not
involved
into
the
research
process,
but
whenever
we
are
discussing
debriefing
or
discussing
a
summary
on
what
we
learned,
I
think
it's
very
important
for
them
to
be
there
and
hear
that
it's
also
actually
to
be
involving,
like
the
whole
team,
in
viewing
the
research
from
a
secret
room
right
on
the
second
monitor
or
something
so
they
actually
see
what
users
say
or
do
themselves.
I
know
this
is
a
bit
I
mean
I,
know
we're,
probably
not
gonna.
Do
that,
but
just
saying
that
to
my
experience.
C
D
B
Same
page,
Demetri
I
want
the
engineers
to
you
and
if
they
want
to
see
the
raw
data
the
interviews
are
recorded,
we
can
share
that
links
to
them
if
they
want
I,
don't
think
they
need
to
participate.
Real-Time
in
that,
and
so
for
me,
it's
very
ambiguous
that
phrase
share
research
results
if
it
means
all
the
stuff
post,
synthesize
share
that
synthesize
stuff
with
them,
but
if
it's
all
the
in-between
stuff
or
we're
talking
about
the
raw
data,
trying
to
figure
out
what
the
some
of
the
activities
doing
the
UX
scorecard
activity
I.
B
A
Post
analysts
analyzation
so
tell
you're
right,
so
it's
it's
the
outcomes.
What
have
we
learned?
What
have
we
already
looked
at
the
data
and
found
from
it?
However,
I
will
put
my
vote
in
to
say
that
I
would
love
to
have
something
Belapur
sitting
on
some
of
these
sessions
to
listen.
It's
not
a
requirement,
but
often
developers
have
told
me
in
the
past.
A
I
don't
know
who
I
am
designing
for
I,
don't
ever
get
to
meet
the
end
user
and
I'll
get
to
see
them
and
yes,
the
videos
are
available,
but
as
anybody
in
this
call
knows
it's
very
very
difficult
to
make
time
to
watch
videos
after
you're
done
for
the
day.
You've
done
your
work
so
and
I
do
understand
like
their
priority
is
coding
and
they
have
to
focus
on
that.
But
I
would
like
to
open
those
sessions.
Up
to
them
is
optional.
A
B
Yeah
I
hear
what
you're
saying
Laurie,
and
that
makes
a
lot
of
sense
in
in
the
password
it
wasn't.
Our
issues
were
not
open
to
the
community,
but
I
think
our
develop
our
engineers
here
at
gate
lab
get
a.
They
do,
get
a
lot
of
interaction
with
the
end
user,
because
I
see
their
conversations
on
the
issues
with
our
community.
So
I
disagree
that
they
are
out
of
touch
with
the
users
of
the
things
they're
developing
for
they're,
very
actively
engaged
in
conversation
with
them,
but
but
you're
right.
B
A
Well,
I
would
tell
them
the
same
thing.
I
would
tell
you
like
if
you
have
questions
for
this
person
just
put
in
the
slap
and
I'll
ask
them
for
them,
and
then,
at
the
end
of
the
session,
we
can
open
it
up
and
have
a
conversation
with
the
person
we
have
time,
but
that
that's
usually
how
I
handle
it
with
Amy.
If
is
a
CTO
who's
coming
in
to
watch
or
whoever
they
send
me,
the
questions
and
I'll
ask
them,
so
they
can
get
their
questions
answered.
Oh
I,.
D
A
A
So
that's
why
I
typically
tell
people
to
send
me
your
questions
through
slack
I'll
work
them
in
as
part
of
a
conversation
and
then,
if
there
is
time
at
the
end,
I'll
actually
verbally
open
it
up
in
the
session
to
say
you
know
John,
do
you
have
any
questions
for
Charles
who
we're
talking
to
today
them
and
then
they
can
ask
additional
questions.
We
have
time.
Yeah
I,
think
we
get
it
I
totally
gave
case.
Of
course
everybody
that's
right,
everybody's
questions,
so.
B
B
I
said
what
don't
have
me
in
the
session
if
I
can't
be
verbally
engaged
with
with
the
interview
process,
so
we
totally
open
to
inviting
them
as
optional,
just
be
prepared
to
hurt
cats
and
be
understanding
if
you
want
to
unmute
and
engage
directly
because
because
if
they
feel
like,
if
you're
gonna
take
their
time
and
involve
them
in
a
session,
they
want
that
that
real-time
verbal
be
part
of
the
conversation.
They
don't
send
that
it's
not
a
conversation,
yeah
right
right,
hey.
D
A
quick,
quick
request
in
between
this
conversation,
because
I
sent
a
link
of
the
current
agenda
after
day
and
I
would
I
would
appreciate
if
we
go
forward,
I'll
try
to
die
to
take
notes,
and
it's
at
least
because
I
know
where
we
are
you
Jenna,
curtly
or
not.
You
know
recording
any
of
the
things
we
actually
discuss
and
feel
like.
We
can
be
more
effective
if
that's
always,
if
you
actually
all
try
to
take
these
notes
as
we
go
and
then
why
you
can
read
back.
If
we
forget
a.
C
D
C
D
Is
not
included
for
today's
meeting.
It's
wait.
Wait
lunch,
wait
what
I'm
you
can
actually
discuss
I
feel
like
for
today,
but
that
was
the
agenda
and
I
think
we
have
discussed
so
many
like
great
things.
I
cannot
relate
back
to
it,
except
from
Washington
recording,
which
is
inefficient,
I'd,
say
yeah.
B
B
C
D
Okay,
I'll
create
a
new
document
after
this
meeting
and
I'll
copy
over
this
last
content
into
that,
or,
as
you
wanted
to
write
up
some
notes.
Tau
V
feel
that,
like
I
can
do
that
right
after
this
meeting-
and
you
know,
give
you
a
message
on
slack,
but
you
know
I'm
fine
with
drainage.
Any
topic
like
this,
because
I
feel
that
the
agenda
item
for
this
being
is
also
created
by
me.
So
I
can
easily
updated.
Don't
ever
one
is
able
to.
B
D
I
would
even
say
that
you
know,
as
as
as
long
as
the
direction
is
sound
for
CI.
We
can
even
use
part
of
this
meeting
to
collaborate
and
say
all
right.
Well,
what
is
on
your
mind
for
the
next,
like
the
epics,
we're
going
to
schedule
a
and
then
I
think
we
all
available
feedback
to
give
you
an
alkene
to
setting
like
creating
that
the
epics
needed,
but,
yes
for
sure
one
or
two
bigs
that
you
know
your
we
want
you
to
want
to
dedicate
to
regardless
is
a
good
idea
and
one
of
the
epics.
D
But
what
I
wanted
to
say,
like
whatever
my
main
point
here,
is
that,
like
the
direction
page,
yes
should
be
managed
by
Pam,
but
I
would
say
it
is
not
a
one-way
street
of
the
direction
page
influencing
this.
This
meeting
thing
Bay.
It
should
be
a
two-way
street,
where
our
discussions
in
our
think
big
session
actually
have
an
impact
on
the
category
vision
page
for
a
CI.
In
that
way,
you
know
have
a
collaborative
direction
set
up
to
some
extent.
Yeah.
B
B
But
but
then
that
leads
me
to
if,
if
this
this
time,
this
recurring
meeting
session
time
is
for
the
bigger
group
session,
that
means
I
want
to
understand
when
we
would
meet
just
UX
and
p.m.
to
strategize
of
some
of
the
things
that
doesn't
belong
in
a
think.
Big
session
with
the
entire
team
is
the
intent
that
we
would
use
our
just
our
weekly
Tuesday
meeting
series.
B
Part
of
it
is
for
grooming,
but
part
of
it
is
also
for
planning,
think
big
sessions
so,
for
example,
before
I
think
big
meeting
with
our
entire
team
I
at
that
meeting,
rather
than
go
through
just
reviewing
all
the
current
milestone.
I
would
probably
want
to
start
it
off
by
saying
this
is
this:
is
this
is
an
opportunity,
canvas
that
I've
been
working?
You
know
UX
and
p.m.
on,
and
it's
gonna
drive
this
session,
because
there
is
a
big
topic
out
of
this.
That
we
want
to
dedicate
this
think
big
session
to.
B
D
B
D
Ux
we
can,
if
we
want
to
dilute
that
to
some
extent
and
include
something
big.
You
know
trades
into
that,
meaning
that
it
that
it
should
be
a
conscious
decision
of
merrily
it's
because
then
we're
watering
down
what
the
exact
definition
of
that
meeting
is
versus
this
meeting.
We
don't
want
to
have
two
meetings,
that
kind
of
discussed
the
same
things
right,
yeah
and
I.
Don't
want.
D
That
is
something
else
I
believe
they
have
a
slightly
smaller
team,
but
I'm,
not
sure
exactly
but
I
would
say
they're
a
little
bit
further
into
the
process
and
perhaps
some
things
work
for
them
in
some
dome.
We
can
only
assume
what
how
it's
going
to
work
for
us
at
this
moment,
so
I
propose
to
just
experiment
to
Songshan.
Sorry
what.
C
C
D
B
Yeah
and
actually
the
CIT
meeting
yeah
and
that's
why
I
hesitate
to
have
them
join
more
meetings,
but
actually
the
the
CIT
meeting
is.
Is
it's
almost
like
a
weekly
stand-up
because
they
talked
through?
Are
there
anything
at
risk
now?
Are
there
any
questions?
They
don't
think
crystal.
Tells
me
she's
trying
not
to
have
that
be
a
grooming
meeting,
because
it's
only
30
minutes
but
her
her
agenda,
for
that
is
very
specific
of
talking
through
the
current
work.
B
If
there
are
any
deliverables
at
risk,
is
the
the
main
topic
of
that
meeting
yeah.
Unfortunately,
when
they
talk
about
things
on
that
topic
of
what
might
be
at
risk,
the
conversation
will
come
up.
We
we
found
we're
a
little
we're
at
an
impasse
on
a
particular
issue,
because
there's
different
ways
of
handling
this
implementation,
that
has
questions
for
UX
and
for
front-end,
and
then
it
becomes
a
slight
discussion
to
groom
out
what
the
proposal,
what
the
implementation
will
be:
mm-hmm
yeah
yeah.
C
C
Talking
about
the
thing
peak,
because
looking
at
the
activity
and
interest
of
engineering
on
the
package
team
in
the
strategy,
discussion
and
the
level
of
participation
in
the
user,
research,
discussion,
I'm
surprised
and
maybe
we
would
be
same
lucky,
maybe
engineering
in
our
group
would
be
reacting
to
the
differently,
but
maybe
I
would
even
suggest,
like
you
know,
yeah
Leslie,
let's,
let's
invite
them,
let's
try
the
sessions
and
we
can
always
like
quite
quickly
do
a
small
retrospective
check
in
and
see.
Do
they
find
this
interesting?
Is
it
useful?
D
Originally
is
yes,
we
just
didn't.
Do
it
yet
and
I
feel
that
fully
grooming,
the
UX
p.m.
grooming
session
there
is
not
yet
that
that
request,
though
I
wonder
what
package
does
for
that,
because
I
believe
they
do
mean
to
can
find
engineering
to
that
one
as
well,
but
like
the
current
occurred.
The
current
point
where
we
are
at
is
that
we
have
a
weekly
CI
stand
up
team
meeting,
which
is
on
Tuesday,
and
we
have
the
UX
p.m.
grooming
meeting.
D
Also
on
Tuesday,
then
we
have
a
Wednesday
grooming
engineering,
back-end
meeting
I,
don't
know
if
there's
also
a
front-end
engineering
grooming
meeting
separate
to
that,
then
we
have
this
thing
big
session
and
we
all
want
to
be
everywhere
at
all
the
time.
So
we
have
four
meetings
in
or
even
more
in
one
week
every
week
and
I
feel
we're
doing
double
double
duties
somewhere.
D
That
might
not
be
a
super
problem
for
now,
but
I
would
say
that
we
need
to
think
that,
if
we're,
including
engineering
to
some
of
these
meetings,
perhaps
we
can
lose
one
of
those
meetings
instead
and
you
know
create
free
time
and
and
but
we
we
should
be
clear
with
the
exact
outcomes
of
those
meetings.
We
need
to
be
clear
on
the
agenda.
We
need
to
be
clear
on
what
a
pool
is
who
and
could
we
prepare
for
those
meetings
right
and
I
understand?
D
There
might
be
some
additional
meetings
always
needed,
but
I
would
say
that
you
know
that
seemed
to
change
it
with
us
move
a
little
bit
more
towards
sink
nasty
in
our
communication.
With
these
meetings,
we
need
to
watch
out
that
we
do
not
fill
our
agenda
unnecessarily
with
with
additional
meetings
like
it's
fine,
but
like,
let's
see
how
we
can
optimize
as
well
after
we've
settled
in
on,
like
the
exact
contents,
we
need
to
discuss.
Does
that
sound,
logical
right?
So.
B
Right
now,
only
Dimitri
and
I
are
the
ones
that
are
at
all
four
of
these
on
a
weekly
basis,
and
so
when
you
propose
Nadia
that
including-
and
we
can
invite
them
optionally
but
we've
real
reached
a
point
where
they
may
be
overwhelmed
by
the
number
of
meetings
and
mean
Dimitri's
right
like
what
I
say
right
now,
I,
don't
think
anyone
is
aware
of
how
much
is
bandwidth
is
consumed
in
this
meeting
except
Dimitri.
Now,
because
we
are
at
all
four
of
them
every
week
right.
C
Yeah
and
a
good
point
Dimitri
and
why
I
mentioned
the
previous.
A
comment
is
because
I
thought
we
kind
of
like
started
discussing
you
know
like:
where
are
we
gonna
discuss
that
UX
p.m.
related
stuff?
So
maybe
I
just
misunderstood
the
comment
but
yeah-
and
this
is
a
good
point
about
meetings
being
overwhelming
yeah
I'm,
not
sure
how
many
are
there.
So
it's
a
bit
hard
to
judge
but
yeah
I
think
at
some
point
you
can
just
try
and
then
run
the
crib
chicken
after
a
week
or
two
weeks,
yeah.
D
I
think
the
big
difference
between
package
and
see
is
that
package
is
kind
of
like
set
up
as
a
new
team.
Just
they
started
out
from
nothing
and
set.
You
know.
Creative
things,
ci
has
a
lot
of
baggage
from
the
past
and
you
take
meetings
and
everything
there
forever
and
just
continue
doing
them
without
much
regard.
So
I
think
we
have
a
little
bit
of
an
extra
challenge
here.
B
D
A
C
B
The
grooming
meetings,
the
so
our
UX
going
meeting
on
Tuesday
is
for
things
in
the
very
immediate
or
current
milestone
or
immediate
future
next
milestone,
which
I
agree
that
you
meet
you
Luke.
We
don't
want
to
dilute
that
with
discussions
preparations
before
a
big
session
and
then
the
engineering
is
to
recurring
meetings
also
is
distinct.
One
is
for
a
very
immediate
milestone.
Work
in
flight
discussion
and
the
other
one
is
grooming
for
future
things,
and
then
the
thing
I
think
maybe
what
we
can
do
as
a
compromise.
B
Which
brings
me
back
to
that
that
there
is
still
a
need.
In
my
past
experience
was
working
with
with
UX,
both
researcher
and
designer
that
there
still
needs
to
be
a
separate
weekly
meeting
for
PM
to
sync
up
with
their
counterparts
on
the
UX
team
for
the
given
product
area,
because
we
would
be
doing
because,
like
engineers
get
their
implementation
issue
and
they
they
talk
amongst
themselves,
you
know
to
kind
of
solution
stuff,
which
maybe
involves
their
am.
It
involves
other
engineers.
D
Cancel
anything
right
now,
but
I
would
say:
let's,
let's
get
a
little
bit
more
stable
ground
or
a
feet
with
their.
You
know,
coming
weeks
and
and
look
from
there
as
to
like
hey,
can
we
reduce
or
optimize
or
no
is
this
meeting
needed
like,
for
example,
that
meeting
yesterday
with
engineering
we
thought
it
was
gonna
be
about
I
was
going
to
go
into
all
the
time,
but
it
wasn't
goodbye.
D
So
I
would
say,
like
there's,
there's
some
miscommunication
there
as
to
like
what
is
the
real
intent
with
that
meaning
is
there
like?
This
are
now
gonna
be
another
meeting
where
like
where,
like
that
aligns
with
the
original
intent,
we
have
four
photos
for
that
meeting:
I'm
unsure
to
be
honest,
yeah.