►
From YouTube: Digital Experience Team Retro - Apr 8, 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/
Inbound Marketing handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/
B
Yeah,
I
said
this
this
morning
in
the
inbound
marketing
call,
it's
really
worth
repeating.
Thank
you,
lauren
tina,
I
think
in
terms
of
things
that
went
well,
this
iteration,
like
y'all,
just
like
knocked
it
out
of
the
park
really
making
this
work
easy
to
manage
conceptualize
and,
like
figure
out
like
how
to
move
the
ball
forward
on
the
event
templating.
So
just
thank
you
so
much
for
doing
that.
It's
like
made
my
day-to-day
so
much
easier.
Last
two
weeks.
C
Thank
you
tyler.
I'm
gonna
do
this,
so
this
sprint
is
my
first
sprint
on
storybook
and
I
really
want
to
say
thank
you
to
every
single
member
of
this
team,
because
when
I
was
about
to
start
last
week
monday,
I'm
like
oh
now,
I'm
about
to
do
storybook.
I
need
to
get
started,
so
I
was
disturbing
every
single
person
that
okay,
where
do
I
get
started?
What
do
I
do?
First?
C
C
I
can
do
this
all
week
and
everybody
put
me
in
a
good
mood
that
made
me
really
get
into
a
beast
mode
that
I
just
went
on,
crushing
everything
that
I
need
to
do
and
before
the
end
of
the
sprint,
I
was
so
comfortable
that
I
know
that
okay,
I
can
do
way
much
more
better
and
we
can
quickly
knock
out
a
lot
of
components
that
are
still
existing
on
fema.
So,
thanks
to
everybody
for
the
good
job
with
the
windows
keepers,
I
really
love
this.
It's
interesting.
D
I
just
wanted
to
call
out
that
if
you
had
any
feedback
or
things
that
things
that
were
like
weird
in
that
process,
I
think
there's
a
lot
of
things
that,
like
at
least
like
for
myself,
so
it's
like
I
like
was
trying
to
like
when
we
were
first
putting
that
together.
It's
just
like
we
made
decisions
and
we
were
just
like
all
right
cool
like
this
is
how
we're
doing
things
and
then
just
like.
D
Never
it
never
got
written
down,
because
it's
like,
of
course,
that's
like
just
the
way
that
we
do
it
so
yeah.
Some
things
may
make
sense
or
may
not
make
sense,
as
like
an
outsider
coming
in
and
like
trying
to
figure
stuff
out.
So
that's
why
I
I
would
encourage
you,
like
those
questions
like
hold
on
to
them,
because
I'm
sure
other
people
will
run
into
stuff
like
that
too,
in
the
future.
Definitely.
C
E
Yeah
I
just
wanted
to
give
a
shout
out
to
the
entire
team.
The
ui
is
looking
great,
not
just
for
commit,
but
all
the
stuff
I've
been
seeing
come
out
of
storybook
and
all
of
that
the
quality
of
work
is
amazing,
and
I
appreciate
that
every
time
I
click
on
a
review
app,
I'm
like
damn,
looks
so
good
and
tyler.
F
I
actually
just
like
to
echo
some
of
those
like
the
last
week
when
I
was
going
through
some
of
the
content
that
we
have
for
this
okr
and
you
go
to
some
blog
posts
and
you
see
brand
new
lovely
and
then
you
got
something
old
and
of
course,
your
eyes.
So
the
the
contrast
is
really
huge.
It's
more
than
night
and
day
it's
just
it's
different
galaxies,
so
yeah
10
out
of
10
for.
G
Everybody
I'm
up.
Next,
I
had
some
big
fears
of
being
over
committed
for
our
okrs
and
I
communicated
that
with
michael,
and
he
really
eased
that
for
me
and
really
stressed
for
okrs.
That
means
first
iteration,
it's
out,
so
we're
good
and
there's
there's
future
ones
that
we
can
work
on
after
that.
But
that
doesn't
mean
we
didn't
like
succeed
in
reaching
our
okrs
over
to
brandon.
H
So
I
just
wanted
to
you
know
note
that
it
feels,
like
everyone's
been
making
great
progress
on
large
tasks
without
you
know
having
to
go
in
and
direct
everyone.
So
that's
been
great,
really
appreciate
that
feels,
like
we've
been
getting
to
the
when
we
started
doing
something
in
our
sprint
planning
docs
recently,
where
we
had
kind
of
a
working
towards
section
where
we
noted
our
okrs
and
things
we
would
need
help
from
everyone
on.
I
feel
like
that,
helped
a
lot
this
iteration
cycle
past
couple
cycles.
H
So
that's
in
the
things
that
those
are
in
the
things
that
went
well
and
then
also
overall,
it
feels
like
we're
making
a
lot
of
progress
in
slippers
and
cms
and
templating,
and
all
that
great
stuff
that
we
haven't
had
for
the
past.
You
know
year
and
a
half
that
or
so
that
I've
been
here.
So
it's
it's
been
great.
Seeing
this
all
come
together,
so
huge
shout
out
to
everyone,
and
thanks
and
yeah
next
step
looks
like
stephen's
got
a
note.
F
F
But
if
you
have
a
question
or
if
you
have
a
concern
or
a
suggestion
on
how
to
improve
things,
everybody's
very
open
to
it
and
which
really
just
makes
it
a
bit
easier
to
go
about
your
business
and
not
feel
too
overwhelmed,
which
is
great
so
and
but
not
on
the
call
with
the
content
team,
they're,
all
very
nice
and
approachable
and
very
excited
about
the
work.
That's
ahead
as
well.
So
just
a
quick
one
on
that.
A
And
then
I
think
I
bring
up
the
rear,
thank
you
tyler,
specifically
for
creating
a
grid
specifically
for
the
event
template,
which
I
have
used
in,
like
all
five
of
the
blocks
that
I've
created.
It's
just
a
super
quick,
you
know,
quick
improvement,
while
the
larger
ongoing
grid
stuff
is
is
happening,
the
larger
epic
of
the
grid
foundation.
So
thank
you
for
that.
I
think
we
can
move
on
to
things
to
improve
on
it
looks
like
lauren
has
the
first
one.
G
I
just
wanted
to
call
out
that
the
contact
shifting
from
our
slippers,
repo
to
our
dub
dub
dub
repo,
is
hard.
It
takes
extra
we're
working
with
different
tech
stacks
different
language,
and
I
do
best
when
I
focus
on
one
repo
for
a
whole
a
whole
day
is
what
I
would
like
to
do,
but
I
can
get
at
least
a
half
day
on
each
one.
I
don't
know
if
we
can
make
that
better,
but
that's
my
current
situation
send
me.
C
Thank
you
lauren.
So
the
next
thing
we
can
improve
on
is
to
put
some
plan
into
place
to
avoid
overlapping
engineering
issues
such
as
the
one
that
happened
between
me
and
lauren
last
week
on
the
events
cap.
But
I
think
we
had
a
very
good
discussion
about
that
during
our
working
group
and
we
can
always
try
to
avoid
stuff
like
that,
so
that
we
can
always
move
with
speed,
and
I
think
it
happened
because
the
whole
the
hurry
to
push
a
lot
of
stuffs
out
and
that's
so
beautiful.
A
Thank
you
yeah.
I
made
a
note
here
about
code
reviews.
I
think
there
was
a
lot
of
pieces
that
came
out
from
the
whole
team,
especially
I
saw
a
lot
coming
and
going
in
slippers
and
I
feel
like
I'm
trying
to
assign
review
requests
to
different
people.
They
like
lighten
everyone's
low,
but
I
don't
know
if
that
is
adding
to
the
context
switching
problem
like,
but
I
also
don't
want
to
be
like
hey
javi,
you
get
all
my
code
reviews.
Good
luck!
Thank
you
so
much
you
know.
B
Yeah
I
I
know
I
don't
have
a
good
idea
about
like
the
rotation
itself,
although
I
know
that
there
are
ideas
out
there
like.
I
think
we
could
probably
find
something.
That's
easy,
whatever's
like
simplest
to
adopt
we're
a
small
enough
team
where,
like
there,
must
be
some
system
that
makes
a
lot
of
sense,
even
if
it's
literally
just
like
you
like,
take
a
piece
of
paper
with
every
reviewer's
name
and
you're
like
okay,
who
did
I
do
last
just
go
around
a
circle.
B
This
work
is
both
the
implementation
and
like
whatever
you
missed
in
that
first
iteration
and
then
the
final
piece
is
like
keep
that
within
reason,
because,
like
review
should
be
like
like
it
should
be
one
round
and
if
it
goes
further,
then
like
there's,
maybe
a
larger
problem
upstream
of
like
inappropriate
scoping
for
something
that
needs
like
10
reviews
or
whatever,
or
even
two
or
three.
So
those
are
my
initial
thoughts
and
I'll.
Have
you
go
next.
D
Sweet
just
briefly
because
I
have
some
comments
in
there
in
terms,
and
I
also
have
like
the
next
couple
of
points,
but
I
had
made
the
comment
about
setting
a
time
frame
to
review
mrs
during
an
iteration.
It
seems
like
people
are
on
board
with
that.
I
don't
know
like
at
what
point
that
should
happen.
I
feel
like.
D
B
There's
a
note
in
some
process
in
the
handbook,
and
I
can
find
the
link
elsewhere
but,
like
I
think
it's
one,
the
communication
protocol
things
about
like
acknowledge
receipts,
and
I
try
really
hard
to
like
when
I
when
I
get
asked
to
review
something
I
do
my
best
to
like
leave
a
comment
and
say
like
hey.
I
see
you've
asked
for
a
review
like
I'll
get
to
this
today
or
I'll
say
like
hey.
B
I
can't
get
to
this
until
tomorrow
and
like
then,
people
can
make
a
decision
of
like
do
they
need
it
reviewed
right
now,
because
it's
urgent
or
like
is
tomorrow
cool.
So
I
find
and
like
people
have
responded
well
to
especially
for
like
community
contributions
that
are
totally
unexpected.
We
get
a
lot
of
those
where
people
say
like
hey
like.
Can
you
review
this
and
I'll
be
like?
I
really
did
not
budget
for
this.
B
D
Yeah
and
I
see
lor
lauren
added
the
engineering
code
review
handbook
page,
which
I
think
we
should
link
to
in
from
our
handbook
just
so
that
we
have
something,
because
I
I
think
there's
been
like
times
where
we
wanted
to
like
make
our
own
situation
like
something
that's
more
like
team
specific
to
www.
But
I
think
like
linking
to
that
at
some
point
would
be
a
good
thing
and
we
can
add
that
as
an
action
item,
sorry,
I
was
just
like
something
right
there.
H
Just
a
quick
note
on
that.
One
thing
I
would
say
is
it's
definitely
important
to
to
ask
you
know,
and
why,
and
you
know
to
be
able
to
say
no.
I
would
just
caution
that
sometimes
no
is
not
sometimes
no
is
the
best
answer.
Sometimes
it's
better
to
frame
it
as
no,
but
maybe
x,
y
z
instead
or
this
aligns
with
or
we
can
get
to
it.
H
D
Agree
wholeheartedly
with
that
sentiment,
I
think
it's
like
that
saying,
no
with
kindness
or
like
telling
people.
Why,
like
you,
say
no,
not
just
like
no,
because
I
think
that,
like
feels
bad
things
to
improve
on
another
point
on
like
trying
to
keep
making
sure
that
we
add
documentation
during
the
process
of
an
mr
rather
than
like
after
I'm,
like
the
biggest
perpetrator
of
that
personally,
and
some
of
you
all
have
points
in
there
that
I
think
y'all
can.
B
Just
add
bad
documentation
like
it's,
it
doesn't
have
to
be
bad,
but,
like
add,
your
rough
draft
everything's
in
draft
is
like
a
sub
value
right
so
like
embrace
that,
as
a
specific
example
wrote
a
thing
during
blog
work,
I
wrote
like
a
helper
and
I
dropped
like
a
two-line
comment
in
the
helper
lauren
and
I
reviewed
it.
Lauren
made
a
change
during
a
follow-up
iteration
and
I
was
like
oh
hey
and
like
we
I
was
like.
B
We
should
update
this
comment
because
now
it's
out
of
date,
but
like
the
existence
of
the
comment
like
triggered
me
to
think
hey,
I
need
to
update
this
documentation
and
that
documentation
has
now
been
iterated
on
two
or
three
times
because
it
exists,
even
if
it's
literally
just
like
one
or
two
lines.
It's
like
this
function
returns
a
value,
maybe
not
quite
that
that
low
level
but
like
you
can
you
can
be
like
here's
the
input
and
here's
what
I'm
gonna
use
for
it.