►
From YouTube: CI/CD UX Meeting 2020-01-24
Description
By-weekly CI/CD UX Team Meeting to go over important updates, discussion items, feedback, etc.
A
Hopefully,
hopefully
you
all
have
the
same
well
give
it
a
test
right
now
and
also,
of
course,
would
be
nice
to
run
a
little
bit
of
a
retro
after
some
time
so
yeah,
maybe
I'll,
just
drop
in
to
let's
do
the
items
that
we
have
on
the
agenda
and
I
think
the
first
one
is
yeah
kind
of
like
talking
about
topics
that
are
happening
in
the
stage
groups.
What's
something
interesting
and
nice
exciting
that
you
want
to
share
about
the
stage
cool
about
your
stage,
cool
and
Ian.
You
have
a
first
item
there,
Thanks
I'm.
D
You
can
you
dive
into
a
well
before
I,
go
to
my
topic.
That
means
in
the
detail
itself
or
the
process
and
kind
of
rationale
behind
it.
I'm
really
curious
to
hear
how
you
folks
are
going
to
tackle
this
and
in
package
and
I
linked
here.
The
20/20
job
to
me
on
calendar
for
release
that
Jackie
put
together
and
I
think
would
be
awesome
to
learn
new
experience.
B
Sure
I
will
let
you
know:
okay,
currently
we're
trying
to
figure
out
and
partnering
with
Lori
about
what
the
next
Ducks
are
and
how
to
capture
that
data
effectively.
But
I
will
definitely
share
out
the
results
as
we
get
them.
A
Awesome
I
think
this
is
super
something
super
exciting
because
you
know,
as
with
was
this
with
the
direction
that
we
would
like,
you
have
showcases
and
jobs
to
be
done,
be
more
involving
than
the
real
users.
I
think
this
is
a
great
forum.
This
is
a
huge
step
towards
that.
So
would
be
really
cool
to
hear
you.
D
A
D
Oh,
my
god,
my
brains
like
like
for
the
conversation
to
be
any
it's
Friday,
so
I'm,
trying
to
read
and
trying
to
put
into
words
anyways
it
looking
to
what
other
teams
are
doing
and
also
looked
at
team
strategy
and
trying
to
identify
the
functionalities
that
overlap,
sort
of
things
that
are
common
for
you
know:
progress
of
delivery
and
raise
management,
so
the
CI
file,
settings,
environment,
etc,
and,
if
you're
curious,
to
hear
more
about.
What's
how
we've
done
it
and
also
the
release
you
axiom
strategy?
D
There's
a
merchant
class
open
yeah,
because
I
know
that
Ian
also
put
together
right
together
with
team,
a
strategy
based
in
a
very
beginning
so
yeah,
if
you
have
anything
to
share
also
from
your
experience
on
that
side,
feel
free
to
look
into
the
murder
request.
But
it's
kind
of
a
heads
up
that
if
you
have
to,
if
you're
working
with
something
specific
for
reason,
management,
that's
me
and
for
progress
and
delivery
that
will
be
Mike.
Weird.
The
assign
the
arrives
right
now.
E
E
No
I,
really
like
it's
it's
just
difficult
to
I
mean
one
of
the
big
things.
It's
meetings
right.
We
were
running
this
problem
where,
for
me,
my
entire
morning
was
blue.
I.
Think
I,
honest
tired
afternoon
was
blue,
just
doubling
up
with
PM's
and
meetings
and
things
like
that
as
a
huge
time
sink,
but
that
I
mean
that
is
what
it
is.
I,
don't
think.
That's
a
driver
decision,
I
think
really
it
didn't
day.
E
It
was
about
priorities,
you
know
and
having
to
have
two
sets
of
priorities
and
two
things
to
manage,
and
you
know
both
from
the
PM
side
right.
The
PM
had
to
have
two
sets
of
designers
that
they
were
working
with
on
initiatives
and
things
like
that,
but
also
for
high
on
I
myself.
We
had
to
work
with
two
PM's
right.
So
there's
the
the
double
priorities,
kind
of
went,
both
ways
so
I
think
just
sinking.
E
A
Cool
yeah,
so
if
anyone
will
be
interesting
to
learn
more
about
that,
follow,
Anna's
links
and
you
have
free
to
ask
questions
to
Mike
and
Rihanna
yeah
I'm,
seeing
curious
to
see
how
much
of
that
will
be
coming
in
future.
Who
knows
you
know
how
much
stages
we'll
be
splitting
and,
of
course,
a1?
If
you
have
anything
interesting
to
share
with.
G
I
mean
well
there's
nothing
like
super
major.
That
I
feel
it's
happening
like
I,
think
most
of
the
times,
I
think
because
Timmy
tree
has
been
longer
here
like
he,
many
people
buy
associated
like
pipelines
and
like
whatever
a
pipeline,
cersei
I
see
the
UX
is
happening,
they
think
about
Dimitri.
So
he
usually
like
replies
to
those
messages
like
yes,
like
could
be
a
touring
the
issues
to
get
luck.
G
He
says
like
oh,
he
seems
to
be
something,
but
it's
more
on
the
runner
or
testing
areas,
and
one
is
now
in
charge
from
that
and
then
he
attacks
me
and
then
I
chime
in
and
I
gave
my
thoughts.
No
so
and
then
I
don't
need
has
happened.
The
other
way
around
to
be
honest,
but
yeah.
That's
that's
the
mostly
the
interactions
you
know
like
the
item.
G
We,
we
don't
have
a
lot
of
cross
dependencies
right
now
like,
but
we
definitely
are
collaborating
a
couple
of
issues
of
one
is
like
I,
open,
an
issue
that
it's
gonna
fall
under
him,
which
is
like
nada.
You
were
not
for
this
meeting,
but
when
I
show
like
new
designs
for
this
screenshot
feature
that
we're
trying
to
release
and
then
we're
gonna
be
using
tabs
on
that,
and
what
we
found
out
of
that
meeting
is
that
that's
gonna
be
like
exhausting
that
pattern.
G
A
lot
to
gonna
be
like
it's
gonna
make
the
UX
not
as
good.
You
know
like
we're
already
kind
of
like
hitting
a
ceiling
with
that
fear
with
that
you
expand
on
so
what
I,
like?
That's,
probably
gonna,
fall
under
Dimitri,
but
when
I
created
the
issue
with
all
the
context
that
I
have
really
I
kind
of
like
cross-posting
the
issue
that
I'm
that
I
have
with
screenshots
on
whatever,
and
so
it's
very
informal
but
I.
Think
like
it's
more
like
a
shark
like
us,
we
work
on
things.
It's
like.
G
E
G
There
are
four
PM's
because
now
verify
these
four
groups,
so
I
interact
with
two
PM's
like
on
a
daily
basis
and
like
he
interacts
with
the
PM's
and
I
think
like
he
he's
an
interim
designer
for
that
group.
Right,
Nadia,
yeah,.
A
So
there
are
situations
like
this
in
verify.
There
are
indeed
four
groups:
continuous
integration,
the
new
templates,
the
Dimitri
is
interim
right
now
Andres
testing,
and
there
is
runner
and
for
the
custome
runner
one
is
the
product
designer
and
for
each
of
the
four
will
have
four
four
different
people
as
the
product
managers
and
yeah
I,
guess
dependable,
and
how
much
you
acts,
work
and
research
work
is
needs
to
be
needs
to
be
done
in
each
of
this
stage.
A
A
Cool
so
I
guess
that's
something
that
you
know
the
car
would
be
probably
interesting
in
the
future
to
share
as
well
experiences
or
ask
more
questions.
So,
thanks
for
sharing
one
sure,
I
see
the
challenges.
Part
in
the
agenda
is
kind
of
empty,
maybe
just
for
vocalizing.
This
question
and
anybody
struggling
with
anything
in
the
stage
group
that
you
wanna
share,
ask
for
help
or
anything.
G
I
just
put
something
there,
since
that
one
was
empty
yeah,
so
I
think
one
thing
that
I'm
trying
we
James
McKeen
in
testing
that
were
kind
of
like
we.
We
have
this
issue
that,
like
our
words,
are
very
polluted
all
issues
coming
from
many
places,
so
it
was
kind
of
hard
to
like,
like
still
like
that
into
like,
what's
happening
in
the
'quran
milestone
and
like
kinda
like
understand
how
things
are
like
going
through
the
workflow.
G
So
we
came
up
like
without
point
we're
testing
these
right
now
but
like
they
is
that
basically
we're
gonna
have
we
have
a
column
with
all
the
open
issues
right
like
usually
those
issues
are
issues
that
are
created
by
someone
like
that
in
the
past,
like
they
describe
like
a
problem
in
testing,
usually
what
we?
What
we
will
do
in
the
past
is
that
that
issue
itself
becomes
like
the
work
working
issues
like
it's
ours
moving,
so
like.
Basically,
people
like
if
this
was
created
by
a
customer.
G
That
issue
becomes
a
working
issue
faces
right
if
it
was
created
by
an
internal
stakeholder.
The
issue
becomes
a
working
issue
if
it
was
created
by
us,
so
basically
all
them
were
treated
equally,
which
is
it's
okay,
but
that
was
pretty
confusing.
I
think
it's
kind
of
hard
to
like
understand
which,
when
we're
talking
about
implementation,
when
we're
talking
about
validation,
we're
talking
about
research,
we're
talking
about
design
and
whatnot,
so
I
think
what
we
decided
is
that
we're
not
gonna
move
those
issues
into
the
workflow
talks
anymore.
G
G
Now
I
ties
back
to
the
original
issue,
but
it's
just
basically
describing
the
problem
in
a
very
succinct
manner,
and
then
that
issue
becomes
the
actual
issue
that
we're
gonna
work
through,
like
the
workflow
frights
like,
for
instance,
we
have
like
a
usability
testing
validation
item
right.
That's
like
we
validate
that
on
problem
validation
that
we
move
that
to
we.
We
have
that
on
the
backlog,
validation
and
we
move
that
problem
validation.
Then
we
move
that
to
like
design,
then
like
solution,
validation,
then
back
to
design
and
then
finally
to
development.
G
What's
the
evolution
of
the
design
I
like
the
feature
in
terms
of
like
we
said
right
now
in
terms
of
work,
if
it's
been
worked
on
like
in
the
research
area
or
if
it's
being
worked
on
the
design
area,
so
I
don't
know,
oh
I
just
want
to
put
it
out
there
to
see
what
you
guys
think
about
it,
but
I
like
it
so
far.
I
think
it's
very
good
way
to
work.
G
Of
course,
like
a
lot
of
the
responsibility
falls
on
James
he's
the
one
who
basically
needs
to
go
like
check
out
the
open
issues,
move
them
to
the
validation
backlog
with
the
new
issue,
and
then
he,
when,
when
things
get
like
closed,
then
he
needs
to
go
on.
Like
closed
your
original
issue,
so,
like
there's
still
little
bit
of
manual
manual
workflow
going
on
there,
but
it
definitely
helps
me
a
lot
of
the
designer
to
see
it.
That's
clean,
you
know,
that's
why
it's
sure.
D
Yeah
now
just
adding
here
the
what
we're
doing
further
for
release
is
that
moving
to
two
different
boards,
first
age
groups.
So
we
have
the
planning
board
where
the
validation
in
the
design
phase
is
it
happen,
and
then
the
dev
boards,
where
things
that
were
ready,
scoped
they
moved
there
and
then
the
developers
worked
this
way,
and
that
means
that
yeah
we
have
to
be
working
ahead
and
Ian
do
you
want
have
Boise
or
your
comment
as
well:
yeah.
B
D
We
also
have
those
those
issues
that
Jackie
and
created
for
like
things
that
need
you
acts
attention
so
yeah.
We
have
the
board's
the
in
the
backlog
where
we
should
all
look
for
an
upcoming
items,
but
then
we
prioritize
them
separately
to
kind
of
help,
also
balance
the
the
workload
and
to
our
top
priorities.
It's
still
pretty
new
I.
Think
I
think
we
do
this
based
on
the
package
example,
if
I'm
not
mistaken,
yeah,
it's
interesting
and
who
on
how
does?
How
is
working?
How
is
this
working
with
the
like
with
two
designers?
G
Usually,
there's
we
don't
have
like
an
over
cross
there,
because,
although
they
are
both
very
fine,
we
are
both
very
fine,
like
usually
like
the
item.
Hopefully,
hopefully
will
be
tacked
as
route
testing
or
group
continuous
integration,
but
I
can't
get
away
your
trailer
like.
Maybe
what
are
your
trend,
while
you're
trying
to
say
like
there's
gonna,
be
issues
that
seem
to
be
it
could
be
continuous
integration
or
testing
right
or
both
and
I?
Think
that
when
that
happens
like
when,
basically.
G
That's
a
hard
question
like
in
the
past.
I
know
that,
like
Demetri
has
like
chiming
in
certain
things
and
I
have
in
doing
the
same
on
his
issues,
but
I
think
we
kind
of
like
depend
on
our
PMS
to
like
figure
out.
If
the
issue
is
there
or
not,
so
I
will
say
that
it's
very
hands
up.
It's
like.
Oh,
my
PM
says
that
this
is
an
issue
that
be
long
long
slow.
So
he
work
max.
G
A
Yeah
and
it's
just
something
that
I
had
a
discussion
on
this
today
with
Jason
Lenny,
who
is
the
director
of
the
chastity,
but
also
who
is
an
interim
product
manager
for
the
configure,
continuous
integration
stage
group?
And
he
been
basically
talking
about
this
approach
that
Dimitri's
also
starting
to
take
so
that
he
is
creating
like
that
word
for
the
UX,
where
he
would
be
like
basically
mirroring
these
items
for
the
Deaf.
In
order
to
have
his
own
backpack.
A
And
then
he
said
that
let's
make
sure
that
if
we
are
mirroring
the
items
or
like
if
we
are
creating
one
one
issue
from
another
one
for
the
UX
passivity.
Let's
make
sure
that
we
like
have
a
clear
title.
There
like,
for
example,
design
a
solution
for
or
like
like
yeah
like
research
that
or
they
saw
it
like.
A
We
don't
have
to
same
exact,
same
title
for
the
issues,
one
on
the
dev
board
and
one
of
your
export,
because
that
looks
that
can
look
very
confusing
for
the
customers
and
also
to
avoid
using
their
action
labels
on
the
UX
items,
because
the
direction
labels,
as
we
know,
they're
they're,
being
shown
in
the
handbook
in
the
pages.
Sorry
not
in
the
handbook,
but
only
get
the
pages
where
we
showcase.
What's
going
to
be
delivered
in
a
milestone.
A
D
So
that's
pretty
much
the
question
in
this
life
thread
like
do.
We
need
an
opportunity
campus,
yes
or
no,
and
the
answer
from
I
think
Scott
Christie
was
that
for
a
job
to
be
done
that
we
already
support.
We
don't
necessarily
need
an
opportunity
canvas
unless
it's
a
really
use
of
time
from
designer
and
a
p.m.
and
there's
a
merge
request
to
update
these
criteria
in
the
handbook.
D
Well,
just
a
heads
up:
that's
you
know,
for
whatever
reason,
if
you're
confused
or
if
you
think
that
the
opportunity
gave
us
will
be
available
for
the
experience
baseline
for
the
job
to
be
done,
experience
that's.
That
was
the
answer
from
product
and
my
second
question
that
is
not
there
has
anyone
else
started
restoring
their
if
there
are
jobs
to
be
done
or
have
finished
it
in
the
the
last
quarter.
D
A
That
Dimitri
is
doing
quite
some
research.
He
his
job
to
be
done,
is
about
getting
on
board
to
give
up
CI
and
they
was
pretty.
It
is
a
pretty
huge
topic
that
actually
funny
enough
ended
up
to
be
the
templates
stage.
Group.
That's
racing
right
now,
so
I
know
that
yeah
he
wasn't
really
recording
it
yet
because
they
are
doing
some
of
the
smaller
Corrections
with
with
engineering
and
but
he
was
validating
everything
that
he
found
with
users.
So
maybe
maybe
it's
maybe
you
have
to
pinky
meaty
yeah.
D
I
had
a
chat
with
him
a
couple
of
weeks
ago,
and
he
said
that
the
score
was
the
same,
and
because
of
that,
the
like
the
video,
it's
quite
the
same
because
I
wanted
to
see.
You
know
the
the
assets
were
at
least
deliverables
from
other
people
and
then
what
they
need
to
say
is
that
the
other
isn't
it's
the
same
score.
A
I
B
So
quick
wasn't
ready
for
that
yeah.
So
the
next
question
that's
on
the
agenda
was
about.
Does
anybody
need
any
specific
knowledge
from
another
area
in
CI
CD?
There
isn't
a
specific
piece
of
knowledge,
but
we're
working
on.
We
built
a
dependency
proxy
which
currently
kind
of
caches
versions
of
docker
images.
One
of
the
reasons
it's
really
useful
is
because
we
cache
it.
B
But
there
was
also
conversations
around
like
adding
the
time
it
saved
to
a
pipeline
or
some
other
parts
of
CIC
D
where
that
kind
of
comes
into
play,
and
so
I
wanted
to
raise
to
everyone,
not
necessarily
to
answer
the
question
now,
but
if
you
think
there
could
be
a
way
that
the
dependency
proxy
helps
your
area,
it
would
be
great
if
you
could
jump
into
that
epoch.
Sorry
yeah
there's
an
epoch
now
and
kind
of
give
us
some
thoughts
or
feedback
we're
still
in
ideation,
so
there's
no
design
so
anything
like
that.
B
G
Yeah
I
recorded
a
video
of
how
to
set
up
like
CIE,
has
mostly
I
project.
I.
Think
that
that
could
be
helpful
for
anyone
who,
like
needs
I,
mean
I,
said
I
not
like
you
review
up
is
not
super
straightforward,
so
like
that
that
video
explains
well
how
to
do
it.
I
like
how
to
use
like
now,
which
is
like
a
site
site
that
side
that
Co
service
explains
that
have
a
small
way
of
setting
setting
that
up.
G
I
think
that
that
could
be
helpful
for
it,
but
someone
if
they
want
to
understand
like
certain
aspects
of
like
say
no,
but
your
Eid
lab
CI
mo
file
and
how
I,
like
you
interact
with
other
services
outside
of
eat,
lab
and
whatnot.
So
I,
don't
know.
I
I
thought
I
would
just
put
that
for
anyone
who's
interested
on
it.
A
E
You
you
honestly
threw
me
for
a
loop
when
I
watched
that
cuz
I
was
like
wait
a
minute.
You
cannot
deploy.
I
get
my
page
on
a
review
act
like
you
can't
do
it
it's
impossible.
How
did
you
solve
this
problem,
but
it
it
was
a
good
example
of
like.
Oh
it's
just
if
it's
a
static,
you
can't
build
and
deploy.
There's
not
that
problem,
but
yeah
so
like
it
was
great
cuz.
You
know,
I
mean
this.
Is
you
touched
on
two
of
my
areas
and
I
actually
learned
something
by
watching
you,
so,
okay,
I.
J
E
I
think
it's
a
great
like
you
know,
don't
never
assume
you
know
stuff
right.
It's
amazing.
How
often
like
you
watch
somebody
on
a
video,
do
something
that
you've
done
a
thousand
times
chances
are
you're.
Gonna,
learn
something
like
wow
I,
didn't
I
didn't
I've
been
doing
this
hundred
times.
I,
never
thought
to
do
it
that.
E
We
want
to
fix
this,
but
we
need
this
other
group
to
do
that
anyway,
so
that
topic
came
up
yesterday
again
and
Nadia
was
nice
enough
to
volunteer
me
to
like
just
let's
get
something
happening
on
this
right.
So
two
things
are
happening
right
now.
One
I'm
working
on
an
issue
trying
to
articulate
this
a
little
bit
clearer
than
I.
Just
did
there
so
I'm
working
on
that
issue.
So
we
can
all
participate
in
that
give
an
idea
of
it
and
then
I
think
the
next
step
out
of
that
is
to
have
think
big,
I.
E
Think
the
first
one
probably
like
just
to
talk
about
the
problem,
make
sure
the
hypothesis
that
I
just
kind
of
threw
out
that
those
are
the
real
problems
are
the
real
problems
and
then
see
how
we
want
to
tackle
it.
But
I
could
turn
that
see
that
turning
into
a
series
of
like
raw
stage
think
things
I
know
Jackie,
that's
actually
your
idea
is
like
the
cross
stage,
thinks
big
I
think
are
going
to
be
useful
things.
So
thank.
F
E
C
E
A
B
Yeah
so
I'm
super
excited
I,
think
things
are
happening
because
they
all
came
from
a
random
meeting
with
Tim
and
I
that
just
blew
up
into
a
thing
that
actually
is
really
effective.
So
that
just
makes
my
heart
sing
because
I'm
a
processor,
it
would
be
cool
just
as
an
outside
initiative,
so
like
partner
with
the
product
management
team
or
CI
CD
and
start
having
those
like
large-scale
vision.
Conversations
about
what
CI
CD
could
be
and
I
wonder
if
that
would
enable
us
to
have
the
trickle-down
effect
of
like.
B
E
B
D
Still
the
topic
of
crustacean
tendencies,
we
have
a
few
current
and
upcoming
items
in
release
related
to
environment
variables.
That
also
happen
in
verify
so
I
linked
all
those
issues.
I
mean
some
of
those
issues
there
and
my
suggestion
was
to
collaborate
like
in
a
prototyping
phase,
because
there
was
a
proposal
from
from
Dmitry
from
I,
don't
know
months
ago.
That
I
think
it's
a
good
start,
but
first
it
wasn't
validated
and
also
doesn't
consider
all
the
use
cases
for
release
that
we
have
for
for
the
environment
sections
of
the
settings
page.
D
It's
a
good
thing
that
Jackie
is
here
because
we've
been
discussing
this
issue
for
a
couple
of
days
and
weeks
now,
but
I
would
like
to
assign
a
specific
DRI,
because
it's
a
different
teams
and
different
designers
working
on
the
same
page.
Dmitry
is
not
here
Dale,
but
one
you
can
perhaps
give
some
I
know
some
inputs
on
how
you
see
the
collaboration
happening
there
and
yeah
it's
something
that
we
can
definitely
take
over
from
a
release.
Point
of
view.
It
crosses
with
both
release,
management's
and
progressive
delivery,
so
Mike
and
I.
D
We
had
a
lot
of
troubles
with
this
page
I
mean
there's
it's
too
much
content
and
we
keep
adding
variables
and
input
fields
there.
It's
not
usable
at
all
and
the
responsiveness
is
also
a
mess
so
Demeter's
proposal,
if
you're
not
looking
at
the
Asian
now
what
is
to
bring
the
creation
of
variables
to
a
model
and
that's
super
awesome
but
yeah.
D
We
need
to
consider
the
the
edge
cases
and
use
cases
also
for
what
we're
planning
on
on
release
management
and
progressive
delivery,
and
it's
just
unclear
now
who's
a
DRI,
but
Jackie
do
you
know
I
think
our
issues
move
to
the
backlog.
What
do
you
know
if
we're
gonna
touch
this
with
the
environments
job
to
be
done
in
departments
interviews?
It
are
so
difficult
to
be
working
on
so.
F
The
surveys
that
I
have
the
the
questions
that
I
have
in
the
survey
today
are
very
focused
on
the
environment
views
and
how
people
are
using
actual
environments,
so
environment
variables
might
come
up
and,
as
we
start
to
dive
into
secrets,
management
and
supporting
vault,
aashiq
or
bizarre
defective
secrets,
management
tools,
but
I
haven't
I,
haven't
created
any
issues
to
deep
dive
into
how
environment
variables
are
being
used.
Today,
it's
just
that
just
environments,
okay,.
D
Yeah
I
know
that,
from
a
progressive
delivery
point
of
view,
there's
a
lot
of
things
that
we
want
to
do
now
with
the
environment
variable,
so
I
actually
worked
on
the
issue.
Three
chocolate,
seven.
That
became
like
three
different
issues
and
I
know
that
this
page
is
going
to
keep
changing
so
just
a
heads-up
that
whatever
happens,
we're
three
people
were
unit.
A
D
A
Really
nice
of
you
to
bring
this
up
this
kind
of
I
think
it's
really
nice
that
someone
is
able
to
support,
to
support
that
and
yeah
and
I
and
I
think
your
suggestion
to
just
find
one
person
who
will
be
responsible
for
that
and
maybe
all
three
will
participate
but
yeah.
Maybe
you
can
even
you
can
take
a
little
bit
further
and
just
make
sure
that
I
get
that
that's
aligned.
You
know
what's
the
best
way,
yeah.
D
G
Okay,
that
makes
sense,
but
I
don't
know,
I
have
some
cost
about
that.
Maybe
we
can
talk
about
it
applying,
but
like
we're
gonna,
do
that,
like
that's,
not
what
you
need
to
actually
bring
in
environment
variables,
like
other
places,
for
like
it's
very
needed
like,
for
instance,
we
were
setting
up
your
did:
lopsy
IMO
file,
that's
like
an
area
where
you
really
need
to
have
like
that
context
of
your
environment
variables.
So
you
won't
make
sense
that
you
can
just
open
it.
G
D
B
Yeah,
so
next
up
is
user.
Research
I
am
going
to
be
coordinating
with
Lori
when
she
becomes
available.
I
mentioned
earlier
that
I'm
doing
the
jobs
to
be
done,
research
which
is
looking
at
all
the
jobs
and
the
like
individual
tasks
related
to
a
job
and
I'm
trying
to
get
a
robust
array
of
data
in
terms
of
what's
important.
What's
not
so
I
was
hoping
to
get
some
assistance
in
terms
of
how
do
I
reach
out
to
support
and
get
them
to
engage
and
rate
things.
B
A
From
customer
success,
sales
I've
talked
to
someone
from
customer
success.
He
was
like
yeah.
We
would
love
to
engage
in
the
conversations
like
that.
I
haven't
really
been
yet
involved
with
sales,
but
I
can
help
you
figuring
out
people
who
we
can
work
there
with
I
also
was
even
in
that
with
Ryan
forgot
his
name,
that
there
are
analysts,
who
is
often
that
chase
Jason's
meetings.
Who
is
like
the
main
analyst
basically,
and
he
was
bringing
a
lot
of
like
data
from
I,
know
from
like
Forrester
Gartner
and
their
expectation.
You
know
all
of
that.
B
That
would
be
perfect.
My
big
open
question
right
now
that
I
would
like
to
ask
Laurie
is
what's
the
best
way
to
capture
all
of
that
data
and
knowing
that
there's
so
many
avenues,
I
want
to
pursue
right
now,
it's
set
up
in
an
issue
and
I
could
use
reactions
and
thumbs
up
and
thumbs
down,
and
that
could
help.
The
problem
is
that
you
create
a
bias,
the
more
people
that
fill
it
out.
The
more
things
seem
important
because
they
have
reactions
so
later
on.
B
A
B
A
Just
kind
of
like
a
heads
up
about
that
again,
the
new
stage
group-
that's
emerging
in
verify,
so
at
all,
moved
from
CI
to
the
template
stage,
group
she's
going
to
be
the
responsible
PM
there,
and
that
was
about
a
heads
up
for
Laurie
that
we
just
had
a
meeting
today
with
Talan
Jason
talking
about
what
is
this
stage
group
gonna
be
about
by
the
way
heads
up
for
everyone
on
this
call?
It
sounds
like
it's
going
to
be.
A
lot
of
overlap
with
was
release.
A
A
E
I
E
A
E
A
Seems
like
that's
okay
way
to
do
why
I'm
asking
because
it's
like
24,
it's
close
to
the
19th,
and
although
we
had
someone
there
with
respective
issues,
open
and
I
wanted
to
see,
should
we
bring
this
up
right
now
we
talked
a
little
bit
about
some
of
the
things
that
maybe
some
of
us
plays
there.
Someone
wants
to
complain
about
something
someone
wants
to
good
I.
B
D
Made
a
suggestion,
I
think
all
the
way
out
there
that
it's
awesome
that
we
consider
retrospective
issue.
But
perhaps
we
can
also
bring
our
own
stage
group
issues
there
because,
for
example,
some
of
the
points
making
the
UX
retrospective
issue
they're
not
the
same
as
the
one
that
we
make
in
the
team.
D
A
D
Let
me
start
it:
I
was
talking
right,
I
didn't
go
over
the
UX
retro
yet
because
I
always
have
trouble
figuring
out.
Is
this
1207
or
Java
8
or
whatever,
because
we
work
in
different
timelines,
but
I
think
in
general
positive
thing
was
the
team
split
or
that
we
we
had
a
conversations
about
it
and
we
finally
did
something
about
it.
D
Yes,
definitely
a
positive
thing
and
one
not
negative,
but
it
always
happens.
That's
often
have
not
related
to
see.
I
said
he
would
often
have
the
issues
being
brought
up
like
mean
milestone
that
they
already
have
UX
proposals
that
were
not
reviewed
by
waxers
I
mentioned
before
that
we
are
moving
to
you
know
those
two
different
boards,
and
hopefully
this
will
help
us
a
lot
with
their
with
the
with
this
problem.
But
it's
always
a
case
that
there
is
something
that
it's
considered.
Super
minimal
and
I
have
an
issue
here
to
eat.
D
An
example
was
like
add
a
button
here
right,
but
this
button,
just
like
the
environment
interface,
that's
three
teams
working
on
it,
but
their
proposal
seems
so
straightforward.
That's
the
engineering
team
just
starts
having
a
conversation
how
to
implement
it.
So
what
is
the
conversation
again
for
us
to
have
with
with
the
PM's
in
the
team
as
a
whole
that
yeah,
you
might
be
simple,
but
let's
see
if
this
really
is
really
what
we
want
to
achieve
and
in
this
example
specifically,
we
had
all
of
our
developers.
D
C
D
C
D
I
F
So
I
think
that
that's
something
that
we
can
start
enforcing
like
on
the
product
management
side
and
I
can
start
percolating
with
PM's
about
a
way
to
solve
some
of
that
and
yeah.
This
looks
like
a
really
straightforward
implementation
and
doesn't
need
a
UX
view
because
sometimes
like
product
is
obviously
just
thinking
about
their
area
and
not
understanding
what
this
looks
like
across
other
areas,
either.
D
Yeah
and
I
think
are
the
engineer
team.
They
do
a
great
job
by
figuring
out
within
those
gaps
when
they
happen
and
and
something
that
I
brought
up
in
the
release.
Do
you
work
in
retrospective,
but
that's
I,
don't
think
in
general,
everyone
needs
to
be
a
bit
more
attentive
because
I
don't
think
they
would
move
forward
with
the
backhand
proposal
without
child
backhanders,
right
or
front-ends
new
component,
just
because
someone
suggested
and
that's
kinda
the
analogy
if
something
seems
very
straightforward,
just
make
sure
that
there
is
a
new
wax
chair
right
on
it.
A
Brilliant
point
I
think
that's
often
thing,
unfortunately,
and
very
nice
analogy
that
you're
saying
Ayanna
so
I
think
like
if
we
see
that
peak
that
and
bring
it
up
here
as
well,
Mike
Cohen,
maybe
especially
Mike,
is
with
I
on
the
same
stage.
Have
you
seen
something
like
that?
Does
it
happen
in
your
stage
below.
E
Yeah
I
mean
I,
mean
I
think
it's
always
gonna
happen
right.
Sometimes
it's
like
it's
that
you
don't
know
what
you
don't
know
kind
of
thing
right,
so
it's
like
this
thing
seems
simple.
So,
let's
just
do
it
makes
sense,
because
you
know
that's
how
you
get
stuff
done,
but
and
it's
great
to
move
forward
fast
and
get
things
done.
That
just
didn't
be
done.
That
makes
sense
too,
but
then
there's
like
that
always
yeah,
like
some
of
my
favorite
design
work.
E
E
So
it's
it's
just
something
you
got
to
look
out
for
and
I
think
the
best
way
to
handle
it
is
what
Jackie
was
talking
about
is
great,
but
also
you
know
it's
just
we
need
engineers
to
get
it
and
more.
You
work
with
them
the
more
they
do.
Right.
I
think
it
takes
one
time
of
working
an
engineer
through
that
process
of
like
yeah.
No,
it's
not
just
the
button
and
here's.
Why
and
then
then
they're
like
aware
of
the
process,
so
you
know
my
thoughts.
A
D
What
I
would
like
to
see
us
is
having
more
days
across
stage
discussions
like
we
didn't
see
any
and
for
us
to
not
just
do
it
from
a
design
like
for
the
design
like
this
things,
accessions
I
think
they're
great
idea,
bringing
the
PM's
together
to
build
this.
This
shared
vision
and
I
would
love
to
have
a
way
to
see
where
things
overlap
and
see
what's
plan
for
that
and
how
do
I
fit
in
this
plan,
because,
right
now
it's
like
what
I
mentioned
before
me.
D
A
F
G
A
F
I
mean
it's
valuable
in
that
I
like
to
connect
with
all
of
you
and
see
how
I
can
help
I
would
say
that
the
first
half
of
this
meeting
I
end
up
like
using
it.
You
also
do
other
things,
because
it's
just
kind
of
like
listening
and
then
when
something's
relevant
I'll
duck
in
mainly
cuz.
This
is
like
the
timezone
crunch,
where
I
often
have
like
overlaps
with
a
bunch
of
other
people,
so.
F
D
C
E
Yeah
I
think
my
role
on
the
team
is
to
always
state
things
negatively,
since
everything
else
is
so
positive.
My
fear
in
PM's
joining
this
meeting
is
I,
do
think.
There's
value
and
us
talking
as
UX
team
about
UX
stuff.
That
inherently
always
does
involve.
You
know
the
product
as
well,
but
there
would
be
a
temptation
for
it
to
turn
into
a
like
planing
kind
of
like
strategy
of
what
we're
going
to
accomplish
and
less
about
peer
design
topic,
so
I
would
be
in
favor
of
both
I.
E
A
E
I'm,
saying
is
I
I
like
the
way
Jackie.
Does
it
right
like
she
shows
up,
she
doesn't
have
an
agenda
if
she
wants
to
participate,
she
participates,
but
it
she
hasn't
like
driven
the
conversation
away
from
like
our
topics.
So
that
would
be.
My
only
fear
is
not
every
p.m.
in
the
world.
It's
this
great!
It's
Jackie
right,
no
I
mean
there's
just
a
right.
You
get
a
lot
of
PM's
together.
They're
gonna
want
to
talk
about
key
em
stuff
right,
get
a
lot
of
you
Xers
together.
They
want
to
talk
about
UX
stuff.
F
E
I
think
I
think
having
both
will
be
body,
but
I
just
don't
want
to
lose
this
one
right,
I
think
a
group
conversation
with
p.m.
this
would
be
fantastic.
Much
like
this
has
been
fantastic
right.
We
didn't
we
used
to
not
have
this
call.
We
could
this
call.
It's
been
great
I.
Just
don't
wanna
lose
that
maybe
we
can.
E
D
We
can
have
like
once
a
month
the
standing
call
like
this
very
same
call,
but
we
do
aggregations
and
we
invite
PM's
and
other
people,
but
then
we
still
lead
the
conversation
right
just
like
what
every
scene
does
they
didn't
like
the
what
you
exit
group,
we
have
our
slice.
These
are
topics
that
we
want
to
present
it.
Cuz
I
agree
with
Mike.
D
The
conversations
you
want
to
have
with
PM's
but
I
think
like
yeah
many
bar,
but
I,
think
we
have
so
much
to
learn,
for
example,
from
team
and
Ian
in
the
ways
they
worked
gather
or
to
sort
of
you
know,
people
are
doing
the
opportunity
campus,
for
example,
with
it
together
with
their
design.
I
think
we
can
use
this
moment
with
Ian's
to
get
a
bit
more
knowledge,
but
but.
G
Seema,
who
we
make
this
one,
so
we
have
these
wings
bi-weekly
right.
So
what
we
will
do
is
like
we
keep
this
one
bi-weekly
and
then
we
add
another
one
on
top
of
this,
one
right
like
which
is
a
monthly
one
with
the
same
title,
but
it
says
like
product
product
sync
up,
you
know
like
UX
products
income
so
like
it's
only
visible
to
us
as
you
waxers
that,
like
like
it's
at
the
same
slot,
but
then
like.
G
A
I
think
taking
all
of
this
feedback
from
all
of
you
into
account
I
will
just
yeah,
probably
like
replace
like
every
force
or
every
third
session.
We
can
invite
everyone.
We
can
update
the
invites
in
in
perspective.
So
if
everything,
if
everyone
is
good
without
I'm,
just
gonna
change
it,
so
we
don't
add
another
session,
but
we
take
like
one
of
this
and
turn
it
into
it
once
in
a
while
with
the
PMS
would.
F
M
A
They
say
anyway,
we're
five
minutes
over
I.
Don't
want
to
keep
people
who,
especially
like
that's
the
last
thing
before
I,
don't
know
the
Friday
evening
dinner
or
beer
wine
or
whatever
enjoy
the
weekend.
Everyone
thinks
I
really
enjoyed
the
session.
Thanks
thanks.
Everyone
who
contributed
and
yeah
I
took
your
money.
Heyo.