►
From YouTube: Project Quality view MVC Kickoff call (2021-06-16)
Description
We (PM and Designer) discussed the business goal and opportunity for the project and the assumptions we will test as part of solution validation.
This was the in depth discussion of the epic overview in this video: https://www.youtube.com/watch?v=bWUyo4k8uvc
A
So,
overall,
our
business
goal
here
is
we
want
to
drive
existing
ultimate
users
to
this
view
and
then
to
other
subsequent
paid
views.
So
the
data
points
that
we
already
have
are
that
the
data
views
that
we
already
have
are
the
group
code
coverage.
That
is
a
premium
feature
we
want
to
take
those
ultimate
customers
have
them
see
this
top
level
quality
type
data
view
and
then
be
able
to
drive
into
others.
We
also
think
there's
an
opportunity
to
drive
them
to
using
other
features
if
we
expose
them
to
gaps
in
that
data.
A
So
those
those
are
the
the
that's
the
opportunity
I
see
today
so
there's
assumptions
that
we
want
to
test
with
this
design.
As
part
of
our
solution,
validation,
where
users
are
looking
for
this
data,
we
know
that
they
have
a
hard
time
finding
it
in
our
current
left,
left
nav
for
lack
of
a
better
term
where
they
always
end
up
in
analytics
ci
cd.
The
the
existing
data
views
that
we
have
today
are
in
repository
and
that's
just
not
an
intuitive
place
for
people
to
look
for
code
coverage.
A
We
want
to
give
them
a
data
or
we're
assuming
that
if
we
give
them
a
data
point
of
here's
where
things
are
at
today
and
a
reference
point
for
here
is
where
they
have
been
in
the
past,
that
that
gives
them
enough
direction
to
say.
Oh,
I
need
to
go
dig
into
this
and
see
what
is
wrong,
that
they
do
need
that
additional
context,
but
they
don't
need
much
additional
context.
That's
the
assumption
that
we're
testing,
so
we
think
that
that
helps
that
will
help
you
simplify
the
design.
B
A
Not
at
all,
I
was
that
was
just
me,
putting
together
a
very,
very
quick
sketch
of
it.
It
was
really
to
talk
through
with
engineering.
Is
it
feasible
to
get
data
like
this
and
present
it
in
a
way
like
this,
I
didn't
reference
pajamas
or
anything
like
that.
We
want
to
use
as
much
off-the-shelf
components
as
many
off-the-shelf
components
as
we
can
for
speed,
because
this
is
a
lot
of
a
test
and
later
for
consistency
with
the
rest
of
the
look
at
the
site.
So.
B
Okay,
another
question
that
I
have
is
it
says
pro
project
quality
dashboard
and
I
think
in
your
previous
video
that
you
had
recorded.
You
also
mentioned
that
what
is
like,
how
would
users
interpret
this
quality
like
what
all
they
expect
to
see
in
that?
So
does
it
right
now
what
the
proposal
is?
Does
it
only
just
upon
putting
testing
related
information
on
the
project,
quality,
dashboard.
A
Yeah
and
we're
not
stuck
on
the
name
either
the
the
name
may
change.
I
tried
to
not
use
the
word
dashboard,
but
it
was
really
hard
to
not
use
the
word
dashboard.
It's
really
just
here's
data
about
the
quality
of
your
project
and
people
talk
about
quality
they're,
usually
talking
about
tests
or
performance,
or
things
like
that,
but
is,
I
think,
there's
potentially
a
fine
line
to
block
between
that
and
monitoring.
A
A
They
think
that
it's
about
testing,
when
it's
really
about
fulfilling
requirements
at
a
compliance
level
that
mark
would
and
the
compliance
team,
not
compliance
the
I
forgot
mark's
team's
name,
but
that
they
put
together
and
there's
really
no
connection
between
the
testing
that
and
the
test
reports
that
we
consume
and
generate
data
views
for
and
that.
So
that's
a
potential
area
of
confusion
as
well.
A
B
A
Test
that
assumption
of
is
quality
the
right
word
here,
and
maybe
we
need
to
field
a
survey
to
validate
that,
or
maybe
we
need
to
do
some,
some
of
the
usertesting.com,
with
just
something
really
simple,
as
a
click
through
of
just
the
left
nav
like
show
them
a
view
of
the
dashboard
and
say
we
want
you
to
go,
find
this,
and
maybe
it
doesn't
have
a
name
on
it
and
they
go
figure
out
where
it
is.
That
gives
them
that
view.
That
might
be
a
way
to
to
quickly
validate
the
right
name
right.
B
Yeah,
this
is
what
I
was
thinking
too.
I
mean
this
workflow
kind
of
fits
to
at
least
get
an
idea
about
what,
where
do
they
go
to
see
quality
related
information
in
the
interface
that
exists
today,
and
maybe,
if
we
put
some
data
there
I
mean
we
can
still
think
about
that
later,
but
maybe
we
can
just
put
in
questions
like.
Are
you
satisfied
with
the
information
that
you
are
seeing
here?
B
A
I
think
that
there's
a
big
opportunity
there,
because
a
lot
of
that
is
dependent
on
how
much
you've
like
set
up
for
your
project
if
you're
only
running
unit
tests
and
giving
us
the
test
report,
but
not
coverage
data
you're,
not
running
code
quality,
you
have
no
performance,
testing,
you're,
not
doing
accessibility
testing.
I
think
that
there's
an
opportunity
to
show
those
panels
as
empty
and
then
give
them
a
link
into
documentation
to
drive
them
to
figure
out
how
it
could
work.
A
So
that's
as
we
continue
down
like
the
first.
The
first
parts
are
really
validating
these
assumptions,
but
I
think
that
there
later
there's
an
opportunity
for
that
that
we
might
want
to
explore
and
we
don't
need
to
incorporate
that
into
the
design
we
can
like
rebuild
it
later.
If
we
want
to
show
extra
cards,
because
who
knows
what
other
categories
we're
going
to
have
in
the
future
too?
So.
B
That's
true
yeah.
We
can
provide
some
confusing
options
if,
in
case
we
proceed
with
the
user
testing
method
of
doing
this,
you
can
probably
give
some
conflicting
options
which
fall
very
close
to
each
other.
For
example,
we'll
just
provide
the
like
hotspots
for
those
places
and
see
where
they
click
first
and
that
communicates
a
lot
in
itself.
A
A
Alternatively,
we
could
go
the
user
testing
route
to
validate
either
the
like
the
design
and
the
navigation,
but
I
would
say
we
should
try
to
do
one
and
one
only
because
we
have
a
very
limited
amount
of
time
and
we
have
you
have
a
limited
amount
of
time
to
get
the
this
done,
because
you're
also
still
working
on
other
projects,
but
we
also
have
the
14-1
milestone
to
work
on
this.
So
we
want
to
try
to
slim
that
down
as
much
as
we
can.
A
C
A
Sorry
scrolling
through
jobs
to
be
done
realizing
I'd,
never
removed
the
good
quality
jobs
to
be
done.
That's
not
our
category
anymore,
okay,
so
we
have
validated
that
where
is
it
status
of
a
project's
test?
Yes,
when
team
leads,
do
you
want
to
see
like
trends
of
test
coverage?
They
want
to
be
able
to
see
that
that
is
a
job
that
they
need
to
do.
That
is
the
job
to
be
done
and
the
maturity
our
maturity.
There
is
graded
out
a
c.
A
There's
not
a
great
way
to
get
to
it
from
mrs
there's
not
a
great
way
to
get
to
it
from
the
group.
It
was
just
really
hard
for
them
to
find,
so
we
have
validated
that
job
to
be
done,
and
I
think
that
this
just
rolls
up
to
a
higher
level
of
not
just
test
coverage
over
time,
but
all
of
my
team's
quality
metrics
over
time
and
okay.
C
B
A
Maybe
yeah
we
could,
we
could
choose
either
the
delaney
or
the
dakota.
Thinking
about
this
at
tiered
at
ultimate
dakota
is
the
right
persona
for
that.
I
think,
because
they're
going
to
be
looking
like,
they
want
to
start
at
the
project
level,
but
eventually
we
might
roll
this
view
up
to
the
group
level.
So
you
can
see
across
multiple
groups
or
across
multiple
projects
within
a
group.
Rather
sorry,
so
I
would
say
for
our
recruitment
purposes,
either
of
them
will
be
fine,
it'll,
probably
be
easier
to
get
the
delaney
persona.
B
A
Okay,
I
think
that's
okay,
because
I
think
that
these
quality,
like
ultimately,
who
we're
going
to
be
selling
these
into
and
the
people
buying
ultimate
or
the
the
organizations
buying
ultimate,
are
probably
bigger
anyway,
but
I
I
think
that
when
we
boil
down
the
problem,
it
applies
the
same.
I
add
a
project
view.
What
do
you?
What
are
you
seeing
so?
Okay,
great.
B
Thanks
yeah,
so
we
can
come
to
this
point,
which
was
the
agenda
for
about
my
bandwidth.
So
I
have
added
the
issue
for
my
planning
and
there
you'd
see.
I
have
a
lot
of
like
enough
time
for
both
the
design,
as
well
as
the
solution
validation
for
this.
So
I
would
be
available
awesome
and
I
think
we,
if
I'm
looking
at
our
ethical.
A
So
we
have
some
timing
14-2,
where,
if
you
want
to
hand
off
the
end
of
solution,
validation
to
me,
I
can
get
it
over
the
finish
line.
That's
fine
or
I
can
finish
up
that
project
that
will
be
just
fine
so
that
you
can
transition
back
off.
So
let's
make
sure
that
we're
partnering
on
that
solution,
validation
as
much
as
we
can.
So
that
would
be
a
seamless
transition,
because
I
think
we
only
have
your
availability
during
14.1.
A
B
Sure,
if,
if
I
see
this
kind
of
encroaching
upon
the
next
milestone
I'll
speak
with
jackie
to
maybe
extend
this
a
little
bit,
because
I
think
we
have
had
a
discussion
once
already
that
it
might
become
difficult
to
do
a
lot
of
work
in
a
single
milestone.
So
this
might
just
seep
in
into
the
next
one.
So
that's
not
a
problem.
I
think.
B
So
I
have
an
idea
around
this
that
first
I'll
go
ahead
and
see
the
solution
validations,
which
are
happening
on
user
testing
and
I'll,
try
to
see
if
they're
facing
any
problem
doing
that
there
so
that
you
know
we
are
prepared
for
any
kind
of
problems
and
in
case
if
it
shows
that
it's
not
the
best
way
to
conduct
a
solution
validation.
Then
we
can
go
the
usual
path
and
recruit
users.
A
I
think
we
should
probably
create
the
recruitment
issue
and
get
the
qualtrics
form
ready
in
the
meantime,
and
I
can
tackle
that.
I
can
do
that
so
that
you
can
focus
on
the
design
part
early,
okay
and
we'll
go
from
there
and
I'll
just
ccu,
or
also
assign
that
to
you.
So
you
can
keep
track
of
that
as
we
go.
B
Yeah
that
will
work.
Okay,
thanks
yeah
this
one
is
covered.
The
next
question
is
covered.
The
next
is:
how
would
we
handle
iteration
during
initial
design?
So
we
are
so
we
stay
aligned.
I
wanted
to
know
like
is
this
about
the
design
that
I
would
be
working
now
are.
Are
you
concerned
about
the
improvements
that
kind
of
we
have
to
work
on
after
the
validation.
A
B
Yeah
yeah,
so
I'm
going
to
ping
you
on
the
issues
of
course,
like
you
and
maybe
front
end
engine,
a
backend
engineer,
front-end
engineer
that
you
direct
me
to
like
who
I
should
be
keeping
in
loop
in
that
for
that
design,
and
in
case
I
feel
that
I
need
some
urgent
input
from
you
I'll
reach
out
to
you
over
slack.
Okay
sounds.
A
A
A
A
So
then
next
steps
are
create
the
design
for
the
mvc
you're
going
to
tackle
that
one,
or
do
that
I
will
work
just
I
will
work
on
initiating
recruitment
I'll.
Also,
if
there's
a
discussion
guide
that
you
can
point
me
at
for
solution,
validation
or
I
can
dig
up
one
of
juan's
old
ones
I
can
start
from
now.
I
can
I'm
happy
to
to
do
that
so
that
we
can
fast
track
this
a
little
bit
more.
B
A
A
But
for
me
this
is
like
this
epic
is
going
to
be
a
big
driver
for
us
for
our
performance
indicator
of
validating
those
ultimate
and
really
those
ultimate
users
get
value,
and
we
can
drive
additional
value
in
other
categories
for
them
once
they
see
at
the
top
level,
all
the
things
they're
missing
so
validating.
This
is
a
top-level
view.
They
want
is
kind
of
that
first
step
for
me,
and
so
that's
what
we're
that's
the
assumption
that
we're
really
validating
with
the
solution,
validation
and
getting
this
feature
out
there.
A
Sweet
easy,
easy,
peasy.
Well,
I
will
so
I'll
take
my
to
dose
of
creating
the
recruitment
issue,
I'll
look
for
a
discussion
guide,
just
skeletal
doc
and
then
I'll
start
filling
that
in
I'll
get
caitlyn
up
to
speed
on
what
kind
of
recruitment
or
the
recruitment
that
we'll
be
looking
for
after
we
validate
that
user
testing
may
or
may
not
work
just
so
they're
in
the
loop
of
what
we're
doing
and
why
we're
kind
of
slowing
that
portion
down
and
then
maybe
speeding
it
up,
really
quick.
A
B
Yeah,
that's
true,
okay,
awesome
and
I
would
start
working
on
the
design,
and
once
I'm
done
with
that,
I
would
I
mean
in
the
process
I'll
also
like
collaborate
on
the
discussion
guide
with
you
and
my
apart
from
working
in
the
design
I'll.
Also
look
at
the
user
testing
existing
solution,
validation
tests
and
see
how
that
how
those
panned
out
fantastic.
I
have.
A
Just
thinking
about
recruitment
I've,
in
the
back
of
my
mind,
I
have
a
couple
of
customers
that
I've
spoken
to
in
the
past
that
have
wanted
this
kind
of
view
that
I'll
reach
out
to
and
see
if
they'll
be
around
for
solution,
validation
or
up
for
it.
So
maybe
we
can.
Even
if
we
do
user
testing,
we
might
be
able
to
get
two
or
three
qualitative
bits
of
feedback
as
well
from
those
customers.