►
From YouTube: Digital Experience Retro - Sept 23, 2021
Description
Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
Digital Experience Retro Doc: https://docs.google.com/document/d/1kMNiUF2UDuSrMDuzLyRi8OEhVxry_MJoYi38RmmWafY/edit?usp=sharing
A
Hi,
everyone
welcome
to
the
digital
experience
teams,
retro
meeting
we'll
go
over
what
went
well
and
things
to
improve
on
that.
We
learned
from
the
last
two
week,
iteration
first
up
for
things
that
went
well.
Tyler
is
the
first
one.
B
I
think
we're
all
feeling
it.
I
think
this
is
the
perception
from
outside
as
well.
I
think
we
just
did
an
excellent
job
with
a
disrupted
iteration
with
a
non-standard
schedule,
just
lots
of
yeah
I'd
like
I
think
everyone
should
feel
really
good
about
the
work
that
they
did.
I
know
I
am
and
like
we
had
our
green,
yellow
red
check-ins
and,
like
everyone's
feeling,
green
and,
like
you
know
this.
C
B
The
way
to
work
every
single
iteration
for
all
of
your
working
life.
But
if
it
feels.
C
B
B
Oh,
I
did
that
last
week,
jeez
so
like
I
also
don't
I
I
think
the
other
videos
like
I
don't
have
a
very
critical
reflections
either
on
the
last
two
weeks
because,
like
I
like
didn't,
have
time
to
critically
reflect
on
things
which
is,
you
know,
part
of
why
you
probably
can't
do
that
every
single
time.
But
it's
it's
nice
to
get
a
lot
of
stuff,
it's
nice
to
get
a
high
volume
of
like
high
quality
stuff
out
the
door,
and
I
think
that's
precisely
what
we
did
so
congrats
to
everyone
for
doing
it.
D
I'll
hop
in
next,
I
think
the
migration,
the
customer
reference
pages
went
well,
there's
a
good
workflow
between
ux
and
engineering.
I
shifted
tactics
with
this.
I'm
usually
advocate
for
minimal,
viable
mvc
and
like
one
mr
per
migration,
and
I
threw
that
out
the
door
for
this
one.
I
was
like
there's
too
many.
D
E
I
guess
I'm
up
next
yeah,
so
I've
noticed
a
bunch
of
mrs
this
last
iteration,
where
we've
been
putting
more
data
into
yaml
files
and
I
think
it's
a
huge
plus
because
if
we
migrate
the
page
over,
we
just
have
to
build
the
page
without
any
data,
and
it
just
works.
So
let's
keep
doing
that
and
then
who
knows
later
down
the
road
with
like
internationalization
and
stuff
everything
will
be
in
the
data
files,
so
I'll
just
keep
doing
that.
E
Yeah,
I
guess
we're
going
on
to
things
to
improve
on
parker.
Do
you
want
to
kick
it
off.
D
B
I
agree-
I
I
think
you
know
not
like
highest
volume
of
work,
but
a
lot
of
that
volume
was
like
reworking
things
that
got
out
the
door
that
were
not
like
ready
to
be
out
the
door,
so
I
think
you
know
like,
but
I
also
think
that,
like
probably
the
crossroads,
we're
sitting
at
in
this
moment,
is
that
that's
to
be
expected
and
like
not
it's
like
not
because
necessarily
like
our
team
was
like.
Okay,
like
let's
shift
our
mode
to
working
fast
and
that's
like
what
we
should
be
doing.
B
It's
just
like
what
we
have
to
so
I
think
you
know
this
is
a
good
moment
for
people
who
are
watching
outside
this
team
or,
like
other
people,
we
collaborate
with
for
like
us
just
to
like
make
note
of
it
that,
like
we
are
like
indexing
on
speed
and
not
necessarily
on
perfection.
It's
not
it's
not
low
quality,
it's
not
like
lower
quality,
but
it
is
like
fewer
checks
like
I
I
did.
B
I
released
a
ton
of
mrs
this
time
around
without
like
code
review,
because
I
was
like
look
like
if
someone
told
me
like
change
this
code.
I'd
be
like
no
I'd,
be
like
I'm,
not
gonna,
because
it's
gonna
take
too
long,
and
so
I
did
a
lot
of
just
like
design
reviews.
I
was
like
okay,
like
someone
look
at
this
and
like
did
this
like
meet
the
meet
the
list
cool,
it's
going
out
the
door.
So
I
think
this
is
just
you
know
if
you're
watching
out
there
like
next
like
little.
B
While
I
think
this
will
be
our
team's
operating
mode
and
it's
worth
it
if,
if
there's
something
that
like
needs
to
have
all
the
eyes
dotted
and
t's
crossed
before
it
like
gets
shipped,
I
think
we
should
like
be
explicit
about
it
and
be
like
this
is
a
thing
that
shouldn't
move
fast
at
the
expense
of
like
at
the
expense
of
thoroughness.
Right,
because
I
think
our
default
mode
for
a
little
while
is
going
to
be
fast
like
fast,
rather
than
thorough.
B
So
yeah,
I'm
I'm
with
you,
but
and
like
I'm
cool
about
doing
it
and
it's,
it
seems
like
from
what
I've
seen
like
feedback
and
responses
and
like
people
like
you
know,
talking
to
us
like
every
everyone
else
is
in
that
same
place,
and
everyone
is
like
accommodating
and
it's
like
make
sure
you
don't
mess
up
the
big
stuff
and
don't
sweat
the
little
things
and
just
keep
on
moving
through
right.
C
Oh,
I
guess
I'll
vocalize.
I
just
added
a
note
that
you
know
I
finally
remember
clean
up
over
sign-off.
Thank
you
barker.
You
always
say
that
all
the
time,
so
I
just
want
to
remind
you
that
that's
we
value
that,
but
then
I
added
a
sub
note,
because
I
realized
that
often
we
can't
go
back
and
iterate.
So
that
is
something
to
improve
on
we.
We
are
moving
fast
and
sometimes
we
can't
look
back
so
something
to
take
into
consideration.
A
I'm
ready
as
I'm
talking,
but
I
think
the
pricing
page
is
a
really
good
example
of
what
we
can
do
like
what
we
can
accomplish
when
we
actually
do
go
back
and
iterate
on
something
and
really
spend
some
time
with
it.
It's
gone
like
it's
made
a
lot
of
improvements
in
the
last
eight
months
or
so
may
be
really
cool.
We
could
do
that
with
other
pages.