►
From YouTube: Tufts Capstone Project: Final presentation
Description
Tufts students. Calisa, Claudia, Emmeline, Melinda, and Alex, present their findings and deliverables from the Tufts Capstone project for GitLab CI/CD.
A
C
B
Okay,
awesome,
hello,
everyone.
So
today
we
have
the
Tufts
University
students
here
to
present
their
Capstone
project.
I
just
want
to
give
a
quick
intro.
If
you
haven't
heard
what
this
project
was
about,
we,
the
ux
team,
was
able
to
sponsor
their
class
the
Capstone
project,
it's
a
it's
a
class
for
senior
level
students
and
they
meet
up
with
certain
industry
level.
Sponsors
like
companies
like
us
and
other
companies
and
carry
out
a
project.
B
D
Yes,
I
think
we're
ready
to
go.
I
can
share
the
slides
if
that
works,
yeah
go
for
it.
Wonderful,
so
thank
you
all
for
letting
us.
You
know
take
the
time
today
out
of
your
weekly
meeting,
we're
really
appreciative
of
having
this
opportunity.
I,
don't
think
all
of
the
Capstone
groups
that
we
worked
alongside
had
this
opportunity,
so
we
really
do
appreciate
it
so
yeah.
D
As
Gina
said,
this
is
our
Capstone
project
for
our
engineering
Psychology
major
all
of
the
majors
students
have
to
go
through
this
project
and
well
not
this
project
specifically,
but
this
course
to
basically
show
what
we've
learned
so
far
and
we
got
the
opportunity
to
obviously
work
with
Git
lab,
which
has
been
really
amazing.
So
we
wanted
to
first
shout
out
Gina
and
Ben
and
Gina
is
a
Tufts
alumni
of
the
program
that
we're
doing
so.
D
It's
been
really
amazing
to
have
this
support
throughout
the
semester,
so
we
specifically
worked
on
the
cicd
onboarding,
oh
sorry,
to
introduce
ourselves
first,
that's
kind
of
important,
so
yeah
I'm,
Melinda,
Fern
I'm,
the
project
manager
for
our
group.
We're
all
engineering,
psychology,
majors
and
I
specifically
have
a
minor,
also
in
studio
art
I've,
had
past
experience
working
with
a
few
other
companies,
and
most
recently
I
was
a
design
ux
design
intern
at
PWC
digital,
where
I'll
be
working
in
September
Emeline.
If
you
want
to
introduce
yourself
first
sure.
E
F
G
Hi
everyone
I'm
Claudia
I,
worked
as
a
ux
designer
and
researcher
on
this
project.
I
am
double
majoring
in
engineering,
psychology
and
computer
science.
There
are
a
lot
of
things
in
the
past
in
school,
but
my
work
experience
has
been
accessible
Engineering
in
Akamai
last
summer
and
they're
going
to
be
working
full-time.
Also,
software
engineering
engages
and
science
systems
coming
in
July
yeah.
H
Hello,
everybody,
my
name
is
Calissa
Sana
I'm.
Also
an
engineering
Psychology,
major
and
I'm
minoring
in
studio
art
I
have
some
experience
as
a
ux
design
and
research
intern,
with
carrier
and
I'm
planning
to
return
there
to
work
full-time
after
graduating
and
yeah
I
helped
with
the
ux
designs
and
some
of
the
research
for
this
project.
D
Awesome
so
yeah,
that's
our
team.
We
were
really
lucky
to
work
together
and
with
get
lab
specifically
and
Gina,
and
Ben
gave
us
the
task
of
looking
more
into
the
cicd
onboarding
at
gitlab.
So
I
know
this
is
the
ux
department
and
it
took
us
a
second
to
get
to
know
what
cicd
is
so.
I
was
just
gonna
review
that,
for
everyone,
just
in
case
cicd,
is
continuous
integration
and
deployment,
and
it
basically
allows
developers
to
automate
the
testing
and
deployment
of
code
into
production.
D
So
gitlab
provides
templates
to
support
this
process
that
can
really
make
it
a
lot
easier
since
it's
so
complex,
so
obviously
because
it's
so
complex,
this
does
provide
some
issues.
So
many
users
find
that
gitlab's
CI
CD
onboarding
process
was
difficult
due
to
the
complexity
of
some
of
these
Concepts.
So
our
goal
for
the
semester
was
to
create
a
prototype
of
how
to
ease
this
process
for
new
git
lab
users,
specifically
users
who
have
professional
coding
background
with
cicd.
D
H
Great
yeah
I'll
kick
us
off
with
the
discovery
research
section
so
going
into
this.
We've
had
kind
of
three
main
goals
and,
as
Melinda
already
touched
on,
we
needed
to
understand
what
cicd
was,
especially
because
most
of
us
had
no
experience
or
I
myself
had
never
even
heard
of
it.
So
kind
of
getting
our
bearings
in
a
baseline
understanding
before
moving
forward
was
critical.
H
Our
second
goal
was
understanding
our
Target
users,
since
none
of
us
quite
fit
the
description
of
our
Target
users,
understanding
their
needs
and
how
they
use
CI
CD
and
how
they
would
interact
with
gitlab
was
important
for
us
to
understand
and
third
identifying
problems
within
the
onboarding
experience.
This
was
the
overall
purpose
of
our
project,
but
this
was
especially
important,
given
the
short
timeline
of
this
entire
project.
H
Can
you
click
the
next
slide
thanks?
Okay,
so
yeah?
We
conducted
a
resource
review
at
the
start
of
the
semester.
Then
we
looked
at
some
of
our
competitors,
gitlab's
competitors,
and
we
were
looking
at
platforms
that
also
had
cicd
functionality
so
looking
at
how
they
onboard
their
users,
what
methods
and
strategies
they
use.
H
E
Okay,
so,
as
Calissa
mentioned,
part
of
our
Discovery
research
phase
included
an
initial
round
of
usability
tests.
These
tests
were
run
on
the
current
product
and
the
onboarding
process
for
our
Target
users,
which
we
Define
as
developers
who
were
familiar
with
cicd
and
had
developed
four
CI
CD
devops
purposes
before,
but
had
not
used.
E
E
E
It
was
also
difficult
for
users
to
find
key
links
in
the
process,
such
as
browse
templates
button
or
the
setup
CI
CD
button
and
selecting
a
template
proved
to
be
unnecessarily
difficult,
as
users
had
to
scroll
through
and
alphabetize
lists,
which
was
kind
of
tough
for
people
who
didn't
know
what
they
were
looking
for
or
what
gitlab
had
to
offer.
It
also
took
the
users
to
a
separate
window
where
they
weren't
able
to
import
directly
and
they
had
to
copy
paste.
E
E
E
E
So
once
we
ironed
out
pain
points
we
divided
and
each
each
group
member
created
a
separate
sketch
of
a
proposed
solution.
This
was
specifically
for
the
a
revamped
way
to
select
a
template.
These
are
the
nicest
ones
of
the
bunch
of
them.
We
were
very
rough
with
these
because
we
presented
them
to
each
other.
E
Then
from
there
we
discussed
our
Concepts
and
the
different
features
that
they
would
entail.
So
then
we
were
able
to
distill
those
into
two
separate
ideas
for
wireframes.
We
ended
up
creating
a
solution
which
would
bring
up
a
drop
down
style
menu
for
selecting
a
template,
and
this
would
include
a
search
feature
and
you
could
look
at
the
recent
templates
as
well
as
suggested
templates,
and
then
you
could
click
browse
all
to
bring
you
some
to
something
similar
to
the
current
window.
That
gitlab
has.
E
The
second
option
was
a
pop-up
style
menu
which
would
offer
a
pop-up
in
the
same
window,
which
would
have
all
of
the
templates
but
with
searching,
sorting
and
filtering
filtering
features,
and
you
could
select
a
template
and
directly
import
it.
So
these
were
rough
wireframes
that
we
presented
to
our
classmates
for
feedback.
G
So
here
you
can
see
so
we'll
we'll
show
you
animations
of
this
later,
but
you
can
see
how
we
have
like
a
button
here.
That
would
actually
go
first
into
a
drop
of
menu
and
then
you
would
be
able
to
click
to
get
the
pop-up
version,
and
you
can
see
here
how
for
the
navigation,
we
came
up
with
almost
a
little
bit
of
a
landing
page
first,
that
would
hopefully
let
the
user
see
the
current
Pipeline
and
see
all
their
information
about
that.
G
I
see
a
survey
to
measure
more
quantitatively
how
users
feel
about
our
new
designs
and
we
got
issue
a
score
of
80.42,
which
is
an
A
minus
by
yoga,
systematic,
which
was
really
great,
even
though,
because
we
didn't
have
that
many
participants.
It's
not
super
statistics,
significant,
it's
still
very
meaningful
for
us
and
it's
worth
mentioning
that
the
original
interface
had
an
overall
score
of
72.92.
G
But,
of
course,
you
guys
have
more
participants
and
overall,
like
a
bigger
scope,
or
you
were
to
see
more
stuff
than
or
narrow
down
scope,
so
yeah
overall,
we
just
tested
the
ability
to
find
a
template
for
the
pipeline.
We
just
said
just
general
navigation
and
being
able
to
find
all
the
features
of
the
recent
or
the
most
recent
deployed
pipeline,
so
yeah.
Overall,
our
final
takeaways
were
the
fact
that
final
templates
was
much
easier.
We
were
new
design.
All
the
participants
were
able
to
complete
the
task
in
less
than
10
seconds,
which
is
great.
G
We
also
found
that
the
rewarding
and
the
Sorting
picture
was
a
little
bit
confusing.
The
way
that
we
had
different
ideas
about
the
words
of
use
would
mean
for
the
users
and
the
hierarchy
of
the
new
navigation
page
that
we
came
up
with.
It
also
took
a
little
bit
of
time
to
get
used
to
for
them
yeah.
So
overall,
the
final
takeaways
that
we
can
take
from
this
last
front
of
usability
testing
that
we
did
was
that
the
way
that
we
came
up
to
find
the
templates
are
super
successful.
G
Maybe
we
should
just
review
suggested
popular
and
recent
as
the
keywords
that
we
use
for
the
Sorting
once
we
were
in
that
template.
Pop-Up,
then
on
the
page,
for
the
navigation
needs
to
be
tuned
to
match
the
mental
models
of
our
users
a
little
bit
better
and
also
in
terms
of
what
we're
actually
testing
with
the
next
prototype
should
have
more
interactions
and
more
happy
paths.
G
We
as
designers,
kind
of
expected
the
users
to
go
into
this
one
direction
and
when
users
were
clicking
on
different
buttons
and
different
options
that
we
didn't
account
for
that
they
just
kept
trying
to
like,
or
we
didn't
actually
get
that
much
Insight
from
them,
because
we
didn't
keep
going
through
those
spots
and
overall,
we
think
there's
a
lot
of
room
for
improvement
that
went
beyond
beyond
our
onboarding
scope,
but
we
would
love
to
give
that
feedback.
At
the
end.
F
And
here
we
have
the
original
template
browser
layout,
where
the
users
would
have
to
click
and
open
a
new
tab,
and
we
found
that
this
actually
disrupted
the
user's
workflow
a
little
bit.
So
within
our
new
design.
We
wanted
to
kind
of
reduce
that
by
containing
the
template
browser
within
the
same
page
and
as
you
can
see
here,
with
the
drop
down
menu,
that
has
the
option
to
expand
into
a
do
a
pop-up
window.
This
hop
this
helps
the
user
quickly
preview
and
select
some
of
the
most
common
languages.
F
And,
lastly,
we
believe
that
it
will
be
beneficial
to
redesign
the
navigation
bar
to
decrease
nesting
navigation
menus,
as
a
lot
of
users
gave
the
feedback
that
they're,
seeing
things
on
the
left
that
they
don't
know
is
relevant
to
what
they're
looking
for
right
now,
which
kind
of
confuses
them
a
little
bit
with.
That
being
said,.
F
Cool
and
yeah
with
that
being
said,
we
would
like
to
thank
the
gitlab
team
for
giving
us
this
opportunity
to
learn
and
work
in
such
a
cool
environment,
and
especially
Gina
and
Ben,
for
guiding
us
along
this
project
being
so
responsive
and
being
so
helpful
teaching
us
so
much.
But
yeah
we'd
also
like
to
thank
the
Tufts
engineering,
psychology,
human
facts
Department,
but
more,
but
more
still,
good
lab.
Thank
you
and
any
questions.
I
D
I
think,
throughout
our
process
we
got
to
kind
of
do
an
initial
test
with
the
two
different
options
and
we
found
that
like
in
order
to
give
the
user
more.
We
kind
of
combine
the
two.
So
we
put
the
drop
down
that
led
into
the
pop-up
and
decided
to
go
ahead
and
test
with
that,
especially
due
to
the
limited
time
it
would
have
been
harder
to
kind
of
get
each
participant
to
do
the
both
prototype.
So
we
just
decided
to
move
forward
with
one.
J
E
I
think
that
one
thing
I
was
personally
surprised
about
is
I
had
never
conducted
a
user
test
with
a
Target
user
for
any
of
my
projects
before
and
questions
that
we
had
put
into
the
script
that
we
amongst
ourselves,
we
were
thinking.
Maybe
this
is
Trivial
I,
don't
know
whether
we
should
ask
them
what
recent
means
for
like
a
sorting
function.
It's
so
obvious
like
it.
H
H
They
were
their
like
mindset
of
what
they
expected
things
to
happen
were
they
were
kind
of
fixed
in
the
tools
that
they
were
used
to,
and
users
who
were
maybe
newer
or
less
experienced
actually
had
an
easier
time,
because
they
didn't
really
have
a
concept
of
what
it
was
supposed
to
be
like.
Yet
so
I
thought
that
was
kind
of
a
surprising
thing.
A
D
Think
a
lot
of
us
like
understanding
what
the
user
wanted
and
even
during
the
usability
test,
some
of
the
questions
or
points
that
the
users
would
bring
up
like
I
did
not
know
the
answer
to
because
I
didn't
know
like
the
specific
context
of
how
they
would
be
dealing
with
this.
So
that's
something
that
we
kept
on
learning
throughout
the
semester
more
and
more
on
how
someone
would
use
the
product.
G
G
That
was
like
super
interesting
and
not
something
that
I
had
thought
about
before,
even
like,
not
even
through,
like
this
over
engineer,
I
or
like
the
design
of
their
eye,
so
being
able
to
think
more
about
why
these
tools
have
this
features
and
the
way
they
have
them
was
like
super
challenging
for
me,
because
I
already
thought
I
had
an
idea
what
they
were
for,
but
a
lot
of
my
preconceptions
were
changed
or
like
I
felt,
like
I
learned
more
about
cicd.
Overall,
through
this.
E
I
found
it
difficult.
Even
once
we
narrowed
our
scope
and
we
had
between
the
group
members,
a
general
understanding
of
cicd
enough
to
improve
the
onboarding
process
in
some
ways,
especially
when
it
came
to
navigation.
We
realized
that,
even
though
we
had
narrowed
our
scope
that
it
would
inevitably
impact
on
users
of
all
levels,
not
only
like
our
Target
users,
but
like
new
users,
as
they
were
actually
using
the
product
the
product
in
their
day-to-day.
E
So
without
being
able
to
do
like
a
contextual
inquiry
or
really
understanding
what
the
day-to-day
tasks
of
these
developers
look
like.
We
weren't
able
to
be
totally
confident
in
our
solutions
for
navigation,
because
we
didn't
know
how
they
would
pan
out
long
term
for
someone
who's
using
it
day
to
day.
F
Yeah
and
I
guess
from
my
experience,
I'm
just
thinking
about
the
the
part
where
I'm,
personally
learning
and
onboarding
into
cicd
in
gitlab
and
we're
reading
the
tutorial
I
think
it
was
creating
your
first
Pipeline
and
as
a
person
who
has
well
I
I've
taken
two
CS
classes
as
well,
but
no
idea
about
cicd
I
was
reading
it
and
I
was
like
okay.
So
you
need
a
runner.
F
What's
a
runner
I
clicked
that
it
was
a
different
link
and
then
it
gave
me
a
list
of
runners
or
whatever,
and
then
it's
like,
if
you
don't
have
a
runner,
you
need
to
install
it
on
your
local
machine
and
then
I
went
to
install
it
and
then
I
installed.
Git.
Somehow
and
then
I
went
back
to
the
tab
from
before,
and
it
said
oh,
but
we
have
Runners
online.
So
you
don't
need
it
and
I
was
like
wait.
So
what
did
I
just
do
and
I
think
that
tutorial
part
was
the
one.
G
G
D
Thank
you
all
so
much.
We
really
appreciate
you
all
taking
the
time
yeah,
so
we'll
share
the
slides
with
Gina.
Also
we
have
our
linkedins
linked
here.
If
you
want
to
connect
with
us
and
ask
us
any
more
questions,
we'd
be
happy
to
help
and
we
also
attached,
like
all
of
the
things
that
we've
worked
on
this
semester.
If
you
want
to
take
a
deeper
dive,
there's
a
lot
so
great
work.
Thank
you.
So
much.