►
From YouTube: UX Showcase: CI/CD Catalog - Lessons learned
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
So
what
is
this
project
about?
I
think
I
have
already
shared
some
details
on
our
coffee
chat
and
also
on
our
team
meetings
already
several
times,
so
our
amazing
PM
Dove
right
in
this
write
down
in
this
epic
in
a
great
way.
What
is
the
problem?
How
can
we
provide
better
option
in
this
case,
so
I
can
just
provide
you
a
really
simple
example.
So
this
was
the
research
that
I
that
was
done
before
I
joined
on
the
team.
A
Thanks
to
Nadia,
we
have
a
lot
of
ux
research
data
already
and
according
to
this
user
research
Theta
that,
like
people,
are
struggling
a
lot
because
building
a
CIA
mobile
to
use
this
Pipeline
and
then
running
a
job.
Isn't
that
simple
as
as
I
expected?
And
if
the
organization
is
big
enough
and
then
let's
say:
okay,
we're
using
Ruby
and
then
they
want
to
have
Ruby
test
job
forever
in
their
different
projects,
and
then
they
just
have
okay.
A
This
is
the
template,
Ruby
tests
and
you
file,
and
then
they
have
this
ssot
git
live
repository
and
then
the
current
experience
just
copy
and
paste
it
to
their
own
ellipsia
mobile
file,
so
which
is
not
that
ideal,
but
I
can
walk
you
through,
like
how
does
that
look
like
so
this
looks
complicated,
but
I
can
just
give
you
a
really
quick
summary.
So
let's
say
this
is
one
CI
template
that
could
run
a
ruby
I
think
this
one
is
for
the
iOS
job.
A
So
let's
say
this
is
used
organization
wise,
and
that
means
the
project
a
want
to
also
have
this
product.
B
also
want
to
have
this,
and
also
for
the
project
C,
and
what
they
do
at
the
moment
is
copy
from
line
one
and
copy
the
end
of
the
line.
Okay
and
I
paste
it
to
their
ciml
file
and
okay.
But
what
happens
like?
Oh
you
know
what
I
we
wanted
a
new
line
here
or
we
want
to
update
a
couple
of
lines
and
the
current
experience
is
black.
A
A
But
if
we
are
having
this
CI
CD
catalog,
that
means
they
can
make
this
as
one
template
and
then
once
they
release
it
as
a
template
in
the
cicd
catalog.
That
means
the
developer
of
Project,
A
and
B
and
C.
They
can
just
use
the
same
template
by
typing
include
and
component,
and
this
means
some
some
different
configurations,
so
maybe
within
like
less
than
10
lines
so,
which
is
very
handy
and
I.
A
Think
the
most
beneficial
to
having
this
option
is
so
when
there's
new
changes
in
the
template
it
just
fetched
to
here,
so
that
they
don't
need
to
like
go
back
to
their
project,
a
CIA
update
line
27
and
do
the
same
to
the
PC.
That
process
will
be
gone
if
we
introduce
this
change,
so
that's
basically
what
CI
CD
catalog
does.
A
So,
whenever
I
saw
this,
like
I
I
literally
got
so
many
emails
to
see
something.
This
is
I,
think
what
you
need,
okay,
but
this
is
about
API,
endpoints
and
discussion
and
then
well,
you
know
I'll,
try
to
understand
the
discussion.
I'll
try
my
best
to
provide
ux
proposal
after
reading
your
post,
so
yeah
it
wasn't
easy
for
the
first
month,
and
so
this
is
like
January
23rd,
which
is
still
so
it's
a
month
too
and
I
was
thinking
like.
Are
we
on
the
same
page?
That's
why
I
was
asking
this
question.
A
Was
this
project
was
kicked
off
about
a
month
ago,
sorry
a
year
ago
and
then
like
this
is
like
okay
like
since,
like
so
many
people
have
different
opinions,
different
ideas,
but
I
was
wondering
like?
Are
we
using
the
same
terminology?
It's
like?
Are
we
Imagining
the
same
product
inside
our
month?
That
was
my
question.
So
this
is
my
favorite
way
to
do
this,
like
just.
Let
me
know
what
you
envisioned
this
product
so
that
I
can
learn
from
them
and
then
so
that
I
can
grab
their
ideas
to
my
design.
A
We
were
using
different
glossary
for
the
same
things.
So
so
that
was
my
first
okay.
We
need
to
discuss
the
terminologies
and,
as
you
can
see
here,
like
everyone
has
slightly
different
ideas
on
how
we
present
the
temp
template
structure.
I'll,
explain
the
details
a
little
bit
later,
and
this
was
the
sketching
session
summary,
which
I
really
enjoyed
a
lot
like
just
summarizing
this
information
and
the
metadata
they
put
it
here.
A
So
I
can
see
that
there
are
two
major
part
of
using
the
components
so
I'll.
Let's
just
ignore
the
creating
components
part
but
I'll,
just
focusing
on
the
using
the
component
part,
because
this
sketching
session
is
scoped
down
into
that
smaller
scope
and
I.
What
I
understood
was
like
okay,
like
using
and
find
components,
is
important.
A
So
this
is
more
like
the
creating
components
part,
but
I
can
just
skip
to
focus
our
discussion
to
the
using
the
components.
So
so
this
was
the
first
action
item
like
let's
discuss
the
terminologies
and
we
had
a
lot
of
discussion.
We
had
a
blueprint
around
like
this
is
our
Alpha.
Now
it's
renamed
to
experiment,
feature
and
they're
like
what
is
component
like
what
is
product.
What
is
burden
like
what
is
catalog
resource?
How
can
we
let's
say?
A
Oh
like
this
item,
and
also
this
like
there
were
so
many
discussions
ongoing
in
the
end
like
okay,
we
sit
down
together.
We
had
a
lot
of
sync
discussion,
async
discussion,
and
then
this
was
kind
of
the
outcome,
and
then
this
really
made
me
like
easy
to
communicate
because
I
was
still
new
like
it
was
like
month.
Three.
So,
okay
now
I
understand
what
their
think
about
what
they
like
to
communicate
to
me.
A
That,
like
I,
need
this
design
for
a
project
or
for
the
components
repository
so
just
kind
of
like
sorted
out
in
my
month,
three
and
what
I
learned
like
why
I'm
working
on
this
MVC
design
for
this
project
is
wow.
There
is
so
many
relationship
between
the
ux
work
and
the
back-end
engineering,
so
the
database
modeling
part,
of
course,
so
you
have
already
experienced
that,
but
especially
for
this
project
like
since
we
are
building
a
new
feature
from
scratch.
A
Our
backend
Engineers
were
focusing
on
creating
a
new
database
table
and
then
they
are.
They
want
to
design
this
database
as
well
and
in
Peril
with
all
the
ux
validation
and
then
the
US
work.
So
this
example
is
what
I
like
to
share
with
you
all
today
is
this.
So
what
this
means
is
you
see?
So,
let's
say
user
already
released
a
couple
of
CI
components
repository
to
here.
So
each
item
that
you
see
here
is
system,
essentially
the
gitlab
repository
that
they
have
Marcus.
Okay.
A
This
is
my
CI
template
Library
project
and
then
I
want
to
let
our
developers
to
use
these
templates,
and
there
were
so
many
discussion
around
data
modeling.
So
it
wasn't
easy
at
the
beginning,
like
what
is
this
discussion
about?
I
can
give
you
some
more
examples.
So
let's
say
so.
This
is
one
of
the
real
use
case
example
that
we
can
publish
to
our
cicd
catalog,
and
what
this
structure
essentially
means
is.
Are
we
want
to
have
a
nested
component,
so
nested
component
means
are.
A
We
want
to
have
nested
like
Ruby
tests
and
Ruby
links
inside
one
project
as
a
whole
like
Ruby,
and
then
let
them
navigate
through
by
clicking
this
project
and
then
okay,
here's
linked
and
then
there's
a
template.
They
can
use
and
also
for
the
test.
So
are
we
wanting
this
data
structure,
or
this
is
another
possible
option
that
we
could
use?
That
means
so
we
didn't
go
this
way,
so
we
don't
have
the
example
for
this,
but
I
just
I
recreated
like
imagine
that
it
would
look
like
this.
A
A
So
we
had
a
lot
of
discussion
like
what
is
more
scalable
option
and
also
a
lot
of
technical
discussions
involved,
but
to
the
user's
Point
like,
which
is
more
scalable
like
which
aligns
better
with
the
users
like
actual
use
case
and
with
a
lot
of
discussion.
In
the
end,
we
decided
to
go
to
this
way
because
of
many
different
reasons,
but
one
of
the
main
reasons
why
we
chose
this
path
is:
if
we
go
to
the
Ruby
and
having
Ruby
tests
and
Ruby
leans
under
this
product.
A
So
if
they
like
to
use
the
Ruby
test
and
Ruby
links
in
a
hole,
then
they
can
also
use
this
Ruby
at
the
version
number
and
then
they
can
paste
it
and
that's
it.
But
if
we
go
this
way
and
then
if
they
like
to
oh
I,
want
to
use
this
Ruby
test
and
Ruby
leans
all
together.
That
means
they
have
to
include
these
two
separate
components.
A
So
that
was
the
reason.
Why
main
reason
why
we
decided
to
go
for
this
direction
and
the
other
thing
is
so
I
think
so.
I'm,
just
like
powering
the
developers
terminologies
that,
like
what
they
discusses,
is
more
like
monolithal
philosophy
versus
monolith,
philosophy
which
I
didn't
get
all
at
that
time.
But
based
on
what
they're
saying
it's
like
having
this
data
structure
and
maybe
at
some
point,
we
did
a
lot
of
user
research
and
then
we
get
a
lot
of
data
point
after
all,
and
then
probably
this
is
more
right
approach.
A
If
we
go
that
way,
starting
from
this
and
people
think
to
this
way
is
doable,
but
not
the
vice
versa.
So
that
was
the
main
reason
why
we
go
for
this
option
and
then
I
realized
that
wow,
like
this
really
impacts
to
the
user
flow,
as
well
as
the
information
architecture
that
that
I
designed
for
our
users.
A
A
So
this
is
what
I've
learned
so
far
using
a
consistent
language
is
a
important,
of
course
you
you
know,
but
like
it's,
especially
for
this
type
of
new
feature
or
new
project
like
we
were
using
all
different
terminology.
So
it
really
helped
that
once
we
come
up
with
the
decision
that
okay,
let's
use
this
language
for
each
concept,
and
the
second
point
was
like
okay
data
modeling
is
really
linked
to
my
work,
especially
the
information
architecture
work
and
it
could
potentially
impact
the
not
just
the
user
flow.
A
You
could
also
impact
the
performance
in
the
later
situation,
so
I
just
really
try
to
participating
in
all
the
technical
discussion
as
far
as
as
I
can
do,
because
it
seems
like,
like
this
data
modeling
at
the
very
beginning
of
the
phase
and
then
like
how
we
show
the
metadata
and
all
the
information
on
the
UI
who
is
is
really
closely
linked.
So
I
I
also
want
to
be
on
the
same
page
with
our
back-end
engineers.
A
So
what
I
learned
is
like?
Okay,
like
I,
need
to
bring
more
back-end
engineers
and
put
in
my
design
process.
So
my
current
focus
is
I'm.
Having
this
design
sync
session,
I
originally
had
this
thing
session,
with
only
the
front-end
engineers
and
the
TM,
but
I
expanded
the
audience
to
everyone
on
the
team
so
that
the
back-end
Engineers
could
join
and
also
try
to
share
their
thoughts
before
I
dive
into
the
design
and
I
also
plan
for
more
work.
A
Like
user
research,
any
design
work
focusing
on
how
user
choose
to
send
text
and
keywords
so
that,
like
they
have
more
opportunities
to
participate
on
my
design
process.
So
this
is
my
story.
Thank
you
for
your
time.
Thank
you
for
attention
and
if
you
have
any
question
and
I
also
love
to
hear
your
experience,
because
I'm
pretty
sure
you
also
had
similar
one
before
and
yeah
I
I'd
be
happy
to
hearing
more
of
the
tips
from
you.
B
I
have
a
question:
is
the
team
looking
at
incorporating
how
to
like
add
a
template
when
you're
working
in
a
file
that
question
makes
sense
so
like,
instead
of
going
out
into
the
catalog
I'm?
Creating
a
file
and
I
want
to
add
a
like
part
of
a
template
into
that
file?.
A
Yeah
I
think
probably
that
more
aligns
with
the
user's
context
but
like
what
currently
they're
doing
is
they
open
a
local
ID
and
then
they
open
up
the
Philips
CIA
mobile
file
and
then
find
something
on
the
repository
and
then
paste
that
into
your
local
IDE.
So
our
goal
for
the
next
iteration,
like
iteration,
two
or
three,
is
to
have
it
next
to
pipeline
editor,
and
then
that
requires
like
really
like
drag
and
drop
style
interactions.
A
So
if
they
find
software
deploy
components
and
then
they
can
use
it
part
of
the
drawer
and
offer
deploy
and
then
they
will
see
the
parameters
and
then,
if
they
click
okay,
I'm
going
to
apply
to
my
file
and
then
they
can
use
it.
But
this
is
our
MVC,
but
that's
planned
for
the
iteration
two
or
three
not
for
now
yeah.
B
Gotcha,
the
other,
the
other
thought
that
I
had
was
whether
this
can
be
tied
to
code
suggestions
at
all
or
if
you've
talked
to
that
team
and
like
if
someone
is
typing
whatever
out
in
their
file,
and
then
we
recognize
that
that's
part
of
a
template
that
we
have,
we
can
Auto
generate
it
in
some
way.
B
A
Actually,
that
was
one
of
the
insights
from
the
recent
benchmarking
study
that,
if
they're
using
our
pipeline
editor,
then
we
can
it's
like
automatically
generate
suggestion
like
if
they
start
to
type
in
like
include
include
components
and
then
we
can
show
in
the
drop
down
they're
like.
Are
you
using
this
I
think
we
can?
C
I
have
the
next
one
I
was
curious.
Did
you
find
it
easy
to
get
involved
with
the
you
know,
data
architecture
like
design
process
I
find
that
sometimes
like
development
or
product,
don't
necessarily
think
of
ux
when
they
think
of
sort
of
that.
That
step.
A
Okay,
like
we
are
really
part
of
this
design
process.
Now
we
are
one
team,
okay,
she's
new,
but
we
are
one
team.
I
think
this
is
the
point
that
I
started
to
feel
like.
We
are
one
team,
even
though
it
was
just
one
two
or
so
so
I
think
it
was
so
long
story
short.
It
wasn't
easy,
but
it
was
worth
to
try.
C
Yeah
definitely
I've
gotten
I've,
gotten
more
involved
with
like
data
architecture,
discussions
in
fulfillment
and
it's
so
valuable
to
I
think
be
in
those
discussions
of
like
how
they're
structuring
data
because,
ultimately,
like
those
are
the
things
that,
like
Downstream,
our
user
experience
and
so
I
was
really
excited
to
see.
You
present
on
this.
D
Okay,
I
think
the
next
one
is
me.
I
wanted
to
check
like
you
talked
about
how
the
repository
and
like
template
sharing
is
going
to
happen
within
an
organization,
but
is
there
a
plan
for
a
more
Global
marketplace
where
just
anyone
can
contribute
and
use
the
templates
yeah.
A
That's
a
great
question:
I,
don't
remember
exactly
which
Milestone,
but
it's
like
16
Dot,
like
seven
or
so
it's
so
we
have
a
plan
to
have
a
like
Open
Marketplace,
but
we
call
it
at
the
moment
as
public
catalog,
so
that
every
Community
contributor
can
create
their
own
CI
template
and
they're
like
yeah.
This
can
be
used
for
the
docker
component,
Docker
build
Docker,
deploy
and
then,
if
they
can
publish
their
components,
catalog
and
everyone
can
use
it.
A
D
B
E
Go
ahead,
cool
thanks
for
sharing
this.
Do
you
think
it
would
be
valuable
for
you
to,
for
you
and
the
team
to
create
a
conceptual
model
with
the
object,
relationships,
attributes
and
possible
actions.
B
E
This
case
it
will
be
multiple
objects
which
I
think
you
already
described
in
the
that
dictionary
or
glossary,
that
you
should
show
yeah
and
yeah
I
was
wondering
if
it
would
be
interesting
to
visualize
those
relationships
and
also
to
start
describing
what
would
be
the
attributes
of
these
objects.
A
I
think
that's
a
great
point,
because
I
I
was
thinking
to
draw
a
model
just
for
me
to
understand,
and
then,
if
I
understand
it
correctly,
so
that
I
can
share
it
to
all
the
team
that
hey
like
it's
my
understanding,
correct.
Is
it
aligning
with
your
mental
model?
I
was
thinking
about
that
Approach
at
first
but
I'll
be
honest.
We
we
have
a
very
strict
timeline
time
to
see
the
this
MVC
design.
A
I
think
I
had
like
two
weeks,
so
that
was
the
main
reason
why
I
could
not
just
start
to
dive
into
that
object
model
and
then
like
just
drawing
like
really
nicely
but
I
I.
Think
for
this
project
is
what
we
need
it,
probably
because
we
will
also
expand
it
to
the
public
catalog,
which
will
be
open
the
door
to
the
open
source
Community
as
well.
A
A
E
Yeah
and
then
it
makes
perfect
sense.
You
were
in
the
middle
of
that
work
and
yeah
and
to
be
to
be
honest,
the
objects
that
we
already
have
in
pajamas.
They
have
been
designed
and
built
for
years.
So
the
first
one
was
merger
requests.
So
it's
not
something
that
we
need
necessarily
to
do
before
or
at
the
beginning
of
a
project,
so
I
think,
even
if
it's
after
the
fact
and
you
it
helps
everyone
think
better.
E
It
might
be
valuable
and
also
as
a
way
for
other
teams
at
gitlab
to
consume
and
use
the
catalog.
So
if
I
don't
know
in
the
future,
we
have
you
know:
I,
don't
know
value
stream
management.
Looking
at
usage
of
the
CI,
CD,
catalog
or
I,
don't
know
something
in
merge
requests
related
to
this.
Then
the
different
teams
can
look
at
those
conceptual
models
to
help
design
their
experiences.
A
Yeah,
that's
a
really
good
part
that
I
didn't.
Think
of
so
thanks
for
raising
this
I
I
think
this
is
definitely
what
we
needed,
because
I
already
chatted
with
one
of
the
PM
on
the
create
team
that
there
are
a
lot
of
complete
type
of
things
that
we
can
provide
to
our
users.
So
this
is
just
the
CI
components
catalog
for
now,
but
probably
we
might
need
to
have
more
template,
Library
Concepts
like
more
into
our
product
and
then
like
to
do
so.