►
From YouTube: Sync on UX Score Card for Variables
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
Well
right
now,
we're
talking
about
the
ux
scorecard
for
controlling
scope
for
cicd
variables,
and
your
big
hypothesis
that
you
have
up
here,
which
I
agree
with,
is
that
variables
are
crucial
part
of
ci
cd
pipelines.
A
A
B
So
my
understanding
was
that
we'll
be
choosing
just
one
job
to
be
done
and,
like
kind
of
when
we
will
be
looking
at
two
different
personas,
we'll
be
thinking
of
two
different
ways.
Those
personas
would
approach
that
jobs
to
be
done.
B
Should
I
talk
through
how
I
expect
each
of
the
personas
to
like
work
with
these
jobs
to
be
done
like
what?
What
is
the
workflow,
that
I
am
expecting
that
I'm
thinking
they
would
follow
so
for
devops
engineers?
So.
A
Real
quick,
when
I
click
on
the
job
to
be
done,
link
it's
not
deep,
linked
into
the
specific
job
to
be
done.
So
that's
kind
of
why
I'm
asking
like
which
job
to
be
done,
you're
thinking
about
because
it
just
links
to
the
all
the
continuous
integration
jobs
to
be
done.
A
So
I
want
to
make
sure
that
we're
that
you
and
I
are
on
the
same
page
about
which
one
and
I
and
I
think
that
it's
the
bottom
one
which
is
one
architecting
pipeline
configuration,
but
I
just
wanted
to
like
double
check
that
we're
on
the
same
page
with
that
piece
so
because
yeah,
absolutely
okay.
A
It's
kind
of
weird
that,
like
that,
that
it
doesn't.
B
When
I
click
on
the
header,
I
thought,
but
then,
when
I
copy
the
link
after
that,
it's
going
to
get
directed
to
that,
but
that's
not
happening.
Yeah.
A
It's
not-
and
I
don't
know
if
it's
just
this
page
or
if
it's
something
to
do
with
the
table
in
this
particular
page,
but
I
just
wanted
to
double
check
that.
That's
exact
that
we're
talking
about
when
architecting
pipeline
configuration.
I
want
to
be
able
to
define
the
variable
so
yeah,
okay,
perfect
yeah,.
A
So
I
think
then,
then
what
I
would
love
to
make
sure
we'll
go
ahead
and
add
to
this
to
this
page
just
for
to
the
discussion
guide,
the
specific
job
to
be
done
just
so
that
we
have
like
absolute
clarity
for
the
for
other
audiences
here.
So
I
just
added
below
the.
A
Okay,
thank
you
so
much
yeah,
you
bet
so
then.
I
agree.
This
is
the
job
to
be
done
that
we're
analyzing
we're
going
to
analyze
it
from
the
devops
engineer
angle
and
from
the
software
engineer
angle.
So
then,
going
down
with
what
you
were
saying.
I
would
love
to
hear
your
expectations
on.
How
do
you
feel
the
devops
engineer
scenario
will
differ
on
this
job
to
be
done
and
yeah
I'll
start
with
that?
A
B
So
devops
engineers
they
are
responsible
for
the
configuration
right
like
they
are
responsible
for
maybe
the
maintenance
of
the
configuration
files
and
how
things
so
if
things
are
working
smoothly
across
teams,
so
they
would
not
be
performing
the
day-to-day
tasks
that
otherwise
the
software
engineer
would
perform.
So
here
what
I'm
expecting
that
devops
engineers
would
be
concerned
with,
is
how
could
they
utilize
the
power
of
variables?
B
I
mean
the
having
a
control
over
defining
the
scope
of
variables
so
that
they
are
easily
able
to
leverage
them
across
projects
like
if
they
define
something
at
a
very
top
level.
Would
they
be
able
to
drizzle
those
down
across
downstream
projects,
and
versioning
was
a
really
great
example
that
I
I
think
tiffany
has
put
here.
The
video
she
has
put
a
video
here
for
a
few
examples
and
versioning
was
one
of
them.
B
So
what
I
did
was
I
took
inspiration
from
that
video
and
I
have
tried
to
form
a
scenario.
I
don't
know
if
this
is
too
hypothetical
or
if
this
is
practical
or
not,
but
it
says
that
in
this
scenario,
you're
a
devops
engineer,
extending
your
support
to
two
teams
in
an
organization
and
you're
responsible
for
centralizing
the
maintenance
of
versioning
across
projects
by
passing
the
version
number
to
the
downstream
projects.
Every
time
it
is
updated.
A
I
love
this.
This
is
great
because,
what's
great
about
a
persona
is
that
it's
typically
a
role
that
is,
that
is
that
it's
a
hat
that
a
platform
engineer
or
a
release
manager
or
even
like
a
team
lead,
could
be
wearing.
A
So
when
we-
and
when
we
interview
this
devops
engineer,
it
could
be
a
title
that
this
person
is
is
wearing,
but
it
could
be
also
a
different
title,
but
they're
performing
devops
engineering
tasks,
so
what's
great
about
this
scenario,
is
that
they
could
be
also
like
a
release
manager
responsible
for
versioning
their
deployments,
and
this
is
a
really
applicable,
realistic
task
that
should
be
executing
that
we
should
be
able
to
execute
successfully
inside
of
our
variable
across
across
projects.
So
I
love,
I
love
this
a
lot.
It
should
be
done
easily.
A
B
That's
great
okay,
and
for
the
software
engineer,
so
you
you
made
a
suggestion,
some
time
back
and
that
that
perfectly
affects
fritz,
because
so
what
was
this
again?
Send
them
changes
yeah.
So
if
a
team
is
working
or
an
engineer
is
working
on
a
project
and
they
want
like
to
share
some
credentials,
maybe
with
the
client,
so
they
could,
if
they're
able
to
do
that
or
not
to
test
that
yeah.
This
is
great.
A
Yeah,
so
that's
exactly
what
I
was
thinking
is
that
that
your
software
engineer
and
startup,
your
manager,
saying
hey,
you
need
to
send
some
changes
on
a
recently
developed
feature
to
a
downstream
test
project
for
a
client,
this
project
and
then
we'd
link
the
scenario
or
the
link,
the
project
there
as
a
trigger
job
and
an
environment.
A
We
can
change
exactly
what
we
what
we
want
to
to
showcase
here,
because
there's
other
things
like
we
may
want
to
test
like
if
a
user
wants
to
store
as
a
file
or
an
environment
variable,
because
there's
that
functionality
too,
that
if
they're
storing
it
they
there's,
there
could
be
clear.
A
There
could
be
lack
of
clarity
in
this
scenario
where,
if
we
want
them
to
use
an
actual
environment
variable
rather
than
like
a
file
inside
of
the
repository,
we'll
want
to
make
sure
that
that's
crisp
in
this
scenario,
because
I
could
see
that
this
this
would
leave
that
ambiguous
where
a
software
engineer
may
find
it
easier
to
like
just
store
that
as
a
file,
rather
than
that's
a
environment
variable.
A
So
we
may
want
to
clean
that
up,
but
your
my
intent
was
to
make
it
so
that
they're
having
to
specify
either
the
environment
for
in
the
variable
or
change
the
variable
for
the
test.
You
know
the
test
environment
or
the
the
permission
structure
or
share
the
credentials
with
the
with
the
client
in
order
to
access
the
feature
right,
yeah.
B
Okay,
this
should
work
well
and
so
tiffany
does
a
great
job
with
like
defining
what
the
flow
would
be.
I
mean
not
exactly
the
flow,
but
we're
defining
what
the
bear
structure
we
need
to
provide
to
users
to
perform
this.
So
we'll
wait
on
her
to
provide
her
inputs.
A
Okay,
wonderful,
that's
perfect
awesome,
so
I
think
the
other
two
under
devops
engineer.
We
can
probably
kind
of
clear
out
because
I
think
the
first
one
right,
this
probably
is
probably
probably
the
best
like
what
we
really
needed
to
do
to
satisfy
the
job
to
be
done,
because
if
we
look
at
the
job
to
be
done,
we're
saving
efficient.
The
core
ask
here
is
that
variables
are
in
efficiency,
play
for
people
they're
they're,
to
save
time
and
to
reduce
waste
and
keep
code
dry.
A
You
know,
do
not
repeat
yourself
so
when
we
think
about
both
at
the
devops
engineer
and
the
software
engineer
dimension.
This
is
all
an
efficiency
play,
so
we
want
to
make
sure
that
versioning
is
efficient,
that
sharing
credentials
across
the
client.
Experience
is
efficient,
so
that
makes
that
makes
sense
to
me.
Okay,
perfect,
perfect,
well
I'll.
B
Go
ahead
and
go
ahead,
yeah,
nothing
everything
else.
So
what
I'll
do
is
once
we
finalize
on
those
scenarios,
I
will
be
expanding
on
like
if
we
need
to
provide
steps
for
the
tasks
and
if
any,
additional
information
we
need
to
provide
to
users
so
I'll
work
on
that.
A
Okay,
perfect
and
then
we
have
the
five
questions
that
we'll
ask
on
the
leica
scale
in
order
to
get
the
scoring
and
then,
if
you
need
help
creating
the
dovetail
project,
I'm
happy
to
help
you
out
on
that
front.
So
if
you
want
me
to
get
started
on
that,
let
me
know.
A
You
know
I'm
your
pm,
so
equal
partners
here,
so
let
me
know:
awesome
I'll,
post
this
video
and
I'll
link
I'll
link
it
in
the
s
fair
or
the
gci
channel,
because
there's
that
one
too,
I
always
forget
about
that.
One
awesome:
okay,
all
right!
All
right.