►
From YouTube: Testing UX / PM Sync 2021-09-30
Description
Gina and James did a bit of a deep dive on what's next for JTBD research in prep for upcoming maturity changes (covered in a previous video: https://www.youtube.com/watch?v=4dRkVVS-0s4).
A
B
B
Yeah
so
my
fir,
my
highest
priority
is
just
solidifying
the
usability
testing,
mr
and
and
then
I
have
a
couple
other
runner
issues.
I
have
to
do
for
this
milestone,
so
those
are
pretty
high
up,
but
I
I
added
that
item
for
job
to
be
done.
Mr
and
I
just
wanted
to
say
thanks
for
reviewing,
I
think
I
feel
pretty
comfortable
with
the
iteration
that
we're
at
now.
So
hopefully
that
will
go
okay
and
oh
yeah,
and
then
I
just
have
a
working
group.
B
The
the
mr
widgets
working
group
has
started
creating
mrs
to
like
update
those
now
with
the
new
format
and
peyton
created
one
for
performance
testing
today
and
if
you
click
on
that
you
can
see.
I
originally
think
that
I
did
not
need
to
review
that.
It
does
need
ux
review,
but
it's
not
going
to
be
it's
refactoring,
the
widget,
so
that
it
can
take
in
the
core
component
changes
once
the
core
component
is
set
up.
A
A
B
A
I
just
I
don't
remember
if
that
just
uploads
a
report
or
if
that
actually
runs
a
load
test
somewhere.
So
what
I
would
do
for
purposes
of
this
is
just
like
simulate
the
running
of
the
performance
test
by
just
uploading,
a
report
of
the
output,
because
that's
all
this
widget
is
consuming
that'll.
Save
you
a
lot
of
hassle
of
configuring,
a
runner
somewhere
to
do
this.
A
B
A
A
Of
your
review,
that's
I'm
just
trying
to
suss
out
did
we
expect
these
changes
as
part
of
the
refactor,
because,
if
you're
refactoring,
something
I
would
just
expect
it
to
be,
the
underlying
code
of
structurally
is
changing
but
visually.
It's
the
same.
This
looks
to
me
more
like
a
hey.
We
changed
it
visually.
B
So
I
my
guess,
is
that
the
refactoring
is
just
trying
to
get
appropriate
icons
for
those
different
situations
and
that's
why
the
icons
are
changing
and
then,
but
I
I
think
I
need
to
read
up
on
a
little
bit
more
around.
What
would
then
change
after
this?
Basically,
it's
definitely
the
collapse
button.
I
don't
know
what
else
there
is
so:
okay,
cool.
A
This
week,
so
I'm
working
on
transition
issues
or
my
transition
issue
getting
ready
to
transition
out
of
testing
over
to
pipeline
execution.
This
week
I
created
the
14
5
14
6,
14,
7
planning
issues
and
scripts
for
them.
I
think
that
I
shared
one
or
two
of
the
scripts,
but
I'll
go
back
and
make
sure
that
they're
all
shared
with
you
and
I
have
a
block
of
gina
content.
A
That
is
this
just
didn't
care.
It's
gena
content
that
I
assume
you'll
populate
for
me
and
then
I'm
supporting
our
testing
internship
scott
did
another
practice
interview
yesterday
and
went
a
lot
better.
Thank
you
again
for
helping
last
week.
It
was
great
feedback
for
him
and
yesterday's
added
a
little
bit
more,
but
there
was
a
big
big
step
he's
doing
great
and
then
our
customer
journey
research.
A
I
have
a
bunch
of
interviews
scheduled.
I
screwed
up
with
calendar
lee
though
it
there
was
a
conflict
between
calendly
and
whatever.
Whatever
that
thing
is
that
use
that
creates
focus
time,
that
it
blocked
a
bunch
of
time
in
the
first
two
weeks
of
october,
so
the
first
round
of
emails
I
sent
out
nothing
got
scheduled
until
like
the
15th
of
october,
so
I
have
a
bunch
of
end
of
the
month
interviews.
A
A
I
just
want
to
ensure
that
we
are
good
on
what
is
set
up
from
a
planning
perspective
of
moving
co-testing
and
coverage
forage
forward
from
viable
to
complete
and
usability
testing
from
minimal
deviable.
I
haven't
done
the
jobs
to
be
done
review
in
this
quarter
that
I
said
I
would
do
so.
I'm
going
to
try
to
fast
track
that
that's
just
a
we've
already
done
the
research
on
it.
We
established
that
there
are
jobs
to
be
done.
Are
they
still
the
right
ones
for
complete
maturity
versus
a
viable
maturity?
A
So
I
got
to
figure
out
how
to
do
that.
That'll
be
one
of
my
priorities
for
the
last
two
weeks
of
the
month,
probably
and
then
any
other
validation
that
we'll
need
to
do
I'll
work
on
that
in
transition
and
building
out
the
project.
Quality
summary
is
something
that
we'll
want
to
do
as
part
of
that's
part
of
our
complete
vision
for
the
category,
and
I
think
that
either
project
test
results
summary
being
able
to
visualize
just
here's
the
current
state
of
tests
for
this
project
or
doing
the
jococo
parsing.
A
Those
are
the
next
two
things
that
I
look
at
as
opportunities
for
us
to
move
it
forward.
I
don't
know
that
we'll
have
capacity
and
testing
to
do
both
with
current
staffing,
but
we
can
definitely
move
one
of
those
forward.
I
think-
and
then
I
figure
may
through
july
of
next
year,
is
when
we'll
do
the
category
maturity
scorecard
research
with
external
users.
I
always
just
left
a
full
quarter
to
do
that.
A
Research,
because
that's
how
long
it
was
taking
me
when
I
was
running
at
solo,
I
think
you're
getting
through
those
a
lot
faster
than
I
was
because
you're
doing
a
better
job
of
making
it
a
priority
than
I
was
so
that
you
may
not
need
that
entire
timeline.
But
I
wanted
to
make
sure
that
that
was
out
there
and
then
following
kind
of
that
same
script
of
starting
with
usability
which
you're
in
the
middle
of
the
jobs
to
be
done.
Research.
Now
we
can
continue
that
into
november
if
we
need
to.
A
Is
that
right,
usability,
yeah
code
testing
and
coverage,
and
then
I
feel
like
there's
one
that
I
had
scheduled
to
move
in
october,
so
we'll
want
to
start,
then
in
november,
probably
the
next
cycle
of
that
as
well
of
starting
the
job
to
be
done.
Validation,
so
we'll
need
to
look
at
the
categories,
type
yama
file
to
suss
that
up
cool
or
does.
Does
that
all
make
sense?
Did
I
explain
that
in
a
way
that
is
clear
yeah?
That
was
clear,
awesome
all
right.
So
I
think
our
to-do
here
is.
A
B
I
I
think,
considering
just
thinking
about
like
you
moving
to
a
different
group,
it
would
be
nice
if
we
could
evaluate
so
when
we're
doing
the
category
maturity
scorecard
we're
going
to
be
evaluating
two
jobs
at
the
most
from
a
single
feature.
Jesus
and
my
question
was
which
one
should
we
prioritize?
B
A
I
forgot
that
we
hadn't
moved
the
code
quality
job
to
be
done
over
to
the
sas
team
still
sit
here
so
need
to
I'll
get
rid
of
that.
We
have
tests,
ran
status
of
the
projects
tests
and
we
haven't
researched
a
job
around
code
coverage
that
might
be
an
interesting
job
to
look
into
either
from
the
manager
perspective
or
the
the
developer
perspective.
Either
person,
I
think,
would
be
interested,
so
those
might
be
jobs
that
would
get
rid
of
these
jobs
potentially
or
even
open
up
a
whole
new
parent
job
or
job
category.
A
A
A
We
might
test
on
this
job,
but
when
I
open
an
mr,
I
want
to
see
if
the
code
changes
are
covered
or
not.
We
have
that
capability
now
with
the
test
coverage
visualization
yep,
so
we
could
test
on
that
job.
I
don't
know
that
flaky
tests
is
gonna
be
necessary
for
us
to
get
to
complete.
I
feel,
like
the
just
tell
me:
the
status
of
the
tests
is
gonna,
be
a
better
first
step
for
us
to
get
to
complete
that
aligns
us
better
with
what
what
customers
are
used
to
getting
out
of
their
ci.
B
A
A
A
A
A
A
B
A
B
A
B
A
A
A
A
B
A
All
right
keeping
going
down
the
agenda
for
our
last
couple
of
minutes
quarterly
plans.
What
did
I
create
here?
Oh,
I
recorded
a
quick
walkthrough
of
how
I'm
using
these
different
road
maps.
If
you
want
to
take
a
look
at
it,
it
should
help
give
you
better
visibility
into
what's
coming
up
from
a
direction
and
a
possible
ux
perspective,
so
the
recording
is
there.
A
Now
hannah
was
going
to
take
a
pass
at
those.
I
added
it
as
a
read-only
item
today
for
the
team
I'll
edit
this
discussion
item
probably
next
week
for
the
team
just
to.
If
I
don't
see
more
issues
getting
tagged,
then
let's
talk
about
it
and
make
sure
that
we're
finding
that
ux
death
collectively
as
we
as
we
see
things,
and
I
think
that
our
team
does
a
pretty
good
job
of
looping
you
in
when
there
is
a
change.
A
B
A
Just
want
to
make
sure
we
have
a
healthy
pipeline
of
them
just
to
ensure
we're
not
accumulating
ux
debt.
I
know
that
the
widget
thing
is
getting
a
whole
working
room
cleanup,
but
I
know
that
we
have
other
areas
on
the
pipeline
page
on
the
jobs
page
as
built
artifacts
comes
into
the
fold
and
we
start
to
create
things
there.
B
I
have
not
really
made
it
a
priority
for
myself
to
go
through
and
see
what
is
going
on
in
the
backlog
yet,
and
I
think
it's
because
I've
been
so
focused
on
current,
like
design
deliverables,
I
need
to
get
out,
so
I
can
at
least
go
and
add
that
to
my
tasks,
okay,
I
started
doing
it
today,
it's
a
a
little
bit
hard
for
me
to
jump
in
without
any
like
context,
so
it
takes
longer
for
me
to
read
through
the
issue
and
understand
what
it's
going.
What's
going
on.