►
From YouTube: Digital Experience Retro Video - Aug 12, 2021
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/
A
B
Yeah,
I
just
want
to
comment.
I
think
it
was
tuesday.
We
had
that
ui
to
code
meeting
and
it
was
amazing
if
you
haven't
read
through,
I
think
our
documentation
from
that
meeting.
I
suggest
you
do
yeah.
I
love
the
collaboration.
I
love
like
the
back,
not
back
and
forth,
but
different
point
of
views
and
I
actually
learned
a
lot.
It
felt
like.
I
was
back
in
the
office
and
we
were
all
in
a
room
kind
of
brainstorming
on
like
a
whiteboard,
and
I
want
more
of
that
anyway.
A
B
A
A
D
A
Yeah
and
it
shows
kind
of
a
low
ego
which
is
nice
but
cool,
okay,
similar
vein,
but
this
iteration
really
showed
me
like.
Oh
yeah,
we've
got
like
a
lot
of
skill
on
this
team.
Like
we've
got
people
who
have
experience
in
a
ton
of
different
tools
from
one
trust
to
design
system
to
talent,
to
user
journeys
to
data
like
so
many
things
that,
like
whenever
someone
says
hey,
does
anyone
know
about
this
thing?
There's
someone
on
our
team.
That's
like!
A
C
One
I
was
just
like.
I
feel
like
every
single
person
I
talk
to
at
this
company
like
is
interesting
and
cool
and
trying
to
do
like
their
best
work
in
a
way
that,
like
I
haven't
experienced
like
coming
from,
like
a
government
contractor
background,
where,
like
no
one
was
trying
to
do
their
best
work,
which
is
totally
just
cool
too,
you
know,
like
that's
fine,
you
know,
but
like
it's
just
a
very
different
vibe
and
I
feel
like
every
single.
I
do
like
the
donut
chats.
C
D
C
Just
across
the
whole
company,
like
it
just
feels
like
anyways
yeah,
I
just
strongly
agree.
Definitely
about
our
team,
but
also
like,
I
think,
like
d
lab,
is
a
cool
place
to
work
for
a
lot
of
reasons,
but
one
of
them
being
in
particular.
That,
like
I
think
everyone
who
works
here
so
far
that
I
have
spoken
with
is
like
really
trying
their
best
to
be
like
really
good
at
what
they
do.
And
that's
really,
I
think,
that's
unique.
E
Yeah
that's
hard
to
follow
big
plus
one
agree
with
everything
you
said
tyler
from
my
perspective.
What
went
well
is,
I
know
I
know
we.
We
did
have
a
lot
of
synchronous
meetings
over
the
past
few
weeks,
which
can
can
be
difficult
to
manage,
but
also,
I
think
that
the
kickoffs
were
helpful
for
q3
and
probably
resulted
in
reducing
other
meetings
later
down
the
road.
So
I
feel
confident
about
rq3
initiatives
and
I'm
pretty
excited
about
them.
C
Yeah-
and
it's
related-
I
only
put
this
in
things
to
improve
on
because
it's
the
only
place
like
I
don't
know
it's
not
really
up.
I
think
it's
in
the
between
of
these
two
things
I
I
feel
like
and
I'm
pretty
sure
if
we
looked
at
calendars,
this
would
be
true.
I
feel
like
there
have
been
more
synchronous
meetings
in
probably
the
past
two
to
four
weeks
than
usual
and
tina.
I
agree
like
I,
I
have
enjoyed
pretty
much
all
of
them.
C
I
don't
feel
like
I've
been
in
useless
meetings,
so
maybe
that's
perfectly
fine.
I
just
I
I
am
aware
of
like
I
really.
I
really
like
one
thing
about
working
here
like
I
like
the
async
first,
I
like
the
handbook
first,
like
those
things
are
important
to
me
and
I
think
they're
important
about
like
doing
remote
work
really
well
so,
like
only
as
a
yellow
flag
of
like
hey
like.
C
Are
we
missing
so
like?
Are
we
missing
opportunities
to
do
things
asynchronously
that
that
really
could
be?
It
could
have
been
done
asynchronously
and
perhaps
it
sometimes
feels
better
like
does
it
feel
better
to
have
a
meeting?
But
it's
not
like
aligned
with
our
values,
even
like
I
like
I,
I
don't
know
like
looking
back
on
any
of
the
meetings.
I
can't
think
of
one
that
I
was
like.
Oh,
I
wish
that
didn't
happen
right.
C
C
But
it's
not
to
say
that
I
felt
like
oh.
I
wish
I
didn't
have
this
meeting.
I
just
like
it's
one
of
those
things
where
it's
like,
like
it
was
fun
and
good
use
of
our
time,
but
was
it
like
part
of
the
values
or
like?
Could
we
have
done
it
asynchronously
with
like
an
issue
and
like
talked
it
through
because
you
know-
and
I
don't
think
we
knew
at
the
time
because
it
ended
up
being
easier
than
we
thought
it
would
be.
A
Yeah,
I
think
I
think,
a
lot
of
it
felt
like
quarter
kickoff
meetings.
I
think
maybe
a
thing
to
approve
on
this
has
been
kind
of
floating
around
in
my
head
about
this
particular
quarter.
Okrs
is,
we
all
seem
to
be
all
dris
on,
like
all
of
them
like
we're
all
do
your
eyes
on,
like
the
design
system,
one
and
we're
all
a
lot
of
us
are
do
our
eyes
on
the
pricing
iteration.
A
It's
like
it
just
so
we're
all
in
those
meetings,
instead
of
like
an
individual
being
directly
responsible
or
like
how
we've
been
doing
it
with
like
a
design
and
engineering
individual
being
responsible.
So
maybe
there's
a
way
to
like
clean
that
up
next
quarter
but
yeah.
I
I'm
hoping
that
was
just
like
a
beginning
of
quarter
kind
of
scramble
of
meetings,
because
I
also
feel
the
meetings
happening
a
lot,
a.
E
Lot
of
meetings,
I
have
a
point
on
that
too.
I
agree
that
a
lot
of
meetings
could
be
dealt
with
a
certain
asynchronously
and
not
just
you
know,
for
you
know
our
time,
but
also
for
documentation
and
transparency
purposes
like
I
can
think
of
a
couple
meetings,
one
specifically
that
tyler
and
I
had
on
a
project
where
it's
like.
Well,
then,
we
had
to
like
put
in
the
summary
of
that
meeting
into
issues
and
all
three
of
those
issues
could
have
just
been
async
issues.
E
B
But
there
was
a
lot
of
home
page
updates
last
week
like
I
did
the
banner
three
times,
and
I
know
it's
not
the
hardest
change,
but
it
is
the
most
viewed
page.
So
we
kind
of
want
to
make
sure
that
that,
like
the
pricing
page,
a
lot
of
the
high
traffic
pages,
don't
have
any
issues
with
them.
So
I
don't
know
I
I
just
would
like
an
easier
way,
maybe
to
update
the
banner
or
not
have
to,
which
is
why
I
brought
up
the
cms,
but
I
think
tyler
I'll.
D
C
I
agree
that
things
like
that
should
be
easy
to
change.
I,
the
homepage,
is
gonna,
make
it
to
the
new
repository.
That's
like
one
of
the
top
five
pages
we're
gonna
move
in
there.
I
think
I
think
some
of
this
will
be
alleviated,
because
the
build
step
on
that
will
be
faster.
So
if
you're
pushing
to
the
new
repository,
it
will
go,
live
extremely
quickly
or
it
will
be
in
review
apps
extremely
quickly.
C
I
think
you'll
have
you'll,
have
a
much
tighter
feedback
loop
on
that
in
general,
once
we
get
it
over
there
and
I
feel
really
strongly
about
that
being
like
resolved
in
that
way.
Past
experience
here,
sometimes,
but
also
in
just
other
companies.
I've
been
in
where,
like
I
have
like,
built
a
custom
cms
for
people,
because
I
was
like
hey
I'm
doing
like
a
dozen
content
updates
a
day
to
change
the
sentence
like
here's
a
cms.
C
My
past
experience
suggests
to
me
that
the
people
who
ask
you
for
copy
changes
12
times
in
one
week
will
ask
you
to
make
copy
changes
12
times
in
one
week,
because
also
when
they
have
a
cms
and
like
will
not
want
to
use
the
cms.
So,
like
I
agree,
let's
put
in
the
cms,
we
like
everything
should
be
in
the
cms
because
we
should
have.
We
should
decouple
our
like
information
layer
like
our
data
layer
should
be
totally
decoupled
from
the
markup
should
be
like.
C
C
Is
that,
like
the
people
who
have
asked
you
to
make
those
changes
would
not
use
the
cms
to
make
those
changes,
and
they
would
ask
you
it
might
still
be
easier
for
you,
because
you
would
have
a
cms
to
do
it
yourself
but,
like
I
would
like
put
money
on
a
bet
that,
like,
if
you
put
it
in
a
cms,
the
people
who
are
asking
you
of
this
will
not
use
it
yeah.
So
that's
I
just
like,
but
again
I
think,
it'll
solve.
B
D
Yeah,
I
just
wanted
to
say
yes
and
if
you
have
like
a
thing,
that's
like
you,
you
know,
so
I
I
I
think
I
agree
with
tyler,
mostly
that,
like
yes,
that,
like
you,
would
still
get
12
requests,
and
you
also
give
yourself
like
some
coverage
and
fodder
for
like
hey,
like
there's
this
thing
that
we
built
that,
like
our
team,
worked
on
that
you
can
self-serve
it
yourself,
here's
the
link
for
how
to
make
a
contribution
here
now.
The
question
is:
will
people
do
that?
D
You
know
if
you're,
the
only
person
that
knows
that
knows
how
to
change
the
homepage
banner
and,
like
everyone
is
only
going
for
you
like
that's
not
like
sustainable.
You
know
because,
like
if
one
day
you
leave
it's
like
all
right
like
who
updates
the
banner.
Now
it's
like
well,
the
question
is
like
you
probably
should
have
yourself,
but
anyway,
yeah.
E
E
I
think,
like
the
purpose
of
the
personalization
issue,
for
that
banner
hero
area
is
to
prevent
people
from
requesting
stuff,
because
it's
just
going
to
auto
generate
content
based
on
data.
I
mean
they're
still
going
to
be
obviously
requests,
but
there
could
be
like
one
area
where,
like
this
is,
you
know,
yaml
file,
the
cms
or,
however,
things
need
to
be
updated.
I
I
don't
know.
C
C
No,
because
we
don't
have
any
like
databases
here,
like
you
know,
moving
over
is
like
as
long
as
the
same
stuff
ends
up
in
the
browser
at
the
end
of
the
day,
like
you're
good,
to
go,
there's
some
build
step
things,
but
the
data
that
we,
the
personalization
data,
is
like
coming
from
it's
coming
from
a
script
tag
somewhere
so
it'll
be
we
have
to
ensure
that
we
include
it.
You're
like
we
need
to.
You,
know,
dot
the.
C
The
t's
there
but
it'll
it'll,
be
there
without,
like
there's
no
extra
lift
to
get
the
data
there,
but
tina
to
answer
your
question
we
well.
I
actually.
I
think
that
is
like
the
right
idea.
If
we
weren't
doing
the
new
repository,
the
problem
is
we're
gonna
just
have
to
cross
this
bridge
when
we
get
there,
which
is
that
netlify
cms
is
like
hooked
up
to
the
repository
as
it
is
to
the
website,
and
when
we
go
to
the
new
one
we
won't
be.
A
Yeah
I
brought
up
kind
of
a
an
interim
step
of
instead
of
trying
to
force
netlify
in
this
particular
situation
is:
can
we
get
a
yaml
file?
The
events
team
does
this
right.
Now
they
go
and
edit
the
events
yaml
file.
They
have
a
handbook
page
on
exactly
what
format
everything
needs
to
be
in
and
we
can
do
the
exact
same
thing
so
that
maybe
people
can
go
in
and
edit
their
own
homepage
banner
and
see
like
oh
this
pa
this
home
page
banner.
A
That's
currently
up
is
supposed
to
be
displayed
until
next
week,
like
that's
when
I'll
need
to
change
my
banner
so
like
have
people
kind
of
manage
the
banner
themselves,
I
don't
know
but
yeah,
maybe
there's
there's
a
little
baby
iteration.
We
could
do
in
the
meantime,
there's
some
comments
coming
in
some
yeses
yeah
yeah
cool,
so
we
can
look
into
that
yeah
and
then
no
other
comments
on
that.
I
think
tina's.
E
Got
next
one
yeah
just
again
for
things
to
improve
on,
and
I
did
talk
with
michael
about
this
on
our
101
about
how
to
improve
feedback
loops
from
cross-functional
partners.
They
don't
always
fit
into
our
milestones
into
our
iterations,
which
is
why
there's
can
be
some
spillover
and
so
that's
been
kind
of
a
hold
up
and
why
there's
been
projects
that
could
have
been
done
in
four
weeks
that
are
on
to
six
and
eight
weeks.
D
I
added
one
last
point
I
see
now
with
my.
I
have
like
an
extension
that
lets
me
see
how
much
time
is
left
in
meetings,
and
I
see
that
there's
21
minutes
left
in
the
retro
sync.
I've
noticed
that
we
have
tended
to
go
like
on
the
shorter
end
of
this.
Would
it
be
all
right
with
you
all
if
we
let's
say
I'm
trying
to
propose,
we
end
this
meeting
at
the
hour
like
five
before
whatever,
because
I
don't
think
we've
gone
like
the
full
to
12
20
and
like
essentially,
since
we
started.
A
Yeah,
I
I
think
I
own
the
keys.
So
if
we're
all
in
agreement,
we
can
certainly
try
it
out
this
quarter
and
if
we
find
ourselves
going
over
time,
move
it
back,
I
think
we're
yeah.
We
we've
been
pretty
brief.
I
feel
like
cool,
so
we've
got
some
action
items
coming
in.
I
don't
know
if
we
want
to
localize.
C
Yeah,
just
a
quick,
I
I
asked
nathan
volunteered
to
help
me
out
with
a
part
of
the
new
repository
next
iteration
cycle
and
I
had
like
really
hoped
to
have
like
a
write-up
of
like
here's,
what
I'm
looking
for
done
like
today
or
tomorrow,
I'm
just.
I
have
like
a
doctor's
appointment
tomorrow,
an
electrician,
so
I'm
just
feeling
like.
I
might
not
send
you
anything
until
early
monday
morning
at
the
latest,
so
just
wanted
to
give
a
heads
up
and
yeah
like.