►
From YouTube: CI & PA UX Research Planning on 2020-09-30
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
Okay,
great
hi,
everyone
welcome
to
our
twice
a
month.
You
ciu
cipa
ux
research.
I
can't
for
some
reason
I
can't
get
to
oh.
Do
you
know
what
I
keep
clicking
on
the
wrong
link
for
the
agenda?
Lori.
You
have
the
first
agenda
item.
I
do.
B
B
I'm
just
here
to
ask
for
help
defining
the
task
or
tasks
that
need
to
be
completed
to
do
that
and
how
to
set
up
a
test
like
something
for
them
to
use
so
they're,
not
using
their
own
get
lab
instance.
I
don't
know
how
to
do
that.
So
point
me
to
some
instructions,
I'll
figure
it
out
or
offer
up
your
your
fine
fingers
and
hand
coding
skills.
B
I
will
take
them
and
we've
moved
testing
out
a
week
to
accommodate
andre's
nice
schedule,
so
we're
hoping
to
do
the
sessions
the
14th
through
the
21st.
B
So
we
don't
have
to
talk
about
like
defining
the
task
here,
I'm
happy
to
do
that.
Asynchronously.
It's
just
a
call
for
help.
C
Yeah
thanks
for
working
on
this
lori,
I
will
I
saw
that
you
tagged
me
in
the
issue
and
also
in
the
document
I'll
go
through
and
do
my
best
to
contribute
whatever
I
know.
B
D
Yeah,
I
guess
the
question
is
like
how
complicated
we
want
the
task
to
be
like.
Do
we
want
to
do
something
simple,
like
ask
the
user
to
like
add
a
couple
of
chest
stages
at
couple
of
jobs
and
that's
it
or
do
we
want
to
ask
him
to
him?
Oh
hell,
yeah,
like
things
like
that,
like
that's,
I
guess
that's
the
that
will
be
my
my
question.
B
Yeah
dove,
that's
a
great
question.
Typically
I'd
say
we
would
want
to
shoot
for
something
in
the
middle,
not
something
too
easy,
not
something
too
hard
a
pipeline.
That
may
be
pretty
typical
that
somebody
might
need
to
set
up.
I
don't
know
what
that
might
be,
maybe
something
to
test
for
testing.
I
don't
know,
maybe
something
to
push
it.
B
I
don't
know
I
don't
have
no
clue,
but
not
something
that
they'd
have
to
like
learn
yaml
for
because
we're
targeting
travis
circle,
ci
and
jenkins
people
for
the
cms,
so
they
may
not
be
familiar
with
our
language.
So,
yes,
it's
kind
of
hard
to
strike.
That
balance,
I
think,
but
I'm
sure
we
can
come
up
with
something
hey
what
what?
What
does
cms
stand
for.
B
A
E
Okay,
it's
again
from
my
understanding,
so
it's
written
in
the
document
that
I
need
to
create
basically
pipeline
for
others
in
my
team.
E
B
F
Yes
perfect,
so
I
was
saying
that
I
have
dropped
a
comment
in
the
document,
so
I
saw
the
jobs
to
be
done
there
that
was
written.
It
says
I
need
to
create
a
green
pipeline,
so
others
in
my
team
can
leverage
ci
to
increase
the
efficiency
of
the
tasks.
F
In
my
opinion,
this
needs
to
be
split
into
two
parts.
This
task
one
is
creating
the
pipeline
and
the
next
one
is
getting
to
the
first
screen
pipeline,
so
I've
just
elaborated
on
the
same
point:
a
bit
there.
D
G
D
B
B
G
C
Yeah,
I
I
agree,
I
think
it's
good
to
keep
it
a
little
open-ended
and
it
would
be
very
helpful
to
see
exactly
what
struggles
our
users
have
if
we
literally
drop
them
into
the
ci,
and
we
just
let
them
try
it
out
and
I
think
that's
kind
of
the
goal
you
know.
C
Eventually,
we
want
to
understand
how
can
we
make
that
experience
as
smooth
and
easy
as
possible,
so
a
new
user
could
be
just
dropped
into
the
ci
and
they
can
understand
what
their
next
steps
should
be
and
how
they
how
they
should
proceed.
Maybe
we
could
do
something
around
like
kind
of
frame
the
task
in
a
way
that
they
have
to
use
the
template
and
can
they
get
to
the
green
pipeline
by
applying
the
template?
C
I'm
not
sure
I'm
because
I,
in
my
understanding,
someone
who
creates
a
project
wants
to
set
up
ci
cd.
They
probably
do
it
from
the
project
page
and
they
click
on
the
add,
ci
cd
configuration
and
then
they
are
taken
to
the
editor
and
that's
where
you
have
all
of
the
templates
and
then
depending
on
what
kind
of
project
you
have,
you
will
choose
one
template
or
another
from
that
point
on.
I
don't
really
know
how
much
customization
and
how
much
knowledge
of
the
yaml
one
needs
to
have.
C
But
this
is
also
something
that
we're
testing
right.
So
then
they
would
have
to
go
to
the
documentation
and
they
would
have
to
figure
it
out
and
probably
fail
it's
not
so
easy
to
get
to
the
green
pipeline
at
first
try,
but
maybe
we
could
set
up
some
project
that
you
could
apply
the
ci
template
for
and
that
would
require
minimal
customization
but
yeah
again.
I
also
don't
know
what
that
project
would
be.
A
Laura
there's
there's
two
types
of
folks
and
I
want
to
know
if
you're
targeting
this
research
on
both
there's
the
one
there's
a
devops
engineer
who
is
creating
everything
from
scratch:
a
new
project
in
get
lab
and
then
needing
to
create
a
pipeline
for
it
and
then
there's
another
type
of
user.
Who
has
a
pipeline
in
a
third-party
ci
tool
and
they
want
to
translate
those
jobs
into
our
ci
yaml
file.
Configuration.
A
B
Okay,
that's
what
I'm
asking
like
what
direction?
Would
you
guys
prefer
for
us
to
go
in
to
I
lean
towards
the
first
one,
because,
if
we're
trying
to
lower
the
barrier
to
adoption
and
people
wanting
just
to
start
using
it,
and
they
may
never
have
used
ci
before
that,
that's
that
devops
engineer
from
the
first
group.
However,
I
do
know
how
important
it
is
to
capture
existing
ci
people
who
are
using
other
tools
and
pull
them
over
to
our
tools.
So.
G
B
Okay
and
then
would
it
be,
does
it
make
sense
to
have
them
use
the
template
as
part
of
that
task
for
that
type
of
user?
B
A
That's
a
good
question:
if
I
had
something
in
another
tool,
I
would
glance
at
what
templates
we
have
to
see
how
closely
it
is
to
what
I
need,
because
the
idea
is
once
they
start
using
a
template.
They
modify
it
slightly
based
on
their
scenario,
but
I
wouldn't
want
to
have
to
edit
it
a
lot.
I
would
look
at
it
to
see.
Okay,
it
has
the
basic
jobs.
A
I
want
the
build
to
test
the
deploy
and
then
I
just
need
to
add
in
a
few
things
that
are
specific
custom
variables
or
whatever,
and
so
I'm
trying
to
think
through
what
the
user
would
do
and
if
they
look
at
the
templates
that
we
have
and
say
that's
not
even
close,
I
would
have
to
edit
it
so
much.
I
might
as
well
start
fresh
from
nothing.
A
In
that
case
they
would
have
to
understand
yaml
to
say
the
way.
I
would
write
this
in
jenkins
or
encircle
ci.
I
would
have
to
write
this
way
in
yamo.
B
Right
and-
and
we
can
do
that-
I
just
my
gut-
tells
me
what
the
outcome
is
that
of
that's
going
to
be.
You
know
we
need
to
support
them
a
lot
more
in
translating
their
variables
into
yaml,
and
I
just
don't
know
how
valuable
it
would
be
for
everybody
to
do
a
test
like
that,
where
we
can't
actually
get
to
the
point
where
they
push
go
and
to
test
the
pipeline
or
anything
I
don't
know.
Maybe
that
is
still
valuable
and
it's
worth
it.
C
Yeah
yeah,
but
in
the
end
this
is
the
this
is
kind
of
the
process
right,
so
there's
no
way
around
it.
The
way
to
the
way
to
get
to
a
green
pipeline
is
to
write
the
yaml
check
out
the
documentation,
write,
the
ammo
show,
documentation,
fix
things
and
then,
after
some
failures
it
will
be
green.
So
I'm
not.
I
unders.
C
I
totally
understand
this
obstacle
that
there's
this
risk
that
we
will
just
get
stuck
with
them,
trying
to
figure
out
yaml
and
that's
the
thing
that
we
learn
but
there's
as
far
as
I
understand,
there's
no
really
other
step
that
we
would
be
waiting
for.
You
know
what
I
mean:
that's
this
is
it.
This
is
the
process.
Okay,.
G
Yeah
and
actually
that's
kind
of
also
the
thing
that
we
want
to
improve
and
make
easier
so
yeah
I
mean
it's
not
ideal,
everybody
gets
stuck,
but
that's
a
lesson
that
maybe
that's
where
we
can
focus.
B
B
So
if,
if
we're
looking
for
something,
that's
much
more
nuanced
about
giving
them
a
task
and
telling
them
to
talk
to
us
the
whole
time
through
and
give
us
feedback
on
what
they
wish
they
had
and
what
they
don't
have
that's
more
of
a
usability
test
and
I'm
open
to
doing
either.
I
we
don't.
I
don't
have
time
to
do
both
before
the
end
of
next
month,
but
I'm
open
to
doing
either
one
whichever
one
the
team
feels
is
more
useful.
We
initially.
B
A
B
Okay-
okay,
that's
that's
fair
all
right,
and
so
we
still
I
I
will
still
need
to
understand
like
what
might
be
the
best
scenario
for
these
people
who
are
coming
in
from
a
third-party
tool
like
what
might
they
want
to
do.
I
don't
know
like
automate,
testing
or
something,
maybe
I'm
not
sure,
and
I
can
for
usability
tests.
You
know
we
give
them
a
scenario,
we
talk
with
them
and
then
they
walk.
B
B
That's
kind
of
the
very
typical
usability
test,
but
we
still
do
need
to
define
the
task
or
tasks
we
want
them
to
accomplish
and
come
up
with
a
system
for
them
to
do
that,
and
especially
if
we're
talking
to
circle,
ci,
travis
and
jenkins
people,
they
probably
will
not
have
a
gitlab
instance
for
them
to
use.
So
that
is
something
that
we
can
take
offline.
That's
perfectly
fine,
but
I
will
still
need
help
with
that.
A
Hey
in
the
screener
lori,
is
it
actually
it's?
Maybe
it's
not
in
the
screener
when
you're.
One
of
the
questions
you
ask
for
in
the
agenda
is
what
kind
of
defining
the
task.
A
Okay
and
it's
just
a
screener,
we
do
end
up
talking
to
them
before
the
actual
interview
session.
So
maybe,
when
we
actually
talk
to
them,
we
can
ask
you
know
during
the
actual
exercise
the
usability
to
test.
We
need
you
to
come
prepared
with
a
small
excerpt
of
any
pipeline.
You
have
and
show
us
how
you
would
use
our
our
tool
to
create
that
part
in
gitlab
ti.
B
Yeah
yeah
and
I
think
in
in
the
event
that
nobody
like
say
you
got
somebody
who
comes
from
a
very
sensitive
company
yeah
I've
talked
to
him
before.
Maybe
if
we
could
get
some
examples
like
one
example
from
each
of
the
those
three
tools
just
to
have
on
hand
in
case
somebody
doesn't
can't,
show,
can't
share
something,
and
then
I'm
also
thinking
maybe
tell
them,
can
they
can.
B
They
share
an
example
of
a
pipeline
that
they've
used
to
do
some
automated
testing
with
or
something
like
that,
because
if
you
don't
give
them
a
little
bit
of
a
parameter,
they
could
come
up
with
anything,
and
we
want
a
little
bit
of
consistency
with
the
pride
with
the
testing.
Otherwise,
it's
going
to
be
hard
to
compare
across
people.
C
Some
someone
can
can
choose
a
pretty
complex
part
and
then
someone
else
can
choose
something
easy
and
then
it's
not
gonna
be
so
yeah
that
will
affect
the
results,
but
maybe
we
could
have
an
excerpt
from
a
pipeline
for
jenkins
and
then
for
other
tools,
and
then
we
just
give
it
to
them.
C
So
if
they
currently
use
jenkins,
we
have
several
users
who
use
jenkins
and
we
give
this
extra
to
them,
and
we
just
need
to
do
some
research
about
like
what
is
a
very
basic
pipeline,
like
a
part
of
jenkins
pipeline
configuration
something
that
we
know.
If
someone
uses
jenkins
ci,
they
will
understand
what
it
is.
D
B
This
tool,
but
for
when
it
comes
to
the
tasks,
I
would
rather
go
with
what
nadia
suggested.
A
So
we
would
like
give
them
an
example:
hey.
This
is
a
pipeline
with
some
jobs
in
jenkins.
How
would
you
adapt.
A
B
C
Yeah
it'll
be
very
useful
for
us
to
understand
the
nuances
of
what
are
the
things
that
they're
struggling
with
it's.
This
is
the
information
that
we're
looking
for.
If
someone
is
moving
from
jenkins
to
gitlab,
what
exactly
do
they
struggle
with
with
the
yaml
configuration,
what
is
unclear
to
them,
and
then
we
will
get
insights
into
how
we
can
simplify
it
and
then,
in
the
end,
how
we
can
automate
it
as
well.
C
E
B
All
right,
perfect,
well
I'll,
update
all
of
the
issues
and
stuff
associated
with
this,
and
who
can
I
bug
and
bother
about
that
code
for
jenkins,
travis
and
circle
ci.
A
Hey,
do
you
want
when
I
look
at
the
screener,
you
have
in
question
seven:
do
you
want
the
examples
to
be
for
the
ones
that
you
have
recruit
five
notes
for
so
an
example
for
circle
ci
for
jenkins
for
travis
ci.
B
B
A
A
B
A
Yeah,
and
so
if
that's
the
case,
if
we
for
whatever
reason,
didn't
anticipate
that
all
of
the
respondents
are
gonna
say
we
use
team
city
and
we
didn't
have
an
example,
so
we
would
have
to.
We
would
want
to
just
go
create
a
team
city
example.
B
A
B
A
Well,
maybe
the
answer
to
that
is
based
on
what
results
we
get
from
the
responses
I
mean,
I
think
the
ones
you
have
is
a
good
guess
now,
but
once
we
send
the
the
screener
out-
and
everyone
says,
I'm
using
bitbucket
we'll
realize
oh
okay,
we
missed
it
on
bitbucket.
Let's
also
account
for
that
one
testing
for
that
one.
B
Well,
the
only
problem
is,
we
may
not
have
time
to
do
that,
because
okay,
we've
got
we've
got
to
do
all
the
data
analysis
and
give
you
guys
findings
by
the
end
of
the
month
next
month.
So
if
there
is
a
competitive
landscape,
though
out
there
that
you
feel
that
bucket
should
be
included
or
trade
one
for
another.
B
A
That
helps
me
to
understand
how
the
process
is.
Thank
you
yeah.
Thank
you.
Can
we
go
back
to
vitica's
comment
in
the
document
that
is
for
the
category
maturity
scorecard?
I
do
tend
to
agree
with
what
vitica
is
saying
there
that
maybe
we
need
to
break
that
into
two
bullets
under
jobs
to
be
done.
B
Well,
the
job
to
be
done
is
higher
level
than
that.
I
think
you're
you're
thinking
more
of
a
user
story,
because
these
are
user
stories
that
have
to
be
done
to
make
that
job
to
be
done.
True
right,
I
need
to
create
that
pipeline,
so
other
people
can
use
it.
What
does
that
really
mean?
That
means
you
need
to
learn
the
syntax
use
the
templates
test
it
and
make
sure
that
it
passes
all
the
tests.
F
I
think
just
a
rephrase
of
how
it's
written
so
now,
right
now
it's
written
to
create
a
greek
pipeline
and
I
think
just
making
it
getting
to
the
first
fight
first
green
pipeline
would
do.
B
A
This
was
very
interesting,
so
I
don't
mind
that
we
spent
a
lot
of
time
on
this.
A
Okay.
I
guess
agenda
item
three:
what's
the
upcoming
problem
validation,
so
I
haven't
had
a
chance
to
review
the
research
finding
from
the
release
management
team,
but
thank
you
nadia
for
reaching
out,
or
was
it
you
laurie
reaching
out
to
jackie
to
to
link
me
to
other
info,
but
after
I
review
that
I
will
avoid
what
their
findings
were
of
what
was
not
needed
and
then
think
about
what
are
the
mvc?
A
We
can
deliver
for
a
dashboard
about
pipeline
health
vitica
when
I
was
thinking
about
this
problem,
validation
and
trying
to
keep
in
mind
your
three-year
plan
design.
Just
your
very
high
level
ideas
there,
it
may
not
be.
A
It
may
be
as
simple
as
that,
as
opposed
to
building
out
an
entire
new
page
and
then
building
on
it
slowly.
A
lot
of
the
ideas
that
vitica
talked
through
in
her
loom
recording
are
the
same
ideas
that
I
thought
I
was
going
to
put
in
a
separate
dashboard
page
altogether,
but
that
would
probably
perpetuate
the
pain
point
that
she
had
mentioned
is
having
to
go
to
multiple
pages.
To
get
the
information
you
want
about
a
pipeline.
So
so
I
think
that's
the
direction
I'm
gonna
go.
A
A
You
can
any
questions
for
me
on
that,
nothing,
okay
and
and
by
the
way,
I
think,
vitica
having
those
high-level
three-year
plan,
mock-ups
kind
of
is
going
to
prevent
me
from
going
down
a
route.
That's
that
would
conflict
with
that.
A
Okay,
I.
F
Don't
know
who's
vitica
is
your
no
that's.
Just
like
a
read-only
thing.
I
think
dog
should
be
next.
Okay,.
D
Yeah,
we
didn't
have
to
start
defining
the
problem
validation,
but
we
do
anticipate
to
have
several
coming
along,
like
the
next
iteration.
Also,
we
just
went
through
some
of
the
desired
workflows,
and
I
think
like
that,
on
each
and
every
workflow
that
we
have
there
and
we
should
probably
create
a
problem-
validation,
the
first
one,
the
immediate
one,
I
think,
is
the
one
I
listed
here.
We
do
want
to
create
a
dedicated
home
for
pipeline
authoring
where
users
are
able
to
in
users.
D
D
We
have
a
section
of
visualization,
we
show
arrows
warnings
and
more
so
like
all
of
that
is
something
that
would
like
to
understand
the
overall
experience
and
more
like.
If
you
go
to
the
workflows
plenty-
and
I
think
we're
out
of
time
so.
A
F
Okay,
yeah
async
would
be
better
just
making
it
a
point
because
it
needs
to
be
done
fast.
Okay,
that
sounds
good.