►
From YouTube: Testing UX / PM Sync 2021-10-13
Description
James and Gina discussed the iterations on the Project Quality Summary MVC (https://gitlab.com/groups/gitlab-org/-/epics/5430) and what next steps would be now that the initial Jobs To Be Done (https://about.gitlab.com/handbook/engineering/ux/jobs-to-be-done/) research is done for Usability Testing.
A
B
A
Yeah,
I
got
the
feedback
issue
for
the
project
quality
in
dc
yeah,
and
I
asked
you
to
look
at
all
of
those,
the
planning
issues
and
scripts
for
what
I've
set
up
for
transition.
Fourteen
five
fourteen
six
fourteen
seven,
those
are
all
out
there
you
get
on
those.
Yes,
I
forgot
to
check
that.
So
we
recorded
the
fourteen
five
kickoff,
so
I
assumed
that
you
were
okay
with
it
this
week.
A
B
Yeah,
I
just
wanted
to
say
that
I'm
not
gonna
even
share
the
thing,
because
I
don't
think
it's
worth
it.
We
have
five
five
days
left
four
days
left
of
this
milestone
four
days
and
yeah,
and
I
just
wanted
to
say
that
the
project
quality
summary
was
marked
as
a
stretch,
but
I'm
still
thinking
that
I
can
get
those
things
done
in
the
last
four
days
it
just
then.
If
we
have
discussion
around
those
changes
that
would
get
pushed
into
fourteen
five
okay,
I
don't
need.
A
Too
much
discussion
on
those
that's
what
I
was
we've
had
plenty
of
discussion
already
like
the
iterations
that
we're
making
are
results
of
our
previous
discussion.
If
you
want
to
break
that
down
more
we've
broken
down
the
epic
so
that
we're
delivering
just
an
empty
page
first
and
then
test
summary
data,
because
we
have
that
or
the
test
coverage
data
rather
because
we
have
that
endpoint
and
then
the
test
summary
data
is
like
sequential
milestones.
A
A
B
A
B
Yeah
I
have
this
down.
I
believe
that
we've
already
talked
about
how
we're
going
to
move
forward
with
this
and
that
we
wanted
to
use
the
same
type
of
process
that
we
did
before
with
user
interviews,
and
I
just
want
to
make
sure
that
that's
still
that's
going
to
be
my
highest
priority
for
testing
in
14.5.
So
I
just
want
to
make
sure
that
that's
plan
still
sounds
good.
So
I
can
plan
for
that.
B
A
B
A
B
A
Else
on
your
side,
no,
that
was
all
right,
so
my
priorities
this
week
continuing
to
work
on
my
transition
issue
and
supporting
scott
and
his
internship.
He
had
his
first
external
interview
yesterday
went
really
well
lots
of
good
insights
still
giving
feedback
on
interview
style,
but
it's
going
going
well,
I
think,
and
then
we
found
a
couple
other
folks,
so
I
think
he'll
get
to
his
five,
probably
sooner
than
I
do
in
the
current
research.
I'm
doing
I
have
do.
I
have
any
interviews
this
week.
A
That
was
the
problem
before
or
just
cancel
them
we'll
go
from
there,
and
then
I
wanted
to
follow
up
on
what's
next
for
usability
testing.
Now
there
are
jobs
to
be
done.
Research
is
complete
for
me.
Logically,
the
next
step
is
great.
Now
we
know
what
jobs
people
want
to
do
now.
We
measure
how
well
we
do
that
right.
So
it
would
be
a
scorecard
against
that
category
with
our
current
feature
set
of.
How
can
you
do
the
thing
that
we
you
have
said
you
need
to
do
yeah.
B
So
I
was
assuming
that
we
were
going
to
wait
to
do
that,
because
that
would
be
part
of
the
category
maturity
scorecard
is
evaluating
that.
I
think,
although
I'd
have
to
look
at
that
again,
because
I'm
not
super
familiar
with
that
process,
I'm
assuming
that
we
would
have
to
have
evaluated
ourselves
like
a
normal,
ux
scorecard
and
then
also
talk
to
people.
A
I
would
think
that
we
would
evaluate
it
ourselves
to
understand
the
gaps
and
then,
over
the
course
of
the
next
six
months,
build
a
feature
set
that
fills
those
gaps.
If
we
think
that
this
is
the
next
thing
that
we
need
to
go
pursue
and
then
we
do
and
then
we
would
do
a
full,
formal
scorecard
at
some
point
before
july
of
2022,
which
is
when
the
schedule
will
do
this.
B
A
I
mean
I
understand
what
the
gaps
are,
so
if
we
just
scored
ourselves
and
say,
can
we
do
these
things
that
someone
would
need
to
do
with
our
current
feature,
set
with
review
apps
and
with
visual
review
tools?
Yes
or
no?
And
what
is
our
general
experience
and
we
find
that
yeah
we
can.
This
is
viable
and
we
look
at
the
other
things
that
we
need
to
do
to
move
to
viable
which
are.
A
Is
there
significant
use
of
gitlab,
and
maybe
it's
understanding
those
gaps
of
what
is
preventing
us
from
doing
using
this
significantly
at
gitlab?
And
again,
I
would
point
back
to.
Can
we
use
this
with
some
measure
of
significance
for
handbook
and
for
docs,
because
we
know
that
there's
gaps
in
the
environment
management
portion
of
using
it
for
gitlab
the
gitlab
project
itself,.
B
B
I
mean
at
the
very
least
I
can
just
use
so
a
normal
like
ux
scorecard,
will
just
use
a
job
to
be
done,
and
then
you
will
have
a
goal
and
task
set
up
with
it
and
I'll
go
through
it,
which
would
actually
be
good
because
I'm
basically
a
new
user
and
I'll
go
through
it,
and
then
note
the
things
that
I
see
along
the
way
that
would
be
marked
as
gaps.
Would
that
fulfill?
What
you're
trying
to
say?
Yeah,
I
mean.
A
A
A
A
I
think
the
first
step
in
that
is
create
the
dog
food
issue,
find
the
dris
for
handbooking
for
docs
and
engage
them
there
in
that
documenting
issue
of
what
prevents
us
from
using
visual
review
tools
today
and
review
apps
to
be
feedback
on
mrs
about
changes
in
the
handbook
and
on
the
documents
or
on
the
on
the
dock
site
versus
go
into
the
emr
and
leave
a
leave,
a
comment
there
like.
How
can
we
get
that
script
embedded
so
that
it's
usable.
A
B
A
Agree,
I
think
it's
just
what
are
our
impressions
of
this
like?
Would
we
feel
confident
just
moving
forward
with
the
ux
scorecard
today
and
having
it
score
at
that
3.14
or
whatever?
It
is
with
internal
users?
And
if
we're
not,
then
let's
try
to
understand
where
those
gaps
are.
That's
the
intent
of
that
is
either
we
have
the
confidence
we
can.
We
can
do
this.
A
A
A
Okay,
none
of
it
is
front
endy
kind
of
stuff
we
actually,
okay,
somehow
with
fewer
front
end
developers
have
more
capacity
in
front
end
right
now.
It
seems
like
just
because
of
the
work
that
is
being
done
in
back
end
yeah.
I
left
a
comment
about
that.
I
think
yesterday
on
the
team
channel
or
the
group
channel.
B
Okay,
yeah,
I
don't
think
I
need
anything
else.
I
actually.
I
am
curious
to
see,
and
I
don't
know
if,
if
I
should
ask
this,
I
probably
should
have
asked
this
in
the
team
meeting.
Are
we
taking
on
any
additional
issues
for
the
merge
request?
Widgets,
because
there's
two
more,
I
believe,
there's
two
more
that
we
still
have
not
done.