►
From YouTube: Digital Experience Iteration Retro - June 3, 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/
A
Hi
everyone
welcome
to
the
digital
experience
teams,
iteration
retro
meeting,
so
we'll
go
over
things
that
went
well
and
things
to
improve.
On
from
this
past
two
weeks
and
it's
june,
I
said
june
2nd
in
the
last
meeting,
it's
june
3rd,
that's
my
bad
and
so
yeah.
First
of
all
things
that
went
well
happy.
It's
the
first
point.
B
A
I
have
the
next
point
here:
nathan,
it's
been
a
solid
two
weeks
now
I
guess
that
he's
been
with
us
and
it's
been
nice.
He
he's
wanted
to
pick
up
issues
to
learn
his
way
around
the
various
repos
that
we
have,
and
so
a
lot
of
good
things
came
down
the
pipe
he
got
a
few
like
syntax
fixes
all
the
way
to
like
kind
of
like
a
live
production
incident
like
he
said,
he's
gotten
the
full
range.
It's
been
really
great
having
him
here
to
pick
up
that
stuff.
A
C
I'm
trying
to
write
something
in
the
document,
but
I
I'll
tap
back
anyways.
I
do
have
something
to
say
about
something
that
went
well
and
I'll
fill
out.
The
document
after
so
working
on
the
cms
with
the
block,
components
and
slippers
is,
I
actually
closed
a
whole
design
issue,
because
I
didn't
need
it
because
I
worked
out
the
whole
entire
layout
and
just
the
initial
kind
of
research
and
wireframing
stage.
C
So
I
am
noticing
how
much
quicker,
at
least
for
me,
I'm
able
to
get
things
sorted
without
you
know
having
to
be
finicky
about
ui
just
with
these
existing
just
with
slippers
and
the
stigma
version
of
slippers
anyways
for
me,
so
that
for
me,
went
really
well
it.
It
is
why
my
one
of
the
reasons
why
my
my
week
was
green
work
wise.
B
Yeah
I
just
asked:
does
anyone
have
a
good
answer?
What,
when
friends
and
family
days
are,
and
so
then
jess
linked
the
link
for
the
company,
family,
friends
and
family
day,
to
which
I
replied,
wow?
That
was
a
direct
answer,
which
was
I
had
not
gotten
for
a
while.
So
I
appreciate
that
that
link-
I
didn't
even
know
why
friends
and
family
day
like
was
a
thing
like.
I
just
thought
it
was
like
a
gitlab.
D
B
A
Yeah,
so
I
just
onboarded
for
the
second
time
last
week
was
before-
and
I
kind
of
remembered
from
my
first
time
on
boarding
that
you
know
there
were
some
issues,
and
so
I,
as
I
went
along
if
something
came
up
like
a
spelling
error
or
something
was
confusing,
or
I
thought
it
should
be
in
a
different
place.
I
just
noted
it
in
the
stock
that
I
linked
here
just
to
like
remind
myself
later,
that
this
needs
to
be
fixed
and
pretty
much.
Almost.
A
All
of
them
are
like
very
small
things,
but
just
because
I
went
through
onboarding
and
was
still
working,
I'm
kind
of
catching
up
now
and
I
haven't
really
had
a
chance
to
actually
address
any
of
them
if
anyone
else
wants
to
take
a
stab
at
them.
That,
like
I
said,
they're,
usually
pretty
small
things,
but
I
thought
it'd
be
just
a
nice
way
to
kind
of
fix
things
as
we
go,
because
I
think
oftentimes
when
you're
onboarding,
like
oh,
that
sucked
and
then
you're
like.
Oh,
never
gonna.
Look
at
that
again.
A
A
So
I
don't
know
if
there's
a
better
way
to
go
around
like
getting
infra's
attention
or,
if,
like
we
just
ended
up
fixing
it
ourselves
by
re-releasing
slippers
and
crossing
your
fingers
that
it
released
everywhere,
which
it
did
but
yeah
that
doesn't
really
prevent
it
from
happening
again.
But
yeah.
The
concerning
things,
I
guess,
are
the
infrastructure
team
alert
didn't
seem
to
cause
any
sort
of
alert
and
yeah.
How?
How
does
this
not
happen
again-
and
I
think
javi
has
a
few
points.
D
E
I
will
jump
in
here,
I
would
say
no,
let's
not
get
any
access
to
any
of
our
infrastructure,
because
I
don't
want
it
and
I
don't
want
to
break
anything
because
that
is
scary
stuff
and
we
have
like
the
best
infrastructure
guy
teams
in
the
world.
So
let's
use
them,
but
there
is
a
a
gay,
a
hole
because
we
asked
for
support.
We
didn't
receive
support.
E
That
documents
like
a
process
of
what
to
do.
Okay,
there's
an
outage
like
what,
if
about
gitlab.com,
goes
down
and
it's
like
offline
like
do,
we
know
what
to
do.
Do
we
know
who
to
call
yeah
so
start
building
a
process
for
that,
and
I
put
a
side
note
of
that.
No
big
sight
pushes
after
thursday,
ideally
wednesday,
because
in
this
case
it
was
something
that
went
out
and
then
there
was
a
friday
and,
like
all
the
reports
came
in.
D
Yeah
yeah
kind
of
to
what
I
said
earlier,
just
about
getting
more
proficient
at
writing
issues
and
scoping
things
out,
and
I've
had
the
luxury
of
having
to
do
that
before
with
other
team
members
or
previous
jobs
with
project
managers.
So
to
kind
of
take
that
and
wear
that
hat
myself,
so
it's
just
getting
more
up
to
speed
on
that
and
see.
It's
sparked
a
little
bit
of
conversation
underneath
it
as
I
speak,
so
it
I
know
I
don't
think,
there's
a
good
way
or
a
bad
way
doing.
D
It
depends
on
the
issue
because
they're
all
so
different,
but
I
guess
for
some
of
the
ones
that
are
on
the
top
15.
They
might
benefit
from
something
like
a
template
that
we
have
because
we're
going
to
do
the
same
type
of
work
and
that's
why
we've
divided
them
out
and
then
some
will
require
more
work
than
others,
and
all
I've
been
doing
mostly
is
referencing
other
ones
and
copying
that
over
and
I
don't
know
if
that's
a
good
practice
or
a
bad
practice.
But
it
helps
me
because
I'm
not
very
proficient
with
it.
A
Yeah,
I
was
just
saying
that
I've
also
been
like
copying
and
pasting
from
other
issues
and
I
think
taking
the
time
to
actually
create
a
template,
will
be
better
for
my
own
usage,
but
also
so
other
people,
like
you,
actually
actually
asked
me
this
morning.
Steven
like
oh,
can
you
give
me
an
example
of
an
issue
that
uses
whatever
and
I
it
could
have
just
been
like?
C
It
was
just
about
the
templates.
I
was
curious
for
some
reason.
I
had
the
impression
that
we
didn't
own
templates.
If
we
weren't,
we
had
to
request
them
to
be
created.
My
mind
is
blown
now
that
just
says
we
can
just
create
templates.
I
want
to
do
that
and
use
templates,
because
I'm
constantly
copy
pasting
either
your
issues
just
or
some
of
my
old
issues,
depending
on
what
the
type
of
work
is
same
with,
that
yeah.
A
C
B
A
D
See
brandon
is
on
my
we're
both
of
him,
both
myself
and
himself
are
dri
on
prio
for
design
you're
right
for
engineering.
So
it's
great.
I
can
just
ask
him
whenever
I
need
to
and
he's
the
wealth
of
knowledge
when
it
comes
to
that
stuff,
but
it's
not
fair
to
just
rely
on
somebody,
because
that's
a
bottleneck.
D
So
if
we
can
spread
the
spread
the
workload
and
come
up
with
some
templates
that
may
or
may
not
work,
we
can
try
and
look
at
like
a
degree
of
flexibility
like
if
we
were
to
have
a
template
for
absolutely
every
type
of
issue.
It's
like
a
phone
book
of
templates
that
just
wouldn't
work.
We
only
need
to
narrow
it
down
to
a
few.
E
C
E
C
B
B
C
A
A
D
E
Anything
more
on
that
one:
okay
pop
down
the
next
one:
it
wasn't
fyy
fyi,
but
I
I
removed
that.
There's
this
great
epic
for
gitlab.com
improvements
and
support
and
there's
many
sub
epics
and
many
issues
nested
in
that
all
created
by
team
like
prior
to
to
us
and
there's
lots
of
really
great
stuff
in
there.
It
would
be
great
to
knock
some
of
it
out.
Q3
okr
question
marks.
E
B
A
B
I
I
don't
know,
but
I
feel
like
I
kind
of
like
feel
we
should
prioritize
that
more
within
our
friends,
but
I
just
don't
know
how
to
like
feasibly
pull
it
off
like.
I
almost
feel
like
we
need
to
like
section
off
even
more
of
our
sprint
like
say
just
to
do
some
of
those
things.
So
it's
like
say
like
we
spend
a
day
for
agency
related
stuff.
B
A
I
put
a
comment
that,
like
some
companies
will
do
like,
like
you
know
how
they're
hackathons
or
whatever,
but
some
companies
will
do
a
bug
bashing
week
or
whatever.
So
it's
just
like
you
know,
our
team
would
say
we're
not
doing
any
work
for
this
sprint
or
whatever,
and
you
just
clean
out
the
backpack
like
get
whatever
done,
that.
You
can't
close
any
issues
that
are,
like
you
know,
stale
or
whatever,
but
you're
right
about,
like
not
delivering
things.
A
Maybe
there's
a
way
to
like
do
it
like
one
person
at
a
time
like
I
take
a
full
sprint
and
just
don't
do
work,
I
don't
handle
any
new
requests.
I
take
pick
off
as
many
issues
as
I
can
in
our
backlog
or
in
this
like
www,
you
know
issue
or
whatever,
and
then
we
alternate
tyler
does
it
and
whatever,
like
you
know,
maybe
there's
a
way
to
like
convince
michael
that
that's
worthwhile
that
like,
if
one
of
us
can
focus
on
that
stuff
for
sprint.
It's
like
an
agency,
sprint.