►
From YouTube: CI/CD UX/PM Grooming meeting 2019-12-10
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
About
well,
it's
a
big
customer
because
they,
the
am
told
me
it
was
twenty
thousand
licenses.
So
I
think
this
is
a
sizable
customer
and
they
wanted
the
feature.
That's
mentioned
there
that
I
mentioned
in
one
of
the
agenda
issue.
Three,
eight
one,
four
one.
Basically,
when
they
rebase
a
large
monolith,
mono
repo,
they
did
not
want
it
to
trigger
the
CI
pipelines,
because
that
could
run
forever
and
a
lot
of
different
teams
are
rebasing
frequently
and
they
wanted
a
way
to
inject
a
CI
skip.
A
Parameter
so
we're
asked
to
respond
to
that
customer
need
by
8:00
a.m.
Pacific
time
today.
So
that's
why
I
had
the
engineers
look
at
it
and
then
I
realized
that
the
issue
itself
is
specific
to
the
changes
to
the
API
on
rebase,
but
I
was
afraid
they
would
say
what
if
we
wanted,
how
would
we
specify
this
in
the
UI
and
then
I
realized
I
need
to
you
Dimitri
to
give
input
on
what
that
change
could
be,
and
how
high
up
sizable
that
effort
is
so
thanks
for
your
come
in
the
issuer's
yeah.
B
To
arrive
at
the
final
output
there
I
need
some
additional
context
because
they
say
like
alright.
You
need
to
rebase
want
to
give
you
another
option
to
use
it,
but
I
want
to
kind
of
like
I
want
to
know
where
the
trigger
for
the
rebase
is
going
to
be.
Is
it
only
going
to
be
through?
You
know?
The
web
UI
I
know
it's
going
to
be
in
addition
to
the
API,
but
how
is
that
they
are
you
gonna
be
triggered.
It's
only
gonna
be
free
web
UI,
or
it's
also
going
to
be
additional
options.
B
For
example,
some
kind
of
like
a
gitlab
command
line
interface
that
you
know
allows
you
to
rebase
merge,
requests
in
a
different
way,
so
I'll
need
some
feedback,
and
probably
mafia
is
able
to
give
that
and
based
on
that
I
will
walk
through
the
user
flow
once
again
and
then
you
might
be
my
final
proposal.
I
expect
like
not-not-not
something
too
large
and.
A
A
So
we
will
groom
it
and
get
your
questions
answered
Dmitry,
but
since
I
was
asked
to
what
what
I'm
being
asked
to
decide
so
that
that
that
meaning,
the
aims
can
communicate
to
the
customer
is,
can
we
deliver
this
in
January,
which
would
be
the
next
release,
putting
it
into
12.7
and
I?
Wanted
the
team
to
weigh
in
to
tell
me
this
is
enormous.
A
We
could
never
finish
this
in
one
milestone
or
it's
possible,
but
there's
a
lot
of
different
ways
to
tackle
this,
including
some
UI
enhancements,
so
I'm,
getting
the
feeling
that
I
can
say
we
can't
deliver
it
in
12.7,
but
after
grooming
tomorrow,
I'll
know
the
true
weight
of
it
and
the
complexity
of
a
tentative
technical
approach,
including
back
in
and
front
end
changes
and
and
and
you
exchanges
UI
changes,
because
that
determines
how
many
other
direction
issues
might
make
it
in,
but
at
least
I
know.
This
is
not
going
to
span
multiple
milestones.
B
B
B
A
Okay
and
I
made
a
note
so
yeah,
so
the
the
team
is
also
having
discussions
in
the
thread
that
Fabio
created
that
says
continued
conversation
in
this
thread
this
morning.
So
you
can
follow
that
as
well,
but
I
think
we'll
get
a
lot
more
understanding
at
tomorrow's
blooming,
but
but
based
on
their
engineers
discussion
and
then
your
assessment
Dmitry.
It
lets
me
move
forward
of
saying:
yes,
if
they
be
delivered
one
milestone
and
most
likely
to
your.
B
B
These
are
the
important
issues
we
need
to
focus
on,
because
we
might
reach
a
point
where
I'm
not
able
to
support
all
issues
that
include
you
know,
UX
and
I
will
need
to
be
able
to
see
now.
Alright,
these
are
really
important
and
they
have
a
high
probability
of
getting
into
the
actual
milestone
being
assigned
deliverable
label.
B
And
these
are,
you
know,
gonna,
be
less
important
or
will
probably
not
even
make
it,
even
though
there
have
been
assigned
a
certain
milestone
as
a
you
know
like
with
the
assumption
they
might
make
the
future
milestone
and
sorry,
and
the
last
thing
to
that
is
engineering.
Ideation
feedback
available
evidence
that
so
perhaps
that
tooth
long
way
of
saying
basically
I
you'll
need
to
educated
engineering
support
of
issues
before
they
will
get
assigned
a
deliverable
label.
I've
been
asking
the
engineering
managers
today
to
say,
hey
or
will
be
my
engineering
counterparts
to
do.
B
B
It
was,
is
it's
kind
of
similar
to
the
thing
we
discussed
for
the
expiration
only
dedicated
you
know,
engineering
supports
you
know
id8
alongside
with
and
get
feedback
from,
as
you
know,
as
we
go
through
iterations
of
the
design
concept,
so
I
was
mostly
thinking
about
like
how
do
you
think
about
that?
Perhaps
first,
let's
focus
on
deliverable
status,
and
then
we
focus
on
the.
A
Yes,
I,
okay,
so
crystal
and
I
talked
about
something
on
Friday
and
I
want
to
show
it
to
you
all
that
I
need
to
create
for
12.7
to
test
it
out
will
just
start
using
intro
at
seven
and
then
going
forward
to
answer
your
question
about
keeping
on
top
of
dates
and
also
when
the
the
issues
will
be
given
the
the
workflow.
The
deliverable
label
need
a
minute.
A
Actually
different,
the
ready
for
dev
and
in
dev
the
deliverable
label
is
at
the
beginning,
even
before
the
milestone
starts,
to
indicate
that
the
engineering
team,
both
front-end
and
back-end,
has
agreed
to
commit
to
this
for
the
given
milestone
and
then
the
actually
workflow
label
for
ready
forever
in
dev
indicates
where
they
are
in
the
implementation
during
the
milestone,
but
but
none
of
those
even
have
it
even
before
I
get
to
that
state
up.
Those
were
full
workflow
labels.
It
has
to
have
a
deliverable
label.
A
It
gives
me
it
gives
engineering
a
way
of
saying,
although
the
product
manager
gives
us
this
list
of
proposed
issues
for
candidates
for
the
milestone,
these
are
the
only
ones
in
engineering
agrees
that
they
can
deliver.
So
that's
what
their
deliverable
labels
is
intended
for
anything
I'm
trying
to
find
Kristin
the
Bangko
I
did
awesome
here.
It
is
ok,
so
let
me
show
you
all
a
couple
things
that
I'm
going
to
try
to
start
doing
in
order
to
assure
my
screen,
Isis.
A
A
I
have
too
many
things
going
on
here
and
this
one
okay,
so
there's
three
things:
one
thing
is
Kristin:
one
of
the
PM's
has
created
this
product
development
timeline,
calendar
public
calendar
that
users
can
subscribe
to
and
what
it,
if
you,
if
you
remove
all
of
your
your
own
calendar
even
and
you
go
to
the
month
view,
you
can
see
that
she
has
illustrated
in
the
Google
Calendar,
where
we
are
for
both
the
future.
The
next
milestone
and
the
current
milestone.
A
So
to
answer
your
question
of
when
the
deliverable
label
gets
added,
Demetri
is
on
the
last
day
of
this
phase.
For
so
12ax7
is
the
next
milestone,
that's
icon.
She
has
for
writing.
She
uses
for
whenever
there's
a
draft
activity,
that's
going
on
in
this
case
product
is
dropping
the
release
scope
which,
if
you
click
on
it,
it'll
give
you
the
description
that
this
is
when
the
liberal
label
deliverable
is
applied.
Release
cope
is
finalized.
So
this
is
when
all
of
the
discussion
with
engineering
and
p.m.
I'll
look,
the
grooming
happens
and
UX
right.
A
Kickoff
document
is
updated
with
relevant
I.
She
got
this
description
directly
from.
If
you
go
to
the
product
timeline,
handbook
page
I
think
she's
pulling
them
out
of
here
so,
but
then
the
on
the
very
last
day
of
a
multi-day
activity.
She
has
that
same
thing
with
a
a
checkbox
emoji
to
say
that
this
is
that
very
this
is
like
when
things
are
finalized.
So
you
can
use
this.
A
You
can
subscribe
to
this
product
development
timeline
to
get
a
bird's-eye
view
of
what's
happening
in
the
month,
for
both
the
current
milestone,
which
is
12.5,
I'm,
sorry,
12.6
and
then
the
future
112
that
seven.
So
hopefully
that's
helpful,
I,
don't
know
I,
think
she's
done
this
for
yeah
into
the
new
year.
Okay,
so
that's.
A
It's
very
nice
that
and
kudos
to
her
and
Chara.
Thank
you.
She
she
mentioned
it
to
the
P
in
the
product,
Channel
I
believe,
but
I
don't
know
that
she
necessarily
broadly
shared
it.
In
fact,
I
googled
it
she
mentioned
it
in
yeah
at
the
product
channel
when
she
created
it
last
month.
Okay,
so
that's
one
thing:
that'll
help
us
go
ahead
and
go
add
that
to
your
calendars
description,
the
other
thing
is:
I
talked
to
Gabe
Gabe
Weaver,
who
is
another
product
manager
for
I,
think
the
plan
stage
and
what
he
does.
A
This
is
the
one
for
12.6.
He
has
this
issue.
He
creates
a
new
one
for
each
release,
his
cap,
his
his
stages
plan
and
then
what
he
does
in
there
is.
Not
only
does
he
link
to
the
kickoff
video
that
all
PM's
and
clean
himself
record
by
the
17th
of
every
month
that
is
uploaded
to
get
lab
unfiltered.
He
calls
out
what
is
features
to
be
implemented
based
on
what
eventually
engineering
agreed
to
for.
A
He
first
does
a
draft
of
this
of
everything
he
proposed
and
then
he
updates
them
based
on
discussions
he
has
with
both
in
the
grooming
session
and
in
the
actual
issue
itself
from
input
from
the
engineers
and
then
he'll
keep
updating
this
until
it's
finalized
I.
Guess
he
closed
it
out
even
before
the
releases
is
closed
out.
You.
B
D
B
A
It's
yeah,
it's
so
ever-changing
that
she
said
if
she
could
just
have
one
snapshot
of
what
we
had
planned
for
the
release.
This
actually
serves
her
purpose
for
that,
and
so
I
do
like
that.
He
calls
out
the
design
priorities,
because
you
know
some
of
the
things
that
you're
working
on
on
the
validation
board.
A
The
engineers
don't
necessarily
go
visit
that,
but
this
gives
them
an
idea
of
a
bulleted
list
of
the
things
that
UX
researcher
or
our
product
designer
is
gonna,
be
focusing
on
in
the
given
milestone,
because
you
know
all
the
stuff
you
work
on
a
lot
of
it
is
in
the
validation
board.
It's
not
in
the
bill,
milestone
tracking
board.
A
Now
he
does
something
that
I'm
not
going
to
do.
This
is
one
issue
across
the
entire
stage
for
plans,
so
it
has
his
four
for
planned
project
management
and
it
has
portfolio
management,
which
is
this
other
PM.
If
I
were
to
do
something
like
this,
it
would
be
one
for
verify
and
then
Miley,
PCI,
tau,
runner,
Darren
and
testing
James,
but
I
don't
know
if
they
want
to
do
that.
But
I
think
for
crystal
being
very
new.
That's
funny
that
you
told
me
that
they
used
to
do
this.
A
She
finds
it
useful,
so
I'm
gonna
try
to
do
this,
but
one
thing
I'm
gonna,
add
to
this.
So
I'm
gonna
change
it
up.
Ours
will
only
be
specifically
verify
CI
and
so
it'll
it'll
cut
off.
You
know
it
won't
be
it's
long.
A
description,
but
Kristen
does
something
similar
for
hers.
She
doesn't
issue,
but
she
has
all
of
these
Quick
Links
to
filtered
views
of
the
board
and
I'm,
not
too
crazy
about
that.
A
A
A
Yeah,
and
and
because,
with
the
with
the
calendar
view,
if
you
have
all
your
other
stuff
in
there,
it's
really
busy.
You
talk
to
unclick
everything,
but
at
least
this
this
is
the
clean
and
again
she
uses
the
same
icon.
She
because
she's
this
this
P
Amazon,
who
also
created
the
calendar,
the
public
calendar
for
timeline.
A
B
This
this
current
calendar,
it
seems
very
much
geared
at
the
build
track
right.
It
has
to
have
product.
Benjamin,
you
know,
makes
it
ready
for
the
build
tracks.
You
know
to
get
that
running.
How
would
you
feel
about
me
creating
a
counterpart
with
that?
It
came
towards
the
validation
track
and
see.
If
we
can,
you
know
need
to
shift
things
around
a
little
in
order
to
know
or
get
an
ideal
state
of
things.
A
A
E
Yeah,
you
know
actually
I
was
I
already
started,
something
like
that
for,
like
the
general,
like
the
UX
time
line
where,
because
this
one
is
more
like
engineering
focus,
the
product
development
timeline
and
we
don't
have
one
for
the
UX,
which
is
doing
research
as
well
and
validation,
yeah,
yeah
I
would
love
to
pair
up
on
that.
I
have
started
that
thing,
but
I
dropped
it
because
you
did
the
other
priorities
for
now,
but
I
have
planned
to
come
back
to
that.
Yeah.
B
We
used
to
have
some
kind
of
like
a
timeline
dedicated
towards
design,
but
I
would
say
so.
I
was
looking
for
the
page,
but
I
cannot
find
it
quick
enough
for
this
meeting,
but
I
can
place
it
in
later
if
I
find
it,
but
that
doesn't
like
I
think
that
timeline
wasn't
yet
timeline
and
could
use
some
adjustment
also.
The
way
it
was
visualized
was
quite
confusing
to
some
extent
so
yeah
I
would
I
would
like
to
do
so.
If
I'm,
if
I'm
understanding
this
correctly
Nadia
B.
B
E
E
A
A
So
so
that's
the
direct
answer
to
your
question.
Demetri
now
I
just
so
you
know,
because
the
milestone
12.7
includes
a
lot
of
days
out
of
the
office
for
team
members.
It's
I'm
going
to
be
very,
very
conservative,
of
what
issues
I
even
proposed
to
them.
I
was
actually
supposed
to
pass
that
through
yesterday,
but
I
I'm
a
little
prepping
for
end
of
12.6
work.
That
is
due.
A
So
my
guess
is
there
be
very
little
that's
committed
to
for
12.7,
simply
because
I'm
going
to
be
out
for
I
asked
crystal
generally
what
the
team
plans
war
for
out
of
office
or
vacation
PTO
and
at
any
one
time
there
will
be
one
developer
active,
but
some
are
taking
two
weeks
and
then
there's
they're
stacking
them.
So
there's
always
one
or
two
developer,
but
not
the
full
team
for
full
capacity.
B
A
B
So
I
asked
this
question
inside
of
slacks,
because
it's
if
I
look
at
next
week,
the
CIT
meeting
is
when,
on
Tuesday
like
normal
and
I,
asked
him
slack
and
I.
Don't
know
if
I
got
an
answer.
Yes,
no,
like
isn't
gonna,
be
moved
by
default
to
the
Thursday,
but
it
seems
to
be
currently
still
only
for
this
week.
B
A
I,
don't
think
that
was
intended
unless
Christian
only
wanted
to
try
it
out
this
week
to
get
feedback.
I
think
was
intended
to
always
move
earlier
in
the
day,
but
they
had
conflicts,
leaving
it
on
Tuesday,
because
she
was
the
problem.
Is
this
the
time
difference
between
where
crystals
located
in
US
Pacific
time
and
for
Kong
in
Russia
is
so
vast
that
no
time
works
for
them?
So
the
original
time
was
8
p.m.
A
B
B
F
B
F
A
But
but
I
was
gonna
mention
at
the
team
meeting
hey.
These
are
proposed
issues
that
you
can
go
ahead
and
go
evaluate
async,
because
this
is
the
week
for
the
engineering
team
to
do
some
grooming
of
the
stories,
and
it
doesn't
only
happen
in
the
grooming
meeting
the
Boomer
meetings
for
when
I
think
things
that
need
further
discussion.
We
would
never
get
through
all
of
them
if
they
didn't
do
some
of
it.
A
Asynchrony
a
synchronously
this
week,
but
I'll
ask
I'll
message
in
the
G
underscore
CI
slack
Channel
that
the
issues
you
know
these
are
the
issues
on
proposing
12ax7
go
ahead
and
start
asynchronously
reviewing
them
and
then,
whatever
in
these
discussion,
will
cover
in
the
Wednesday
me
yeah.
It
would
be
nice
to
kick.
A
A
B
So
I
mean
that's
that's
even
that
gives
even
more
urgency
to
that.
We
need
to
like
start
working
on
12
8
as
soon
as
possible
mm-hmm,
and
we
need
to
have
a
like.
We
should
almost
be
at
this
point,
but
while
are
they
as
soon
as
possible?
To
you
know,
have
that
kind
of,
like
three
three
weeks
of
ideation
time
to
really
discuss
thoroughly
with
with
engineering
and
and
you
had
some
p.m.
to
go
through
those
ideation
iterations
and
I
will
need
to
provide
from
12
a
day.
So
the.
B
A
If,
if
product,
if
I'm
supposed
to
be
drafting
the
issues
based
on
what
comes
out
of
your
research,
if
this
product
draft,
but
really
it's
it's,
you
and
me
getting
these
issues,
if
we
have
we're
supposed
to
start
as
early
as
the
4th
of
January,
then
you're
right
backing
it
up
the
research.
You
know
that
needs
to
be
completed
before
that
on
January
3rd
yeah,
so
someday.
Well,
we
have
a
calendar
view
of
validation
timelines,
so.
A
B
Would
you
consider
that,
like
the
issues
like
like,
let's,
let's
think
about
this
way,
if
this
is
the
case,
then
that
means
that
we
have
from
the
ninth
until
the
13th
again
similar
to
this
one,
to
work
on
any
issues
that
we're
dedicated
to
from
both
engineering
and
UX
to
arrive
at
a
solution
that
needs
to
you
know:
go
into
the
build
track
at
the
18th
yester.
That
is
one
two
three
four
five
days,
five.
A
B
Ideation
and
going
three
iterations
where
we
throw
away
the
entire
rest
of
the
month
right,
wouldn't
it
be
like
shift
this
back
to
two
weeks,
and
that
would
be
the
correct,
correct
date
for
product
to
have
a
draft
of
the
next
milestone.
I
think
the
fourth
of
January
is
far
too
late
for
me
and
for
engineering
to
also
know
like
all
right.
When
are
we
going
to
start?
You
know
having
the
workflow
design
label
assigned
to
for
12.
A
date
like
the
fourth
is
I
would
say
is
not
considering
the
validation
track.
B
A
B
This
is
this
is
where
I
think
that
we're
misaligned
between
product
and
us,
because
those
technical
discussions
that
is
part
of
the
validation
track
to
some
extent
like
we
should
have
figured
out
like
we
should
be
I
da
ting,
together
with
engineering
to
get
to
that
state.
So
the
issues
we
want
to
get
into
12
a
it
should
be
known
like
at
least
two
weeks
earlier
than
the
fourth
of
January.
You.
A
A
E
Should
be
ready
before
divorce
I
feel
like
we
like,
if
you
would
ask
me,
I
think
we
could
even
start
like
two
milestones
ago.
If
we
want
to,
for
example,
in
release,
there
are
some
issues
that
are
designed
well
ahead.
You
know,
like
just
in
case,
for
example,
one
might
feel
like
he
has
some
time.
He
goes
and
like
designs,
a
proposal
and
then
as
closer.
E
It
goes
to
the
actual,
like
planning
of
the
work
they're,
just
refining
that
so,
if
there
is
no
start
date,
there
is
the
end
date
and
I
sell
houses
before
fours.
It
has
to
be
done,
and
so
that
engineering
can
do
the
planning
properly
and
it's
an
estimation,
okay,
yeah.
Well.
The
next
engineer
has
to
be
involved
before
but
kind
of
like
before
that
it
has
to
be
done.
I
feel
like.
B
B
E
A
particular
example
that
I'm
talking
about
there
would
be
the
recommendations
for
the
Jets
in
case
she's,
not
so
case.
You,
you
access
square
card
and
he
and
read
prioritized
some
of
those
four
twelve
seven,
some
of
those
four
twelve
eight,
and
it
has
a
part
of
like
one
big
solution
produced
design
mock-ups
and
he
attached
that
to
those
issues.
So
right
now
for
twelve,
eight,
for
example,
we
are
doing
eight
like
it
feels
like
there
is
a
big
part
of
work
already
designed.
Of
course,
is
it
final?
E
No,
but
it's
like
a
lot
of
them.
Work
is
produced
and
ready
out
for
discussion
and
further
clarification.
So,
for
example,
if
tower
knows
that
this
and
this-
and
this
feature
will
go
somewhere
soon
like
involve
a
12-7
into
the
production
like
we
can.
If
you
have
time,
I
feel
like
we
can
go
ahead
and
start
like
validating,
brainstorming,
ideation
and
producing
designs,
and
attaching
that
there
and
as
closer
we
go
to
this
force,
the
more
certain
the
work
has
to
become
yeah.
B
A
Though,
if
I
would
just
I
just
created
a
calendar,
that
is
just
a
work
in
progress
calendar.
So
if
we
said
12.8,
if
on
the
4th
of
January,
we
product
would
start
drafting
the
issues
and
it's
based
on
the
validation
track.
Would
we
say
five
days
before
that
would
be
the
solution?
Validation,
I'm,
just
gonna
play
with
this,
or
even
more
days
before
that,
like.
B
Venice
Venice
up
to
two.
What
kind
of
issue
it
is
but
I
mean
five
days
of
ideation
is
not
play.
It
depends
right,
like
a
UX
research
method
like
if
we
go
full-scale
use
research
that
takes
one
and
a
half
months,
so
five
issues
wouldn't
cut
it
there
I
would
say
for
a
proper.
Let
me
see
because
I
took
notes
of
this
for
myself.
Let
me
see
what
I
wrote
down
there.
B
Ideation
issues,
so,
let's,
let's
say
at
least
three
weeks,
would
be
ideal
right.
So
we
have
three
weeks
to
discuss
asynchronously
with
engineering
and
product
management
counterparts
to
discuss
through,
for
example,
exploration
for
to
move
forward
with
that
and
then
eventually
from
the
fourth
till
the
eighth,
you
would
arrive
in
to
individual
issues
from
that
from
those
efforts
before
that,
like
notice,
the
planning
write
down
basically
so.
E
You
know
yeah,
you
know,
I,
think
that's
what
that's
okay,
why
I'm
puzzled
a
little
bit
is
like
I
was
always
struggling
with
putting
like
yeah
you
ax
work
into
them
like
strict
timelines
and
saying
hey.
This
is
that
thing
that
applies
for
every
single
case,
because
I
feel
like
we
design
it
very
well.
Creative
creatures,
as
well
as
the
researchers
I,
feel
like.
Sometimes
it's
just
hard
to
push
those
thing
into
those
like
boundaries
and
yeah
in
general.
E
E
D
A
We're
yes,
I,
agree
so
I.
That's
why
I
didn't
call
out
that
specific
workflow
label
for
the
validation
track,
I,
just
it's
better,
just
to
generalize
the
issue
ideation.
But
what
this
turns
out
to
be
is
after
this
activity,
where
the
the
release
scope
is
finalized
for
the
next
milestone,
the
next
business
day.
C
B
B
Something
to
some
extent,
yes,
but
we
need
to
at
least
know
like
what
is
our
context?
What
are
we
working
for?
What
is
you
know?
What
is
the
scope
word?
We're
trying
to
get
to
eventually
have
a
little
bit
more
clarity
to
some
of
the
issues
instead
of
having
this
last
moment
kind
of
impolite
I'm
having
a
little
bit
of
a
difficult
time,
exactly
explain,
but
I
need
to
figure
this
out
a
little
bit
better.
Perhaps
I
think
this
need
to
get
my
point
across.
A
E
So
you
know
what
I
will
I
will
take
this
input
that
you
made
there
and
I
will
maybe
move
it
to
the
moral
world.
So
it's
you
know
it's
a
bit
more,
like
flexible
I,
know,
I
mean
and
then
maybe
put
my
thoughts
on
top
of
that
and
they
share
it
in
the
issue.
So
we
can
like
add
our
ideas
to
that.
I
agree
with
your
general
suggestion.
E
You
know,
I,
guess
why
I'm
kind
of
like
don't
like
this
idea
of
the
calendar
is
that
it
feels
like.
If
you
know
we
can
like.
If
looking
at
the
calendar,
we
can
only
start
brainstorming
on
the
12.8
issues
when
we
have
the
scope
ready.
So
it's
kind
of
like
really
linear
in
that
process,
which
is
not
in
reality
the
case
but
I
understand
your
your.
Your
intention
is
more
like
to
give
the
general
guideline
guideline,
but
not
like
to
fix
everyone
in
the
day,
so
that
should
work.
I
think
the
beginning
is
good
from.
A
A
A
A
A
B
We
have
some
additional
points
to
discuss,
so
let
me
see
so:
are
we
aligned
on
engineering
availability
towards
you
know
the
validation
track?
How
do
you
think
about
that?
I
created
a
merge
request
to
edit
the
product
development
workflow
to
include
that
or
just
wondering
how
you
thought
about
that?
I
still
need
for
the
exploration
issue
that
I
created.
Let
me
see
I
didn't
call
out
the
engineering
managers
directly
yet,
but
I
like
in
order
to
get
this
going.
B
I
need
to
know
who
I'm
a
believer
in
to
you
know
to
ib8
alongside
I,
want
to
make
this
a
dedicated
part
of
the
problem.
Development
workflow
I
was
discussing
this
with
Kyle
as
well
as
well
as
I,
think
being
but
I'm
not
sure,
and
they
like
at
least
Kyle
from
what
I
remember.
Very
vividly
also
indicated
that
this
is
a
missing
thing
from
the
product
development
workflow.
B
That
engineering
only
gets
included
when
the
bill
track
begins,
and
that
is
not
the
reality
of
things
and
when
we
are
expecting
engineering
to
be
included
in
the
validation
track,
it's
currently
not
official
and
is
not
regarded
to
in
terms
of
their
availability
and
official
responsibilities
towards
it.
So
I
would
like
to
make
that
the
case
and
have
them
actually
be
assigned
to
certain
issues
prior
to
the
bill
track.
B
A
general
discussion
on
the
Edit
for
the
merge
quest
that
I've
created,
so
it's
the
one
that
Hilah
highlighted
now
I
would
I
would
more
say
like
let's,
let's
review
this
asynchronously,
perhaps
but
I
would
say
the
direct
action
point
right
now
is:
do
you
agree?
I
can
ask
for
engineering
availability
on
this
exploration.
You
and
I
asked
in
slacks
I
said
in
the
GCI
issue.
I
will
copy
the
link.
E
B
B
Right
than
that
now
I'll
ask
the
engineering
managers
and
they
will
they
will
assign
someone,
but
I
want
to
have
it
preferably
I
want
not
just
like
all
right.
These
are
the
persons
you
can
talk
to
I
want
them
to
be
assigned
to
issue
that
it
is
shared
responsibility
as
like.
Hey
these
are
issues
you
will
need
to
check
upon
regularly,
because
you
know
these
are
part
of
your
responsibility
officially,
and
that
will
allow
me
to
you
know,
get
feedback
from
them
as
part
of
their
availability.
B
A
D
D
B
My
last
request
to
that
would
be
like:
can
we
push
for
this
merge
request
to
be
merged
together
because
I'm
making
a
proposal
that
will
affect
all
stage
rooms?
You
know
everything
and
I
will
need
support
from
both
product
management
and
engineering
managers
and
UX,
better
news
and
research.
The
whole
thing
that's
great.
Thank
you
so
much
yeah.
E
B
B
B
B
B
A
B
My
suggestion
here
is
like
I'm,
not
gonna
like
super
push
for
this,
but
yeah,
and
the
idea
is:
let's
innovate
like
throughout
next
week.
Let's
give
this
as
much
thought
as
possible
and
then
at
the
end
of
next
week
we
have
some
kind
of
a
draft
version
of
Twala
date
where
I
can
dedicate
myself
to
so
in
weeks.
After
you
know,
I
can
work,
alongside
with
engineering
who
also
need
to
be
assigned
to
those
issues
like
proposals
for
those
issues
agreed.
A
B
A
I
that
would
kind
of
short
changes.
I
want
to
try
this
model
I
have
a
one-on-one
with
Jason
tomorrow
and
I'm
gonna
get
some
help
from
him
on
what
he
thinks.
I
I
met
with
Camille
yesterday,
Camille
has
so
much
domain
knowledge
in
history
and
asked
the
next
important
thing
for
us
to
work
on
based
on
him
having
a
very
broad
view
every
nice
going
on,
and
he
actually
just
gave
me
some
general
ideas
on
process
improvement
with
with
keeping
engineering
accountable,
maybe
having
them
do
weekly
demos
to
UX
and
p.m.
A
but
he
didn't
have
a
clear
direction
for
me
on
his
suggestions.
So
I'm
gonna
use
my
one
and
well
adjacent
tomorrow
to
talk
about
it
and
then
my
goal
will
be
by
just
if
we
want
to
start
adopting
this
model.
Michael
will
be
by
end
of
this
week
to
have
the
things
that
I
would
want
Dimitri
for
you
to
be
starting
ish
12.8
issue
ideation
on
for
Monday
next
week.
Okay,
so.
D
B
So
if
we
go
out
from
this
model,
I
would
even
suggest
that
for
tell
them
aid,
we
are
if
we
do
at
full
scale
scale
research
we're
too
late,
like
we're
not
being
able
to
make
research
great
insides.
Thank
like
do
an
exploration
of
some
kind
of
builds,
they'll
track
issues
that
come
out
of
that
within
that
time
frame
we
have
remaining
to
get
2012
online,
I
would
say
very
feasible
and
I
would
say
strictly
the
right
moment
of
time
to
think
about
doing
actual
research.
So.
D
D
A
A
A
I,
don't
know
where
that
meeting
went
Jason
had
to
move
it
a
couple
times
God
and
the
thing
is
right
now,
unfortunately,
William
is
William.
Chia
is
spread
really
thin.
He
told
me
all
the
stuff
that
he's
working
on
so
ideally
I
would
love
to
meet
with
him
on
a
monthly
basis,
as
we
plan
out
a
milestone,
but
he
just
doesn't
have
the
bandwidth
for
that
frequency
I
see.
E
All
right,
yeah
I,
was
just
thinking
as
a
good
person
to
include
into
the
planning
as
well
like
talking
about
the
ideas
planning
for
the
milestone,
but
just
checking
alright,
so
I
have
to
run
soon,
but
basically
the
so
the
to
do
so
me
I'm,
gonna
start
this.
The
validation
timeline
I'm
going
to
share
it
with
everyone.
Now,
if
you
would
be
able
to
find
some
time
to
start
looking
into
twelve
eight,
that
would
help
everyone
I
think
we're
other
things
that
we
concluded.
That's
it.
C
B
Yeah
and
I
will
add
this
last
point
towards
the
thing
big
session
and
I
see
that
Lorri
already
moved
her
point
on
research
to
that
meeting
as
well.
So
thank
you
for
that.
Yeah
yeah,
let's,
let's
go
from
there!
I
think
this
is.
This
is
good
if
we
got
12
a
date
like
if
there's
some
kind
of
vision
on
it,
I
think
we're
gonna
be
in
a
good
spot.
Awesome.