►
From YouTube: Digital Experience Sprint Retro 2021-07-01
Description
Sprint Retro Doc: https://docs.google.com/document/d/1kMNiUF2UDuSrMDuzLyRi8OEhVxry_MJoYi38RmmWafY/edit?usp=sharing
Digital Experience handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
Inbound Marketing handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/
A
Hey
welcome
to
the
digital
experience
retro
on
our
iterations.
This
is
retro
17
for
the
cycle
from
june
21st
of
2021
to
today
july,
1st
of
2021
it'd
be
wild
if
it
wasn't
of
2021
right,
it's
a
super
long
sprint.
It's
just
like
2022..
Anyway.
Sorry
didn't
land
joke,
didn't
land,
but
we'll
go
on
to
things
that
went
well
in
the
agenda.
A
A
I
really
wanted
to
get
the
comparison
infographic
like
ready
for
review
like
yesterday,
so
I
could
like
release
it
today,
but
the
nice
thing
is
that,
like
we
spent,
I
think
we
did
a
really
good
job
of
like
planning
and
appropriately
scoping
the
like
bigger
project
that
it's
a
part
of
so
that,
even
though
I'm
behind
in
this
like
piece
of
it,
the
overall
goal,
we're
super
on
track
for
tina's,
ahead
of
schedule
and
so
yeah
like
I'm
feeling,
I'm
feeling
good
about
that.
It's
just
one
of
those
things.
A
I
think
there's
like
a
like
a
emotional
feeling
of
like
it
feels
good
to
get
stuff
out
the
door,
and
it
feels
bad
to
like
not
do
that
right,
like
I'll,
probably
honestly
finish
it
between
today
and
tomorrow,
because
I
have
a
bunch
of
focus
time
tomorrow,
but
it's
like
didn't
hit
it
for
wednesday.
I
couldn't
say
it
in
the
release,
video
which,
but
either
way,
I'm
still
feeling
good
about
it
overall,
and
I
think
it's
I
feel
like
that
went
well.
B
Yeah,
so
I
spent
a
real
good
chunk
of
last
week
like
four
days
cleaning
up
the
slippers
figma
just
to
make
sure
everything
was
accurate
to
where
we're
at
now.
So
this
kind
of
all
the
designs
have
been
built
through
attrition
since,
like
october,
it's
natural
that
things
have
varied,
and
you
know
we
missed
some
stuff
along
the
way,
so
just
making
sure
like
we're
using
mobile
fonts
on
mobile,
that
we're
pulling
through
the
slippers
colors
rather
than
just
using
the
hex
codes.
B
A
Yeah
that
had
been
my
follow-up.
That
makes
sense
like
this
is
like
like
cleaning
up
stuff
that
had
been
incorrect
a
little
bit
and
then,
but
thinking
about
the
like
getting
stuff
in
line
with
like
storybook
and
like
what
we're
building
on
the
dev
side.
I
know
like,
like
the
type
style
names,
but
it
sounds
like
tina
and
laura
are
working
on
this
like
in
figma.
A
A
lot
of
type
styles
will
be
called
like
h1,
but
they
like
in
our
tailwind
config
that
the
sizing
that
it
corresponds
to
is
like
size,
xl
or
whatever,
like
those
things
seem
to
be.
Are
at
this
point
I
just
matched
the
values
rather
than
looking
at
the
names,
but
it
sounds
like
you've
got
that
covered.
So
I'm
super
excited
about
that.
Thank
you
for
all
that
work.
C
Yeah
laura
just
to
add
to
that
laura
has
volunteered
to
work
with
me
on
either
most
likely
aligning
figma
to
storybook,
but
we're
going
to
just
probably
create
a
spreadsheet
figure
out
the
labeling
for
those
we'll
we'll
create
that
spreadsheet
and
then
include
steven
and
jess.
To
add
to
that-
and
I
want
to
mention
also
that
javi
is
working
on
aligning
the
cards
to
figma
in
storybook.
So
there
is
a
bit
of
code
change
there.
B
Yeah-
and
there
were
a
couple
small
new
things,
so
we
added
out
a
brand
new
type
font,
whatever
it's
called
and
then
maybe
that
can
be
grouped
in
with
what
tina
and
laura
are
doing,
realize
we're
using
a
couple
different
link,
styles,
and
I
think
maybe
one
of
them
can
be
deprecated.
But
I
don't
know
how
much
work
that
would
be
on
the
on
the
engineering
side
added
glitter
as
a
component.
B
D
C
D
D
It
is
something
to
keep
an
eye
on
and
probably
not
something
that
you
want
to
put
by
the
wayside
too
long
and
because
the
further
out
you
push
the
decision
or
something
like
that,
the
more
expensive
it
gets,
because
you
just
gotta
have
to
go
back
and
change
things
and
just
something
to
be
aware
of.
That's
all.
E
Yeah
regarding
like
brand
color
changes
like
the
way
that
tailwind
is
set
up
now,
is
that
as
long
as
we
don't
change
the
variable
names
of
things,
the
css
classes
will
be
exactly
the
same.
So
if,
as
long
as
we
change
hex
values
within
existing
colors
within
a
storybook,
sorry
within
tailwind,
sorry,
we
should
have
no
issues
with
like
the
engineering
side
of
things.
D
Yeah,
that's
what
I
thought
too,
as
long
as
we're
not
actually
adhering
to
anything
specific
that
they've
given
us,
which
I
don't
think
they
have.
We
just
need
to
take
abstract,
hex
values
and
use
them
to
apply
to
whatever
contrast,
color
that
we
have
or
con
or
whatever
the
version
of
the
color
that
we
have
is
so
kind
of
works.
Like
a
token,
basically,
so
it's
abstract
from
any
kind
of
naming
so
yeah,
it's
not
too
much
trouble,
but
I
don't
think
it's
anything
that
we
need
to
be
too
concerned
about
for
the
minute.
A
D
Yeah,
just
just
that
now,
as
we're
like
you
know,
we
built
a
design
system.
It
got
up
to
a
certain
place.
We
began
to
use
it
and
as
we
go
and
it's
just
the
nature
of
systems
as
you
go
variables
can
be
entered,
can
kind
of
enter
the
fray
as
you
go.
People
can
use
different
line
heights
for
staying,
not
true
in
tension
or
any
kind
of
mass,
but
it
just
happens.
D
So
tech
and
design
that
builds
up-
and
it
just
becomes
a
big,
a
big
issue
for
us
in
the
future
and
then
that
so
as
opposed
to
doing
one
sprint
or
two
sprints
to
fix
things,
you
allocate
a
little
bit
of
time
to
just
like
do
a
bit
of
housekeeping
on
things.
Making
sure
stuff
is
all
good,
because
it's
our
job
still
to
sort
of
maintain
this,
keep
it
up
to
a
certain
standard
and
make
sure
that
it's
not
going
down
any
roots
that
we
don't
want
it
to
go
down.
D
So
it's
just
an
idea
to
maybe
utilize
ui
to
code
a
bit
more
about.
Can
we
make
sure
that
things
are
still
aligning
between
figma
and
between
the
repo
and,
if
they're,
not
what
action
items
can
we
take
from
that
to
make
sure
that
we're
keeping
things
on
track
set
up
small
little
slide
issues?
Maybe
we
can.
I
know
nathan
did
a
lot
of
work
on
streamlining
tags
and
things
like
that
in
in
gitlab
itself.
D
So
maybe
we
could
have
one
for
like
slippers,
maintenance
or
something
like
that
to
just
make
a
change
or
make
an
edit.
Not
to
add
any
more,
that
would
just
take
a
load
away,
but
it
could
be
an
idea
to
keep
keep
on
top
of
things
as
we
go,
because
we
want
to
keep
the
system
healthy,
especially
as
we
get
further
down
the
line
of
bigger
numbers.
And
then,
when
teams
begin
to
use
it,
we're
gonna
have
to
have
things
reinforced
to
make
sure
that
they
don't
break.
A
Makes
sense,
I
think
that
I
think
it's
a,
I
think,
adding
something
like
that
to
the
ui
to
code
meeting
like
a
prompt
or
like
a
section.
That's
like
hey
like
what's
changing,
or
what
has
slipped
through
cracks
like
that
sort
of
thing
where,
like
it
can
be
a
lot
more
collaborative
between
design
engineering
would
be
good.
I
walking
away
from
the
last
one
we
had.
I
was
like
oh
man.
This
was
like
an
engineering
meeting
like
you
know,
which
I
think
is.
I
think
it's
like.
A
I
would
also
love
to
hear
you
all
talk
about
design
as
well,
like,
I
think
it's
good,
it's
just
good
to
like
it's.
It
is
collaborative
to
like
listen
to
what's
going
on,
but
I
know
that
that
meeting
is
like
it's
like
ui
to
code
right,
so
I
want
to
just
make
sure
that,
like
anything,
we
can
do
like
prompts
or
something
like
that.
Just
a
touch
of
structure.
A
D
Yeah
and
there's
no
harm
if
those
meetings
take
a
more
engineering-heavy
approach,
kind
of
a
good
thing,
because
then
it
means
we
have
a
system,
that's
built
up
to
a
certain
standard,
and
it's
quite
big.
So
that's
kind
of
the
nature
of
the
beast
and
every
now
and
then,
if
there's
anything
new
that
needs
to
be
added
to
it
from
design,
we
can
obviously
bring
it
up
there.
But
I
guess
it
would
be
to
optimize
that
meeting
a
bit
more
and
if
we
don't
feel
it's
optimized.
D
How
can
we
make
sure
that
it
sort
of
speaks
to
the
needs
that
we
have
as
the
system
grows,
as
our
team
uses
the
system?
Another
teams
use
the
system
and
there
might
be
further
discussion
as
we
begin
to
open
up
to
other
teams
of
how
we
support
them.
What
channels
of
communication
we
want
to
have,
we
don't
just
want
to
use
like
an
on-call,
random,
slack
messages
falling
in
left,
right
and
center,
so
just
things
that
we
can
sort
of
use.
That
means
to
optimize
for.
A
E
F
Is
our
yeah
they're
being
used
right
now,
but
the
first
iteration
that
that
michael
and
I
have
gone
through
we're
actually
removing
them
so
keep
using
them.
Pretending
like
this
is
gonna
happen
and
then,
when
we're
in
a
good
place,
michael
and
I
will
share
all
the
labeling
with
everybody
and
and
we'll
go
over
a
couple,
iterations
of
it
and
then
yeah,
hopefully
it'll
be
a
lot
simpler,
but
right
now
yeah,
I
continue
using
them.
I
think
they're
used
on
one
of
the
kanban
boards.
E
G
Yeah,
it's
good
we're
talking
about
health.
Something
really
well
is
well
not.
We
had
some
like
caching
issues
with
the
nav
change
and
we
were
able
to
use
that
as
an
opportunity
to
advocate
for
repository
health
days,
which
I'm
so
excited.
It's
it's
really
a
great
opportunity
for
everyone
on
the
team
to
sit
back
for
a
day
and
work
on
what
they
think
is
important,
which
I
think
is
great,
because
we
all
have
like
different
thoughts
and
we're
all
going
to
come
at
it
from
a
different
angle.
A
C
C
I
looked
at
it
and
I
was
like
you
know
what
we
designers
can
use
this
too,
and
then
I
brought
it
up
on
my
101
with
michael
and
he's
supportive,
and
you
know
I
think
justin
stephen
can
and
I
can
coordinate
on
what
we
can
do
for
our
own
kind
of
design
health
day.
I
don't
know
what
to
call
it.
I
mean
our
design
assets
are
in
a
repo
anyway,
so
it
can
be
under
the
same
umbrella.
G
D
A
You
go
another
silver
lining
about
the
caching
issues.
I'll
be
brief,
but
if
folks
watching
this
want
more
details,
like
I
have
a
hypothesis
haven't,
had
a
chance
to
verify
this.
I
think
what
we
saw
on
the
caching
issues
has
been
an
existing
problem
for
a
long
time,
and
I
think
that
the
nav
changes,
because
they
were
so
big
and
like
global
and
obvious
for
when
things
were
like
broken
in
the
cache,
like
surfaced,
a
deeper
problem
that
we've
had
in
the
past.
A
So
just
as
part
of
like
you
know,
silver
lining
of
the
caching
issues,
the
repository
health
stuff,
like
I
think
that
this
problem
has
existed
and
like
we
just
like,
got
the
squeakiest
wheel.
We
possibly
could
have
by
launching
this
huge
nav
change
right,
and
I
think
it
just
gave
us
like
a
really
good
something
a
canary
in
a
gold
mine,
sort
of
thing
so
anyways.
I
just
think
that
I
think
that's
a
net
positive
along
with
this,
with
the
health
days.
A
C
I
responded
to
a
lot
of
questions
that
I
had
already
worked
out,
but
I
didn't
document
and
that
wasted
some
of
tyler's
time,
and
so
it's
like
a
good
reminder
at
how
valuable
those
readmes
are
to
engineers
so
yeah,
I'm
making
a
commitment
to
add
readme's
early
on,
even
though
I
anticipated
change
like
I
didn't
add
them.
I
did
have
a
reason.
It
wasn't
because
I
was
necessarily
being
lazy.
I
just
the
pages
were
having
user
testing
running
on
them
and
I
was
like
I
mean
this
is
all
going
to
change.
A
And
I
think
you
had
flagged
that
to
me
as
well,
like
I
wasn't
surprised
right
like
I
I
was
in
the
same.
I
was
like
oh
yeah,
like
it'll
change
and
then
like
we'll
just
get
the
info
when
it's
settled
and
then
we
just
it
the
synchronization
of
it
was
like.
I
ended
up
needing
the
answers
faster
than
we
would
have
thought
so
yeah,
but
it
worked
out
great
and
you
were
always
very
responsive
to
questions.
So
thank
you,
jess.
I
think
you're
up
next.
B
Yeah
so
kind
of
adding
on
to
what
I
was
talking
about
in
the
things
that
went
well
going
through
the
figma
slippers,
realizing
like
we're,
not
really
nesting
our
components,
the
way
we
should
be
like.
If
we
have
a
link
within
a
card,
we
should
be
going
back
to
the
original
link.
You
know
and
we're
not
really
using
auto
layout
like
we
should
be,
and
I'm
well
auto
layouts
my
nemesis.
I
I
don't
really
understand
how
it
works,
I'm
trying
so
I
know
I
need
to
get
better
at
that.
B
So
I
just
kind
of
like
noted
it
as
like.
We
still
need
there's
a
lot.
We
still
need
to
do
on
the
slippers.
Stigma
learn
flexbox,
but
I
it
was
just
like
too
much
to
do
in
one
week,
so
I'm
kind
of
like
okay,
that's
what
you
do
for
not
just
me,
but
for
all
the
designers
on
our
team
to
figure
out
how
to
do
it
and
be
better
about
like
knowing
like.
If
we
have
a
component,
we
need
to
go
back
to
the
original
one.
B
D
It
might
be
an
idea
and
to
lean
on
the
product
team
for
that
they
are
very
proficient
with
that.
It's
just
hard
to
get
them
all
in
the
one
spot,
because
they're
sort
of
scattered
around
timelines
and
then
the
one
meeting
that
I
did
get
or
do
get
invited
to
happens
at
7,
00
or
7
30
on
a
thursday,
which
would
mean
your
day
starts
early
and
it's
extra
long
meetings,
but
you
do
get
to
find
out
a
little
bit
they're
so
advanced
with
the
product.
D
The
stuff
that
they're
talking
about
is
really
really
my
new
compared
to
the
amount
of
work
that
they've
done,
but
they've
been
added
for
two
years
or
maybe
more,
but
their
sigma
file
is
in
pretty
good
shape
and
jeremy
elle
is
pretty
proficient
at
figma,
so
cool
sorry
mike
really
broke
there.
I
would
have
been
embarrassed,
but
yeah
he's
good
to
reach
out
to
and
always
very
receptive
and
the
team
over.
There
is
pretty
good.
So
it
could
be
an
idea
to
try
and
get
some
of
their
knowledge.
D
C
D
A
B
G
A
B
G
A
A
I
think
I
think
a
big
challenge
is
making
sure
that
we
have
like
a,
and
we
might
not
have
it
for
this
upcoming
one
of
like
a
prioritized
list
of
what
we
should
work
on
to
communicate
like
what
should
be
done
and
then
also
communicate
what
you
are
doing
right.
I
think
maybe
that's
the
missing
piece,
but
I
don't
know
if
we
have
that
I
do.
A
I
actually
already
have
like
a
couple
things
lined
up
for
next
iteration
that
I
was
just
going
to
do
anyways,
but
I
may
call
them
a
health
day
task
like
the
like
the
bootstrap
upgrade,
I'm
going
to
call
it
health
day,
because
it's
like
it's
a
vulnerability.
We
have
a
thing
like
you
know.
Just
do
it
anyways,
but
I
don't
know
if
we
have
a
better
list
that
we
could
pull
from
to
begin.
A
F
G
A
Nathan,
I'm
gonna.
If
you
don't
mind,
I'm
gonna
add
this
action
item
for
you
since
you're
already
doing
all
this
work
with
michael
on
the
label,
whatever
that
ends
up
looking
like
action
item
for
backlog,
like
you
know,
obviously
collaborative,
but
I
figure
you're,
the
a
good
person
just
to
start
it
with.
If
that's
cool
with
you
yeah
that
works,
sweet.