►
From YouTube: Verify & Release By-weekly UX Meeting | 20th May 2020
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
Yeah,
so
welcome
everyone
to
the
refine
release.
Ux
meeting
we
probably
gonna
have
a
little
bit
of
a
shorter
meeting
today.
Maybe
not,
it
seems
like
we
have
a
little
less
participation
yeah
a
couple
of
read-only
items.
I
will
not
announce
them
because
they
yeah
those
are
just
about
the
out
of
office
and
okay,
ours
that
I've
created.
So
if
you
have
any
feedback
on
that,
please
visit
the
issue.
Okay,
Anna.
Thanks
for
the
update,
so
I
just
ended
before
the
meeting
and
yeah
I
will
give
it
over
to
Anna
to
announce
the
first
stage.
B
B
Our
part
is
water,
the
environmentalist
view
improving
connectivity
after
the
components
of
the
environments
and
changing
the
ways
that
the
environments
view
work.
Today
we
got
a
lot
of
feedback
from
users
that
they
have
a
lot
of
problems
on
and
trouble
navigating
throughout
the
environments
that
jobs
waste
southern
environments.
So
this
would
cover
those
issues
and
also
environments
dashboards.
It's
a
quite
long
recording.
Let's
say
you
get
25
50
minutes.
B
Cross
with
progressive
delivery,
but
those
are
mostly
butts
and
we're
going
to
look
again
at
those
issues
in
the
future
and
define
how
to
start
working
on
them.
Another
thing
we
decided
is
that
we're
gonna
think
make
so
instead
of
just
tackling
bug
by
bug
and
issue
by
issue,
we
want
to
look
at
it
in
a
more
holistic
way.
Think
what
would
be
the
best
approach,
for
example,
on
how
to
navigate
your
own
environments?
B
How
do
we
want
to
show
the
data
about
deployments
in
the
dashboard
view
and
then
break
this
into
issues
or
reference
to
existing
issues,
but
we
want
to
work
on
bigger
user
stories
for
environments
and
decide
how
we
want
to
repurpose
the
existing
issues
that
I
want.
So
that's
a
big
attack
but
I
think
it's
also
an
interesting
topic.
You
know
that
environment
Tempe
has
been
yeah.
A
This
approach
pretty
like
well
logical
and
interesting.
The
way
how
Jackie
broke
the
epic
into
three
explicit
three
phases
like
bugs
than
the
redesign
and
then
the
new
features
Pro
like
I,
wanted
to
ask
like.
Why
did
she
say
it?
Why
did
she
select
this
particular
brush,
but
probe
like
it
sounds
like
it's
a
big
like
enhancement,
redesign
project
for
a
huge
piece
of
functionality
like
environment.
So
probably
it
makes
sense
to
structure
it
that
way,
but
I,
like
I,
just
wanted
to
compliment
that
split
and
I.
B
It
also
makes
sense
that
to
check
out
the
bugs
first,
because
you
can
quickly
see
if
they
were
still
reproduce
or
not,
and
you
already
know
the
expected
behavior.
So
let
me
talk
about
redesign
and
new
features.
It's
really
something
that,
for
it,
went
to
first
evaluate
and
check
the
low-hanging
fruits
and
make
our
customers
happier
with
the
small
fixes.
B
We
haven't
quite
someone
back
in
issues
that
are
also
listed
there,
so
it's
a
mix
of
UX
front-end
back
in
it's
a
bit
of
everything,
but
I
think
this
approach
makes
sense
in
a
way
that
we
can
also
look
at
the
development
capacity
and
availability.
And
you
know
we
don't
really
need
to
to
count
on
that
right
away
to
move
with
the
design
specs.
Anything
like
that.
We
can
do
the
design.
B
We
don't
worry
that
much
and
also
I,
don't
think
she
already
did
know,
but
we
also,
we
also
brainstormed
about
you,
find
the
different
views
to
make
sure
that
environments
live
in
a
single
place.
I
have
mentioned
Eastern
idea,
but
now
we
have
environments
dashboard
and
they
also
have
environments,
ListView,
environment
details
view
deploy
boards.
They
all
live
in
different
places,
so
there's
also
this.
B
This
session
also
gives
us
the
ability
to
discuss
what
it
makes
sense
to
rethink
how
people
are
navigating-
and
you
know,
put
some
effort
into
improving
that
the
bigger
user
experience
for
environments
rather
than,
let's
add
a
button
here
and
leave
people
to
some
somewhere
different.
So
it's
a
big
effort
but
I'm
very
excited,
because
yeah
environment
is
everywhere.
A
Nice,
thanks
for
updates,
okay
and
I,
think
it's
useful
on
two
perspectives.
First,
the
process
as
I
said
it's
interesting
and
second
of
all,
yeah.
If
anyone
has
any
well
dependencies
or
cross
cross,
dependable
things
and
environments,
I
guess
that's
nice
cuts
out
looking
forward
to
see
the
results.
It
looks
like
going
to
be
a
big
baby
after
this
I.
C
Was
gonna
add
something
on
my
stage,
but
I'll
hold
it
off.
I
probably
should
be
a
be
so
swamped
that
I
didn't
know
like
exactly
what
to
put
here
to
discuss.
There's
like
a
couple
of
things
that
I
would
like
to
discuss.
Well
like
it's
maybe
wait
for
the
next
one.
I'll
share
a
couple
of
things,
but
yeah
there's
definitely
more
things
happening
on
Runner
lately.
C
A
C
B
Yeah,
so
we
started
at
this
week
right
with
the
UX
kickoff,
where
Billy's
management
and
not
sure,
if
you
guys
saw
the
threat,
is
lack.
We
got
some
positive,
but
also
like
questionable.
Not
she
was
not.
The
right
word
in
English.
Sorry
doesn't
translate
that
blow
in
English,
but
some
feedback
saying
that
yeah
I
think
it
was
weird
that
there
was
a
UX
kickoff
after
the
brother
kickoff
in
because
you
know
some
people.
They
referred
to
those
videos
and
they
need
to
look
at
them
into
the
managers.
B
They
need
to
look
at
those
videos
in
order
to
make
the
big
company
kickoff
announcements,
and
this
wasn't
idea
that
should
a
good
feedback
that
we
received
and
Jackie
wants
to
incorporate
the
UX
takeoff
in
the
release
management.
Video
so
make
one
announcement
where
we
don't
only
talk
about
what
engineering
is
developing
in
delivery,
but
also
what
UX
is
plenty
for
the
milestones
so
we're
gonna
try
the
house
in
13.2
I'll,
probably
just
gonna
record
a
separate
video
and
then
you're
gonna
put
it
together,
but
I
think
it's
so
nice
that
we
got
this.
B
C
B
A
Yeah
until
your
point
and
I
run,
I
think
it
would
be
nice
yeah
like
I'm
I'm,
actually
I
can
pretty
much
easily
imagine
how
to
combine
the
two,
like
you
know
like
how
like
I,
see
it
in
my
hat,
it's
a
happening.
What
happens
pretty
straightforward,
like
you're,
a
designer
of
course
the
you
export
and
then
product
manager.
Of
course,
the
other
part
and
kind
of
combine
it
at
the
end.
C
Yeah
yeah
well
veer
out
that
but
I
love
to
try
it
out
as
well.
B
One
of
the
things
I
mentioned
in
that
in
slides
that
it
can
be
challenging
because
our
priorities
tend
to
change
like
the
u.s.
priorities
are
not
like
engineering
priorities
right.
You
look
at
the
virtue
quest,
they
should
say
this
is
a
five
whatever
and
then
you
you
have
to
deliver
it
in
a
way.
So
that's
one
of
the
points,
I
I
added
the
discussion
that
I
think
we
just
need
to
be
clear
that
this
is
the
design
kind
of
like
the
flexible
goals
for
design
right.
B
It
doesn't
mean
that
I
have
to
deliver
something
by
a
certain
date,
but
this
is
what
we
are
looking
at.
Those
are
the
items
we
are
looking
at,
and
this
is
what
we
want
to
present,
as
in
during
the
kickoff
as
the
items
that
are
aligned
with
our
product
direction,
it
might
be
that
the
priority
changes
or
we
just
deliver
different
design
assets.
B
A
A
Okay,
then,
was
that
it
for
the
processing
stage
group
announcement,
then
I
will
move
on
to
the
cross
stage
ones.
So
yeah
I,
think
many
of
you
have
seen
the
discussion
happening
on
documenting
the
product,
dris
and
yeah.
Thanks
a
lot
for
all
of
the
feedback
you
have
already
provided
upon
the
words
I
understand.
It
sounds
like
a
pretty
busy
period.
Just
I
feel
like
I
need
some
of
them
kind
of
like
bouncing
ideas
in
order
to
document
those
properly
because
it's
kind
of
like
hard
to
digest.
A
That
idea
was
Justin
I,
think
it's
it's
a
nice
way
for
us
also
to
get
a
bit
closer
to
the
to
the
designers
from
their
ops
team.
The
only
one
problem
there
will
be
the
time
because
yeah,
some
of
the
some
of
them
members
are
also
in
Pacific
time
zone,
I
think
so
it's
gonna
be
like
a
little
bit
tough
yeah,
so
yeah
and
sorry
for
this
kind
of.
Like
writing.
Probably
everyone
has
to
Google
right
now
and
understand
what
does
it
mean?
This
is
the
time
so
Thursday
bi-weekly
at
8
a.m.
8
a.m.
A
Pacific
time.
This
is
when
ops
team
have
their
their
design
review
meetings
right
now.
So,
if,
like
everyone
can
mimic
that
to
their
own
time
zones
and
give
me
a
heads
up
and
that's
kind
of
work,
if
you
think
that's
a
good
idea,
if
know
that
it's
certainly
fine
to
keep
separately
but
I,
think
we
could
try
running
those
sessions
for
some
time
together
and
see
what
it
will
bring
back.
B
A
C
A
So
it's
yeah
I,
understand
I,
see
that
it
sounds
like
the
time
is
not
perfect.
Let
me
maybe
try
at
least
like
one
month,
because
maybe
there
will
be
more
advantages
than
disadvantages
from
the
unconvenient
of
the
time
zones.
We
could
just
try
doing
that
once
and
then,
let's
run
a
little
shrine.
If
you
see,
we
think
that
it's
maybe
too
much
effort,
then
we
can
just
revert
back
to
the
normal
time.
E
A
A
Yeah
I
know
that
this
that
propose
timelines
in
the
issue
are
kind
of.
Like
short,
so
the
proposal
is
the
proposal
that
will
be
kind
of
like
a
green,
for
this
task
is
to
break
this
well
recommendation
creation
into
few
little
stages.
So
the
first
one
that
we
agreed
to
finalize
before
the
22nd
of
May
is
to
kind
of
like
khalaqtu,
already
existing
bugs
recommendations.
A
So
if
you
could,
if
you
could
like,
give
it
attention
and
assign
some
more
things
so
that
as
a
next
step,
we
could
be
checking
if,
if
there
is
anything
new
that
it's
not
currently
in
the
least
for
the
improvements
that
we
need
to
document,
maybe
validate
we've
been
talking
about
the
UOC
scorecard
process
here,
as
as
a
way
to
create
a
new
recommendation.
I
understand
that,
like
the
timelines
are
pretty
short
for
that.
A
So
you
know,
I
was
we've
been
chatting
with
Laurie
earlier
with
myself,
who
is
Marcel
and
maybe
just
using
the
well
heuristics
analysis
evaluation
or
try
to
run
a
quick
analysis
with
gitlab
internal
users,
or
even
we
could
try
pushing
you
know
the
the
timelines
here
and
say
hey
if
we
think
this
is
going
to
be
an
important
improvement
yeah
we
can.
Maybe
we
can
make
it
in
another
timeline.
If
you
truly
think
that
this
requires
some
more
attention
from
us
and
then
as
the
last
step
is
kind
of
like
communication
with
p.m.
A
and
the
engineering
managers
to
prioritize,
what
are
we
actually
going
to
do
from
all
of
those
collected
bugs
and
improvements
that
are
already
there
and
from
possibly
the
ones
that
we're
going
to
create?
Or
we
will
be
thinking
about
creating?
We
could
talk
about
okay,
what
are
the
things
that
we
could
propose
to
our
PMS,
but
also
work
with
Marcel
and
create
team,
because
he
said
that
they
could
be
helping
there
to
help
with
yeah
with
implementation
of
some
of
the
functionality.
A
Some
of
the
improvements
around
the
Mercia
quest
experience,
I
put
it
all
of
the
timelines
proposed
in
the
in
the
issue
and
I
just
wanted
to
make
sure
that
you
know
that
I'm
not
creating
something
that
you
will
say
hey.
This
is
crazy.
This
is
not
doable
or
any
actually
any
feedback
or
any
inputs
are
variable
here,
because
I
feel,
like
that's
kind
of
an
important
thing,
but
also
the
timelines
I'm
proposing
are
pretty
short.
C
C
A
Is
the
user
recruitment
process
that
takes
some
time
so
I
was
thinking
if
we
could
be,
you
know,
taking
some
shortcuts
there
and
maybe
recording
heuristic
evaluation.
Videos
like
we
did
for
the
UX
for
cars
in
the
past,
or
maybe
just
quickly
giving
the
tasks
to
some
of
the
internal
like
engineers
or
some
of
the
internal
users
of
a
Mars.
So
maybe
I
was
thinking.
Maybe
there
is
a
way
for
us
to
collect
Lena
like
do
the
reach
the
tasks
to
the
tasks
in
a
shorter
amount
of
time.
C
C
A
A
If
we
think
that
this
is
obvious,
what
we've
heard
about
that
a
lot
again,
it
depends
on
the
case,
but
I
think
there
are
some
things
that
we
could
just
like,
create
as
a
recommendation
coming
from
our
judgment
as
user
experience,
professionals,
other
things
are
need
to
be,
of
course,
better
to
be
around
by
user
I.
Think
we
need
to
look
case-by-case
here,
but.
C
E
Like
if
we
have
customer
feedback
on
an
issue
that
we
can
interpret
as
feedback
see
into
the
design
process,
you
probably
have
a
higher
level
of
confidence
on
what
you're
creating
right.
If
you
don't
and
you're
just
going
by
assumptions
from
your
product
design,
your
product
manager
or
other
assumptions,
you'd
probably
want
to
show
it
to
somebody
to
get
some
feedback
on
it
and
then
the
other
thing
is
the
design
language.
So
if
you're
pointing
straight
from
pajamas,
that's
been
really
verified
right,
a
lot
a
lot,
so
those
design
patterns
should
be
trusted.
E
So
if
that's
the
question,
you
have
I,
don't
sure
if
it
should
be
a
button
or
a
toggle
or
whatever
then
doing.
That
should
probably
be
an
informed
decision
that
you're
making
as
as
a
designer.
So
my
thing
for
research
is
that
I'm
I'm
more
interested
in
getting
making
sure
we
get
feedback
on
the
helpfulness
and
about
a
feature
or
function
and
the
ability
to
successfully
use
it
or
complete
the
task
using
that
not
necessarily
like
small
little
iterations
of
something.
E
B
C
Get
frustrated
with
the
get
up
things
that
I'm
like.
Why
is
it
like
this
and
like
it
doesn't
serve
for
my
I?
Think
we
just
like
look
at
in
a
different
way,
because
we
are
all
so
we
build
good
luck
using
good
luck,
but
I
think
like
sometimes
we
sometimes
we
are
too
harsh
with
ourselves
and
we
don't
value
our
own
feedback
enough
to
the
point.
C
E
C
C
E
Think
too,
we
just
need
to
be
mindful
of,
like
you
said,
any
biases
services
that
people
bring
to
that
conversation
because,
like
the
em,
are
one
of
the
things
that
Christy
put
in
that
research
request.
For
me
to
look
at
is
why
is
there
a
tour
section
of
difference
in
our
performance
between
internal
folks
and
external
folks,
and
it's
probably
those
internal
biases
coming
in,
like
we
know,
what's
going
on
behind
the
scenes,
we're
fine
waiting
for
it
to
do
its
thing.
People
who
do
not
know
do
not
care.
E
A
A
We
don't
really
have
to
validate,
if
that's
a
problem
with
the
users,
because
I
think
we
already
have
heard
about
that
and
yeah
I
think
it's
also
from
the
user
experience
perspective.
It
just
makes
sense
to
make
those
more
visible,
more
explainable
and
yeah,
and
help
out
to
get
from
out
of
the
situation
to
the
user.
You.
B
Know
maybe
we
should
also
clarify
the
myth
when
we
say
that
we
need
to
validate
new
users
that
we
can
also
use
internal
costumers.
We
don't
really
need
to
go
through
the
whole
process
of
finding
people
outside
Caitlin,
but
that
it
can
be
easier
if
you
can
get
ya
an
expert
in,
for
example,
the
delivery
team
that
needs
to
you
know
check
for
vulnerability
issues
and
emerging
paths.
So
I
think
that
that
could
also
help
clarify
this
code.
For
the
this.
A
Okay,
all
right,
so
if
there
is
yeah
you
know
if
there
are
any
questions,
any
concern
or
anything
yeah.
Let's
that's
please
come
back
to
me.
Let's
work
on
this
together
really
appreciate
everyone's
help
here
and
ya.
Know.
Marcel
and
Valerie's
team
are
also
doing
a
lot
of
efforts
here.
So
yeah
thanks
a
lot
for
any
work.
This
is
what
are
you
hopeful.
A
E
It
does
dovetail
mm-hmm
and
then
people
are
having
some
issues
signing
that
port,
so
I
think
I
think
the
consensus
is
to
wait
just
a
few
hours.
I,
don't
know
what's
going
on,
but
dovetails
so
that
very
laborious
process
that
we've
been
under
trying
to
create
insights
into
the
insight.
Repo
is
gone.
No
more
we're
actually
going
to
be
using
dovetail
to
conduct
the
research
so.
E
The
research
you
can
take
notes
in
DuckTales,
so
no
more
spreadsheet
long
live
my
spreadsheets
Reggie's
dead
and,
and
you
can
tag
things
in
the
in
your
notes
in
dovetail,
and
it
will
look
as
long
as
you're
consistent
in
the
tax.
It
will
look
across
those
sessions
and
say:
hey.
You
have
five
things
tags
like
this.
You
might
want
to
look
at
that
and
then
you
can
use
the
interface
to
create
an
insight
like
you
tag
it
as
an
insight
using
the
platform.
E
So
we're
going
to
be
starting
to
store
all
of
our
insights
in
dovetail
and
right
now
we
don't
have
an
API
to
pull
them
back
out
and
it's
like
best
come
up.
Hopefully
soon,
that's
what
dovetail,
but
that's
what
we're
going
to
be
using.
So
it's
very
exciting.
The
research
team
is
very
new
at
using
it
too,
so
we're
all
starting
at
the
same
level,
but
yeah.
If
you
have
access
and
you
can
get
into
it-
I
say-
go
in
there
start
playing
around
with
it.
There's
a
really
good
page.
E
I
think
that
sarah
has
linked
I'll
find
the
dovetail
page
here
from
dovetail
about
like
how
to
use
it
in
ivax
and
there's
also,
there's
I
have
a
slack
what
space
and
I
asked
them
in
the
slack
like
what
are
some
tips
and
tricks?
I
should
tell
my
designers,
and
they
just
point
me
back
to
the
videos,
so
the
videos
are.
Where
is
that
I've
watched
them
all?
It's
a
pretty
good
primer
just
to
get
you
kind
of
feeling
comfortable
with
the
UI,
but
the
best
way
to
do
it
is
to
play
around.
E
B
B
E
Yeah
they're
not
going
away
not
going
away
at
all,
not
gonna,
be
deprecated.
It's
I'm
going
to
sit
there
until
we
can
figure
out
how
to
use
dovetailed
of
pull
them
into
it
and
then
also
go
back
from
dovetail
back
into
it
as
backup
to
dovetail
doesn't
want
you
to
not
use
their
stuff,
so
their
API
is
a
very
stripped
down
as
to
what
they
allow
us
to
explore.
It's
like
useless,
actually
what
they
allow
us
to
export
so
until
they
change
that
we'll
just
use
to
tell
us
our
system
of
record
moving
forward.
E
B
B
A
C
E
E
She's
in
the
process
of
sending
this
out
loud,
I
think
by
Thursday
tomorrow,
everybody
should
have
their
sign
up
email,
but
you
can
do
is
make
sure
they
sign
up
for
it,
because
I
still
out
I'm
still
hitting
some
designers,
not
in
yells
group,
but
other
groups
who
don't
even
have
Qualtrics
access.
So
you
didn't
make
sure
that
they
they
haven't
sign
up
for.
E
Maturity
scorecard
updates
should
be
published
today.
I
gave
Christie
that
okay,
she
pushed
it
out
and
I
think
she
just
has
to
hit
one
more
button
and
it
might
be
out
there
so
I'm
very
excited
so
that'll
be
out
there
and
then
the
jobs
to
be
done.
I
created
a
different
merchant
request
for
it
because
it
was
attached
to
the
other
merger.
Fest
I
mean
you
know
how
merge
requests
work.
This
will
be
a
very
interesting
research
project
for
me,
so
he
did
that
and
so
there's
some
information
here.
E
I'll
share
this
with
you
guys,
so
you
can
have
it.
It's
still
a
draft.
It's
not
nearly
finished,
but
I'm
gonna
be
running
that
alignment
workshop
next
week
with
a
few
people,
and
so
hopefully
from
there
I'll
get
more
details
and
I'll
be
able
to
put
into
this
merge
request.
But
Pedro
looked
at
it
earlier
today
or
later
his
time,
and
he
said
he,
it
was
really
good
information,
so
the
category
of
maturity,
scorecard
stuff
will
be
pushed
out.
I
think
by
Christie
today
so
be
published.
Officially,
it's
going
to
reference
this
page.
E
Whenever
this
page
gets
finished.
This
page
contains
on
stuff
around
jobs
to
be
done
and
I'm
just
waiting
for
that
alignment
workshop
to
make
sure
that
what
I
stay
on
that
page
every
bite
you
to
cream
with
and
then
whenever
we
come
up
with
shared
definitions
and
things
I'll
update
that
page
and
then
hopefully
you
can
push
it
out
to
and
get
that
out,
because
the
truth
for
jobs
to
be
done
will.
E
E
So
yes,
I
feel
free
to
go
into
at
merge
request.
You
should
be
able
to
go
in
there
and
leave
comments
and
stuff
if
you
want
to
feel
free
to
I'll.
Also,
look
at
those
comments
for
my
workshop
to
you
see
if
there's
something
else,
I
need
to
ask
these
people
to
me.
It
serves
on
so
we
can
get
alignment
on
it
as
well.
So.
A
Okay
and
there's
a
final
part
for
this
goal:
let's
maybe
look
into
the
retro
at
the
13.0
or
whatever
was
the
latest
retrospective
or
whatever
the
comments,
or
maybe
the
thoughts
that
somebody
wanted
to
share,
or
maybe
like
I,
actually
see
some
of
the
inputs
from
our
team
members
for
the
13.0
retrospective
I'm,
not
sure
if
you
want
to
bring
something
from
13.1,
because
no,
it's
always
kind
of
like
misleading,
which
one
do
we
talk
about
so
yeah.
Anyone
wants
to
bring
something
good,
bad
or
something
for
improvement.
I.
B
Can
start
since
I
already
reflect
the
issue
just
recently,
which
is
just
one
thing
to
share
I.
Think
the
positive
is
that
I'm
working
so
far
ahead
together
with
the
with
Jackie,
so
I
only
realized
that
when
I
decided
to
take
like
five
days
off
and
that
didn't
affect
my
team
because
yeah,
you
know
we're
kind
of
like
a
milestone
agnostic
at
this
point.
So
that's
that's
super
cool
and
also
even
the
chance
to
have
conversations
about
you
know
bigger
UX
initiatives
such
as
environments,
and
he
gives
us
a
chance
to
do
that.
B
Yeah
those
opportunities
without
worrying
if
we're
gonna
deliver
things
for
the
Deaf
come
on
stone,
yes,
and
also
that's
a
positive
to
me-
and
another
thing
is
that
we
managed
to
plan
you
accept
and
we
assigned
for
13.1
to
UX
depth
issues,
I'm,
actually
excited
and
I'm
gonna
be
working
on
the
front
end
and
we
committed
to
a
sign
at
least
one.
You
accept
issue.
B
B
B
C
It's
a
it's
something
that
we
can
improve,
I
believe
so
it's
quick,
perhaps
document
all
the
internal
team
processes
that
we
we
have
every
several
and
that's
perfect.
They
are
all
helping
us
I
think
they
are
all
useful
in
their
own
way.
They
allow
us
to
solve
problems,
create
communication
channels
and
everything,
but
I
feel
that
now
that
we
have
several
I
think
I'm
having
trouble
to
track
them
keep
track
of,
like
maybe
I
need
to
follow
up
with
this
thing,
maybe
there's
this
meeting,
maybe
there's
this
new
product
product.
C
They
are
writing
that
we're
doing
maybe
there's
this
I,
don't
know
like
if
we
could
have
a
place
where
we
can
track
them
just
so.
We
know
that
what
we're
doing
and
maybe
for
this
particular
meeting
for
the
retros
we
can
go
back
and
look
at
that
list
and
say
like
okay.
What
we
have
been
doing
like
is
this
working.
Is
this
not
working?
Is
this
work
and
it
is
like
so
we
actually
like
read
through
those
things
as
well.
I,
don't
know
I.
A
C
C
Project
for
like
for
the
team,
where
we
are
like
putting
some
issues
and
sharing
some
stuff
I
mean
there's
several
things
that
are
part
of
our
process
and
I.
Don't
think
we
have
any
any
of
that
documented
anywhere
and
I.
Think
at
this
point,
all
those
things
live
on
our
brains
loosely
and
then
we
kind
of
like
come
together.
I
think
the
only
thing
that
it's
basically
tying
all
these
things
together,
it's
our
calendars
and
I,
don't
think
that's
pretty
good.
Aha,.
A
So
you
mean
like
you
need
so
look
because
when
you
said
document
I'm
madly
immediately
imagining
like
yeah
handbook
pages.
But
maybe
what
are
you
saying
like?
You
need
a
place
to
come
back
to
all
of
those
well
issues
or
like
tasks
that
are
sitting
out
there.
So
maybe
we
could
start
leverage
leveraging
and
bring
back
to
use
our
CIC
deboard
CIC
dux
import
or
something
like
that.
C
Yeah,
the
SEC
could
be
a
document
in
Google,
but
like
just
kinda
like
so
so
we
know
all
the
things
that
we're
doing
you
know,
and
then
we
can
come
back
at
the
end
of
the
release
and
say
like
did
we
ever
touch
base
on
these?
You
know,
like?
Are
these
meetings
being
useful?
You
know
because
I
think
that
we
we
we
never
get
a
chance
to
talk
about
these
things,
we're
not
seeing
them
all
together.
C
B
F
C
B
A
D
B
C
So
maybe,
if
we
document
all
those
I'm
going
to
tell
you
why
this
is
helpful
for
me,
because
if
I
have
at
least
then
I
can
go
back
and
I
can
say
like
you
know,
I
feel
that
I'm
not
doing
a
lot
of
these.
You
know
I
can't
like
basically
have
like
a
source
of
truth
that
it's
on
my
calendar
about
the
things
that
I'm
and
it's
just
kind
of
like
a
I,
know
your
tool.
C
A
A
E
A
Indeed,
there
is
a
lot
of
things
that
have
been
introduced
and,
like
things
that
we
started
doing
and
it's
important
to
have
some
sort
of
overview
of
that
I
could
definitely
go
through
all
of
our
UX
pages
in
the
verify
and
release
collect,
maybe
those
sessions
that
are
connected
and
then
maybe
that's
up
to
each
of
the
product
designer
to
document
the
sessions
that
are
happening.
Specifically,
your
stage
group-
and
here
maybe
I'll-
probably
just
also
open
an
issue
that
we'll
be
connecting
to
that.
A
E
C
C
You
know
because,
yes,
I
have,
we
have
slack
and
yes,
we
have
like
to
use
indeed
love
and
everything,
but
if
I
can't
just
go
I
like
look
at
something
and
say,
like
you
know,
I
don't
think
I
have
been
paying
attention
to
these
particular
processes.
You
know,
then
I
can
go
on
like
just
look.
If
why
I'm
not
doing
that,
I
can
just
like
realign
myself
against
that.
A
A
I'll
take
the
few
steps
so
make
for
us
a
place
where
we
could
talk
about
what
are
other
things
that
we
need
to
document
and
I
will
also
look
at
documenting
the
meetings
that
we
have
as
a
first
step,
and
then
we
can
take
it
forward
from
there
thanks
for
any
other
nice
ideas
like
this
nice
input,
improvement
points
or
I,
don't
know
anybody
wants
to
share
something
good.
That
happened
that
we
all
can
learn
from.
B
Each
reading
yeah
yeah-
this
is
not
necessarily
related
to
us,
but
yeah
I
couldn't
really
manage
to
contribute
to
things
outside.
In
my
scope,
like
this
milestone
for
my
mistake,
so
first,
if
I'm
doing
a
traineeship
for
pyjamas
and
I
pretty
much
work
on
only
a
single
merge
request,
because
Nadia
knows
is
my
energy
levels
of
being
pretty
slow
at
this
point.
B
So
I
see
how
this
is
affecting
my
my
delivery,
but
on
the
bright
side
I
know,
I
can
talk
to
my
team
and
I
can
talk
to
Nadia
and
Jackie
about
those
issues
and
realigned
also
yeah
aligned
with
the
expectations.
Everything
and
I
think
related
to
that.
I
also
took
a
couple
of
days
off
this
milestone
and
it's
a
catch-22:
that's
the
emails
and
everything
that
you
have
to
to
track
after
you
come
back
to
the
office.
B
B
E
B
A
You
cannot
go,
but
it's
so
important
to
take
the
time
off,
but
yeah.
This
is
one
of
the
things
that's
holding
us
back
and
I.
Don't
think
there
is
a
magic
pill
from
this
because,
indeed
to
pay
on,
like
you
said,
things
are
just
moving
with
the
training.
Never
stops
it
just
moves
forward,
I
guess
yeah.
A
Maybe
we
could
deal
with
that
yeah
I,
just
living
it
back
up,
it's
somebody
who
can
like
or
like
a
manager,
maybe
as
somebody
who
can
quickly
bring
us
back
to
the
most
important
things,
is
we're
back
and
the
rest
kind
of
yeah
I.
Don't
even
I,
don't
know
how
much
time
you
need
like
if
you
need
to
do
the
follow
up
on
everything,
everything
or
just
like
cookies.
You
know
like
reading
through
all
of
that
yeah
I
think
we
should
also
try
to
not
to
stress
too
much
about
that.
A
B
One
of
these,
like
I
learned
over
the
years,
is
that
the
the
role
of
my
new
axe
back
up
it's
it's
really
like
honorary
role
right,
don't
expect,
for
example,
anyone's
gonna
take
over
my
tests.
Those
emails
are
gonna,
be
there.
Those
tests
are
gonna,
be
open
because
by
the
time
I
come
back
he's
only
ramming
up
on
the
specification
specific
topic.
So
that's
another
point
where
yeah
I
can
probably
get
like
a
status
update
on
things
from
my
backup
but
I
feel
like
if
I
decide
to
go.
B
B
A
B
Know
if
yeah,
but
that's
I,
think
there's
definitely
a
thing.
I
would
like
that
I.
Like
my
peers
in
myself,
you
need
to
get
better
at
like
if
I
assign
someone
as
a
shadow
runner
a
shadow
as
a
backup.
Like
did
you
look
at
my
things
like?
Can
you
help
me
identify
which
items
I
don't
have
to
reply
to?
You
know
just
give
me
like
a
status
update
on
what
happened,
because
usually
I
get
a
reply
as
a
No
a
place
or
nothing
to
report,
nothing
to
report.
That's
what
it
is,
but
I
know
that.
E
And
I
wonder
if,
like
I,
saw
that
out
in
PT,
o
ninja
and
I
be
like
I've
gotten
a
notification
from
like
Sarah
like
maybe
she
goes
out,
and
she
just
puts
me
as
part
of
her
backup,
but
I
won't
get
access
to
anything
else
like
it
all
right
that
propagates
out
throughout
the
system
to
say
from
these
dates
to
this
date.
This
this
issue
of
date
will
go
to
this
person
or
they
will
be
pained
and
guess,
and
additionally,
on
that
update.
E
So
it's
it's
almost
impossible
for
me
to
go
and
follow
up
on
anything
that
she
had
on
in
progress,
I'm,
just
hoping
that
somebody
will
see
it
and
they
slack
her
and
they'll.
Ask
me
instead
of
her
but
I,
don't
think
they
do
I
think
they
just
say.
Although
it's
okay,
all
this
weight
and
I'm
the
only
American
on
this
phone
call,
so
we
just
don't
ever
take
time
off.
We
just
keep
working
all
the
damn
time
when
I
work
with
Europeans,
it's
lovely
because
they're
like
well
no
I'll,
just
I'll
step
away.
E
The
work
will
continue.
It'll
it'll,
be
there
when
I
come
back
Americans.
We
just
tend
to
just
keep
working,
so
it's
it's
a
different
kind
of
situation.
I
don't
like
it,
but
it
is
harder
if
the
system
doesn't
support
the
actual
support
that
you're
asked
to
provide.
It's
weird,
it's
just
weird
to
me.
So
when
I'm
somebody's
backup
I
don't
expect
to
do
much
and
when
I
put
somebody
as
my
backup
I,
don't
expect
them
to
do.
C
Pretty
bad
I'm
taking
time
off
when
I,
say
I
feel
bad
at
taking
time
off.
It
shouldn't
be
like
that,
but
I
definitely
on
so
you
have
a
new.
B
G
F
C
Tried
to
like
eat
James
takes
it
or
Darin
takes
it.
Then
I'm
like
I'm
gonna,
take
it
right,
but
then
they
don't
take
it
so
I'm
like
well
I'm,
not
gonna,
take
it.
You
know
and
James
she's
another
one
of
he's
like
he
works
like
even
in
like
days
that
are
like
you
shouldn't
be
supposed
to
be
working
at
all
right.
So
my
god
to.
F
E
F
A
Right,
we
are
at
the
top
of
the
hour
and
I'm
having
a
meeting
to
go
to
right
now.
So
thanks
a
lot
for
all
of
the
inputs,
as
always,
I
really
much
enjoy.
These
calls
thanks
for
being
open
and
sharing
really
nice
feedback.
I'm
gonna
make
sure
that
I
will
follow
up
on
those
things
that
we
discussed
in
the
retrospective
part,
especially
and
yeah.
Let
me
know
if
there
is
anything
that
I
could
be
helping
with
thanks
all.